v5.3.1 WIN x64 executable issue

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Just downloaded the latest [v5.3.1] on a Win x65 machine. Executable opens a command prompt for a fraction of a second and then closes. Tried running as Admin and same issue.
Expected Behavior
Should run/download files in parent folder.
Steps To Reproduce
Download the latest version.
Environment & Versions
- Operating System: Win 11 Pro
- Architecture: x64 bit
- Recyclarr Version: v5.3.1
- Recyclarr Build: v5.3.1
- Sonarr Version: N/A
- Radarr Version: N/A

Recyclarr Log File(s)
Don't have any
Configuration YAML
Don't have any

Sonarr / Radarr Logs
N/A

It's clear to me that very little effort was put into completing the issue report template. Furthermore, this is more of a support request which belongs in the Discussions tab.


TSLint cli output shows "Unused styles" warnings.

TSLint: 4.5.0
TS: 2.2
VSCode tslint extension: 0.8.1
What does the Unused styles point to? I have no indication of an error in VSCode, but the CLI execution
outputs this. I can't find any rules to reference which output this and have no clue what it is indicating?

you are correct. thank you. sorry. wish there was some sort of indication as to who was giving the warning.


Documented useDefineForClassFields

useDefineForClassFields is incompatible with experimentalDecorators, see https://github.com/lit/lit/issues/1985
There are two solutions, both should be covered by Lit's documentation:

Use useDefineForClassFields: false to force this new feature off.
Use declare to tell TS not to emit inline class fields that block the decorator define function.

Thank you for the PR! We've actually just landed a bunch of improvements to the docs around this issue in https://github.com/lit/lit.dev/pull/516 which you can see live at https://lit.dev/docs/components/properties/#avoiding-issues-with-class-fields.

@aomarks

Thank you for the PR!

Thanks and that's a lot more in depth, but it doesn't mention the declare option at all, and I think that might be a better option in new code than the compiler flag, as it will remain compatible with future TS changes (which seems unlikely for the flag).

Hi @KeithHenry. The engineer who wrote that section left the declare out intentionally. My understanding is that adding declare prevents you from initializing the property. For example:
@property()
declare name = 'No one';

Gives an error. Our preferred style is to initialize the field where we first declare it, and adding the declare keyword would break our sample code that uses this style. Hope that explains the thought process.

@arthurevans @aomarks I'm aware of that, it should be in the documentation too. Yes, declare prevents inline initialisation, but useDefineForClassFields: false affects that too, just in a different way.
So useDefineForClassFields: false lets you do this:
@property() name = 'No one';

However, this must not be initialised as a class field - that's the bit that breaks prototype setter decorators like @property, so the actual JS output (with useDefineForClassFields: false set) is something like:
constructor() {
  this.name = 'No one';
}
...
__decorate([property()], ExampleElement.prototype, 'name');

This makes the constructor vs prototype initialisation done by TS something you're relying on. It's not broken (so not bad practice as such) and definitely the easiest course updating existing Lit projects to TS 4.2, but it's also likely to change again in future and potentially have issues with TS's field outputs (they have good reasons for their switch to class fields by default).
Meanwhile declare syntax stops you from initialising fields, but then also doesn't have side effects that are in the JS output but not your TS working code.
Or to put it another way - if you want to initialise a decorated property with declare you need to set it in the constructor, but this is what TS outputs anyway.
I think it might be better practice to use declare rather than useDefineForClassFields: false because you get fewer potential issues with JS output, but honestly I'm not certain.
Either way declare should be in the documentation, with the explicit caveat that inline initialisation won't work.
Meanwhile useDefineForClassFields: false should have the caveat that inline initialisation will work but won't actually be inline anymore in the output JS.

// TS visible code
@property() declare name: string;

I would be worried about what this syntax will mean when decorators are finally standardized. This seems like it should be a TypeScript error, because the declare syntax means there would be no class field information in JS for the @property decorator to receive. Thoughts @justinfagnani ?


main thread panicked

rust: rustc 1.23.0 (766bd11c8 2018-01-01)
1 ❯ RUST_BACKTRACE=1 alacritty
thread 'main' panicked at 'unhandled pixel mode: LcdV', font/src/ft/mod.rs:481:24
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: __libc_start_main
  11: <unknown>

Which operating system does the issue occur on?
arch linux
If on linux, are you using X11 or Wayland?
X11

I added this to alacritty.yml but still no change.
font:
  options:
    antialias: lcd
    hinting: lcd

@jwilm was this what you meant ?

does your display have vertically decimated RGB sections?

No idea how to check that.


FireListener doesn't support a11y interaction

From what I see when I try to convert Checkbox to use FireListener, it isn't really supported. When I look at the logic in PressListener.click, it doesn't seem to support overriding press/release methods, which is how FireListener adds its listener. @jessegreenberg can we discuss this soon?

This impact https://github.com/phetsims/sun/issues/622, so raising priority to high.

Out of time to test more thoroughly tonight, but I think we should follow what was is being done for down event in PressListener:

Index: scenery/js/listeners/FireListener.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
--- scenery/js/listeners/FireListener.js	(revision c6b0dc1e26c0cd533f027ea725723c8b19709c60)
+++ scenery/js/listeners/FireListener.js	(date<PHONE_NUMBER>278)
@@ -129,6 +129,17 @@
     } );
   },

+  /**
+   *
+   * @param event
+   * @returns {void|*|undefined}
+   */
+  pdomPress( event ) {
+    return PressListener.prototype.pdomPress.call( this, event, () => {
+      this.fire( event );
+    } );
+  },
+
   /**
    * Releases the button.
    * @public
Index: scenery/js/listeners/PressListener.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
--- scenery/js/listeners/PressListener.js	(revision c6b0dc1e26c0cd533f027ea725723c8b19709c60)
+++ scenery/js/listeners/PressListener.js	(date<PHONE_NUMBER>477)
@@ -395,6 +395,50 @@
     return true;
   },

+  pdomPress( event, callback ) {
+    if ( this.canClick() ) {
+      this.interrupted = false; // clears the flag (don't set to false before here)
+
+      this.a11yClickingProperty.value = true;
+
+      // ensure that button is 'over' so listener can be called while button is down
+      this.isFocusedProperty.value = true;
+      this.isPressedProperty.value = true;
+
+      // fire the optional callback
+      this._pressListener( event, this );
+
+      callback && callback();
+
+      // no longer down, don't reset 'over' so button can be styled as long as it has focus
+      this.isPressedProperty.value = false;
+
+      // fire the callback from options
+      this._releaseListener( event, this );
+
+      // press or release listeners may have interrupted this click, if that is the case immediately indicate that
+      // clicking interaction is over
+      if ( this.interrupted ) {
+        this.a11yClickingProperty.value = false;
+      }
+      else {
+        // if we are already clicking, remove the previous timeout - this assumes that clearTimeout is a noop if the
+        // listener is no longer attached
+        timer.clearTimeout( this._a11yClickingTimeoutListener );
+
+        // now add the timeout back to start over, saving so that it can be removed later
+        this._a11yClickingTimeoutListener = timer.setTimeout( () => {
+
+          // the listener may have been disposed before the end of a11yLooksPressedInterval, like if it fires and
+          // disposes itself immediately
+          if ( !this.a11yClickingProperty.isDisposed ) {
+            this.a11yClickingProperty.value = false;
+          }
+        }, this._a11yLooksPressedInterval );
+      }
+    }
+  },
+
   /**
    * Releases a pressed listener.
    * @public
@@ -815,45 +859,12 @@
    * @param {SceneryEvent|null} event
    */
   click( event ) {
-    if ( this.canClick() ) {
-      this.interrupted = false; // clears the flag (don't set to false before here)
-
-      this.a11yClickingProperty.value = true;
-
-      // ensure that button is 'over' so listener can be called while button is down
-      this.isFocusedProperty.value = true;
-      this.isPressedProperty.value = true;
-
-      // fire the optional callback
-      this._pressListener( event, this );
-
-      // no longer down, don't reset 'over' so button can be styled as long as it has focus
-      this.isPressedProperty.value = false;
+    sceneryLog && sceneryLog.InputListener && sceneryLog.InputListener( `PressListener#${this._id} click` );
+    sceneryLog && sceneryLog.InputListener && sceneryLog.push();

-      // fire the callback from options
-      this._releaseListener( event, this );
+    this.pdomPress( event );

-      // press or release listeners may have interrupted this click, if that is the case immediately indicate that
-      // clicking interaction is over
-      if ( this.interrupted ) {
-        this.a11yClickingProperty.value = false;
-      }
-      else {
-        // if we are already clicking, remove the previous timeout - this assumes that clearTimeout is a noop if the
-        // listener is no longer attached
-        timer.clearTimeout( this._a11yClickingTimeoutListener );
-
-        // now add the timeout back to start over, saving so that it can be removed later
-        this._a11yClickingTimeoutListener = timer.setTimeout( () => {
-
-          // the listener may have been disposed before the end of a11yLooksPressedInterval, like if it fires and
-          // disposes itself immediately
-          if ( !this.a11yClickingProperty.isDisposed ) {
-            this.a11yClickingProperty.value = false;
-          }
-        }, this._a11yLooksPressedInterval );
-      }
-    }
+    sceneryLog && sceneryLog.InputListener && sceneryLog.pop();
   },

   /**
Index: sun/js/Checkbox.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
--- sun/js/Checkbox.js	(revision a002e8cc4a9c2d6af92dd3f2fd9c0faf8d8d473a)
+++ sun/js/Checkbox.js	(date<PHONE_NUMBER>332)
@@ -13,6 +13,7 @@
 import inherit from '../../phet-core/js/inherit.js';
 import merge from '../../phet-core/js/merge.js';
 import ButtonListener from '../../scenery/js/input/ButtonListener.js';
+import FireListener from '../../scenery/js/listeners/FireListener.js';
 import Node from '../../scenery/js/nodes/Node.js';
 import Rectangle from '../../scenery/js/nodes/Rectangle.js';
 import checkboxCheckedSoundPlayer from '../../tambo/js/shared-sound-players/checkboxCheckedSoundPlayer.js';
@@ -125,14 +126,23 @@

   content.pickable = false; // since there's a pickable rectangle on top of content

-  // interactivity
-  const checkboxButtonListener = new ButtonListener( {
+  // // interactivity
+  // const checkboxButtonListener = new ButtonListener( {
+  //   fire: function() {
+  //     if ( self.enabledProperty.value ) {
+  //       toggleAction.execute();
+  //     }
+  //   }
+  // } );
+
+  const checkboxButtonListener = new FireListener( {
     fire: function() {
       if ( self.enabledProperty.value ) {
         toggleAction.execute();
       }
     }
   } );
+
   this.addInputListener( checkboxButtonListener );

   // sync with property

Take the work in click, put it in a function called pdomPress. click calls pdomPress. Then pdomPress can be overridden in FireListener.

I don't love the way how this creates two separate channels, and how the a11y methods are like a tip-toe around the actual press hierarchy. What if we could rework PressListener.click() to use (at least in part) press, so that it can work automatically in subtypes like FireListener? Would that cause trouble over in DragListener because we wouldn't want that behavior?

I was wondering that myself! My guess is that we just didn't think about that when initially implementing. I would say go for it, and we can see if anything becomes a hurdle. I'm also happy to work on this next week during our pairing.

@jessegreenberg is taking the lead on this. Let me know if I can help.

https://github.com/phetsims/scenery/issues/1076#issuecomment-689644203 was done and it seems to be working well. ?fuzz and ?fuzzBoard? are not showing any issues locally.
@zepumph would you mind reviewing?

This needs to be blocks-publication until it's closed.

Is this issue blocking for the NS deliverable described in phetsims/natural-selection#208? Milestone for taking shas is this Thursday, 9/17.    If you don't care about a11y support for that milestone, then this is not blocking.  If you want to ensue that a11y works for anything that has a FireListener (like Checkbox, which NS has a load of) then this should be blocking, and the review should be wrapped up.

NS will not include any a11y in its publication @pixelzoom, this issue should not block its publication.

https://github.com/phetsims/tambo/issues/122 is the reminder for why we cannot use press and release directly in click. press and release require a genuine SceneryEvent with Pointer and DOMEvent. I played around with creating a fake SceneryEvent to still use press and release, but it seemed too fragile.
I looked into how we could change press and release as suggested in https://github.com/phetsims/scenery/issues/1076#issuecomment-689185432. But almost ALL of the work in press/onPress is for mouse/touch Pointer things. The only overlap is in setting the _isPressedProperty and calling the optional _pressListener.
So, I went back to something like https://github.com/phetsims/scenery/issues/1076#issuecomment-689181952 in the above commit.
Back to @zepumph to review this comment and https://github.com/phetsims/scenery/commit/0172d28b131988da9261fa5e08b6c67575b5e51d.

I understand and that all makes sense. Thanks for walking me through that. I really like your way of providing the callback with click. It parallels the other methods nicely.

OK, thanks for signing off! This can be closed then.


add a primary key

samp_name?

oops, that's actually sample_name now. I put samp_name in the aliases


Add all the projects

All the projects are not added to the website. @AnkitGuleria please see to it.

@AnkitGuleria tere se yeh umeed nahi thi:joy:

Done!!

Thanks @AnkitGuleria


Pass missing infer parameters during conversion

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #3365
Type of changes
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Pass missing infer parameters during conversion

I saw this PR linked to my issue and had a look out of interest as I wondered about the to_grpc method. In my own work around I had to make sure that the to_grpc was setting the parameters as kserve.protocol.grpc.grpc_predict_v2_pb2.InferParameter objects. This is in the transformer. Then in the predictor I had to do some conversion back to either string, int, float or bool with prior knowledge as to what they should be (I couldn't see a helper on that object to transform back to the intended format).
This is all new to me and I'm not very familiar with kserve so I might be talking nonsense but I couldn't see an elegant way to deal with that.
I must admit I'm using them to place extra information into the request to change some predictor behaviour and some custom component settings, so I could be abusing the functionality.

I saw this PR linked to my issue and had a look out of interest as I wondered about the to_grpc method. In my own work around I had to make sure that the to_grpc was setting the parameters as kserve.protocol.grpc.grpc_predict_v2_pb2.InferParameter objects. This is in the transformer. Then in the predictor I had to do some conversion back to either string, int, float or bool with prior knowledge as to what they should be (I couldn't see a helper on that object to transform back to the intended format).
This is all new to me and I'm not very familiar with kserve so I might be talking nonsense but I couldn't see an elegant way to deal with that.
I must admit I'm using them to place extra information into the request to change some predictor behaviour and some custom component settings, so I could be abusing the functionality.

Can you try with these changes and give some feedback ?

The change looks good, discussed with @Siva to add a few tests

Tests added.

Can you try with these changes and give some feedback ?

A gave your branch a go (3a773e7) but I'm hitting an assignment error pasted below. I think I remember hitting the same problem in my workaround and I ended not trying to reassign on the current parameters but instead recreating them.
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/uvicorn/protocols/http/httptools_impl.py", line 419, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "/usr/local/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py", line 78, in __call__
    return await self.app(scope, receive, send)
  File "/usr/local/lib/python3.10/site-packages/fastapi/applications.py", line 276, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/lib/python3.10/site-packages/starlette/applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.10/site-packages/starlette/middleware/errors.py", line 184, in __call__
    raise exc
  File "/usr/local/lib/python3.10/site-packages/starlette/middleware/errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.10/site-packages/timing_asgi/middleware.py", line 68, in __call__
    await self.app(scope, receive, send_wrapper)
  File "/usr/local/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 79, in __call__
    raise exc
  File "/usr/local/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "/usr/local/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
    raise e
  File "/usr/local/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 276, in handle
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 66, in app
    response = await func(request)
  File "/usr/local/lib/python3.10/site-packages/fastapi/routing.py", line 237, in app
    raw_response = await run_endpoint_function(
  File "/usr/local/lib/python3.10/site-packages/fastapi/routing.py", line 163, in run_endpoint_function
    return await dependant.call(**values)
  File "/usr/local/lib/python3.10/site-packages/kserve/protocol/rest/v2_endpoints.py", line 151, in infer
    response, response_headers = self.dataplane.encode(model_name=model_name,
  File "/usr/local/lib/python3.10/site-packages/kserve/protocol/dataplane.py", line 273, in encode
    response = response.to_rest()
  File "/usr/local/lib/python3.10/site-packages/kserve/protocol/infer_type.py", line 611, in to_rest
    res['parameters'] = to_http_parameters(self.parameters)
  File "/usr/local/lib/python3.10/site-packages/kserve/protocol/infer_type.py", line 688, in to_http_parameters
    parameters[key] = val.string_param
ValueError: Direct assignment of submessage not allowed

I am not reassigning the parameters dict anymore. Can you retry with these changes ?

I am not reassigning the parameters dict anymore. Can you retry with these changes ?

Yep these are being passed through now! The model I am testing is using grpc so once they get to the predictor I have to run the to_http_parameters so I can easily make use of the values in the dict of InferParameter types. But all the functionality is there now to do what I wanted to do, thanks!

Thanks @sivanantha321 fixing this!
/lgtm
/approve


feat: add cache to oras store

Description
What this PR does / why we need it:
To avoid lots of same requests to remote registry at the same time, we'd like to add a cache layer to the store API. Currently Ratify only implements the Oras store as built-in store, so we add Oras cache first. As the original implementation already supports GetBlobContent and GetReferenceManifest with cache, we only need to add cache to ListReferrers API.
This PR just introduced a new cache layer for Oras Store, which will invoke the original Oras API to retrieve data under the hood.
The cache package I used is Ristretto. I'm open to other packages as well.
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
This PR will address part of the issue: https://github.com/deislabs/ratify/issues/201
Type of change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

How Has This Been Tested?

Added unit tests.
Run CMD and K8s Add-on manually.

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

@shizhMSFT is anyone from ORAS interested in reviewing this?

@shizhMSFT is anyone from ORAS interested in reviewing this?

@qweeah @Wwwsylvia @wangxiaoxuan273 Could you help reviewing?


Error: no member named 'deep_copy' in namespace 'stan::model'

I'm running rstan (Version 2.9.0, packaged: 2016-01-05 16:17:47 UTC, GitRev: 05c3d0058b6a) and R version 3.2.3 (2015-12-10) on Mac OS X.
With the simple test model:
data {
  matrix[5, 2] X;
}

transformed data {
  matrix[5, 2] Xt;

  Xt <- X;
  Xt[,2] <- Xt[,2] / sd(Xt[,2]);
}

parameters {
  real a;
}

model {
  to_vector(Xt) ~ normal(a, 1.0);
}
```

I'm getting the following error:

Error in compileCode(f, code, language = language, verbose = verbose) :
Compilation ERROR, function(s)/method(s) not created! file3ae4a3a3ab.cpp:74:38: error: no member named 'deep_copy' in namespace 'stan::model'
stan::model::deep_copy(divide(stan::model::rvalue(Xt, stan::model::cons_list(stan::model::index_omni(), stan::model::cons_list(stan::model::index_uni(2), stan::model::nil_index_list())), "Xt"),sd(stan::model::rvalue(Xt, stan::model::cons_list(stan::model::index_omni(), stan::model::cons_list(stan::model::index_uni(2), stan::model::nil_index_list())), "Xt")))),
~~~~~~~~~~~~~^
1 error generated.
make: *** [file3ae4a3a3ab.o] Error 1

My naive search of the repository for deep_copy.hpp in GitHub seems to indicate that
`#include <stan/model/indexing/deep_copy.hpp>`
is only present in the test case for deep copying but nowhere else.

Thanks for reporting with a reproducible error and diagnosing the problem.
I was able to reproduce the error in RStan 2.9.0 and the current development version of CmdStd.  I'll fix by adding appropriate include (and integration test) ASAP.  We'll be able to roll out a quick fix, but it'll take a while to propagate through CRAN.

I figured out what's going on and am fixing in a bugfix branch.  There wasn't a test model for all the empty index cases (R style).  So I'm adding those and fixing the resulting assignment errors.  Should be done soon.

Thanks! The new R-style indexing is great and makes code cleaner.

this exact problem still occurs with stan 2.9.0-3 (here tested with the code of "to-ml", but in my own models as well).
Do I need to compile the develop branch from source in order to get the bugfix? I used the CRAN version and the install_github develop branch so far.
Is there a particular use-case scenario that crashes the compiler?
Error in compileCode(f, code, language = language, verbose = verbose) :    Compilation ERROR, function(s)/method(s) not created! file4637398b3b93.cpp: In constructor ‘model4637207f932e_2b312211b9bbe4eb97ea4a07ca409b1c_namespace::model4637207f932e_2b312211b9bbe4eb97ea4a07ca409b1c::model4637207f932e_2b312211b9bbe4eb97ea4a07ca409b1c(stan::io::var_context&, std::ostream*)’: file4637398b3b93.cpp:74:25: error: ‘deep_copy’ is not a member of ‘stan::model’ make: *** [file4637398b3b93.o] Error 1 In addition: Warning message: running command '/usr/lib/R/bin/R CMD SHLIB file4637398b3b93.cpp 2> file4637398b3b93.cpp.err.txt' had status 1

The pull request to fix this has been merged on the Stan
side.  So to build RStan with the fix, you'd need to make
sure that stan as a submodule of rstan is up to date with develop.

Bob

On Feb 25, 2016, at 10:43 AM, behinger<EMAIL_ADDRESS>wrote:
this exact problem still occurs with stan 2.9.0-3 (here tested with the code of "to-ml", but in my own models as well).
Do I need to compile the develop branch from source in order to get the bugfix? I used the CRAN version and the install_github develop branch so far.
Is there a particular use-case scenario that crashes the compiler?
Error in compileCode(f, code, language = language, verbose = verbose) :
Compilation ERROR, function(s)/method(s) not created! file4637398b3b93.cpp: In constructor ‘model4637207f932e_2b312211b9bbe4eb97ea4a07ca409b1c_namespace::model4637207f932e_2b312211b9bbe4eb97ea4a07ca409b1c::model4637207f932e_2b312211b9bbe4eb97ea4a07ca409b1c(stan::io::var_context&, std::ostream*)’:
file4637398b3b93.cpp:74:25: error: ‘deep_copy’ is not a member of ‘stan::model’
make: *** [file4637398b3b93.o] Error 1
In addition: Warning message:
running command '/usr/lib/R/bin/R CMD SHLIB file4637398b3b93.cpp 2> file4637398b3b93.cpp.err.txt' had status 1
—
Reply to this email directly or view it on GitHub.


Web component: Link list section - "Lorem ipsum dolor sit amet" - missing heading tag.

Detailed description
Issue:
"Lorem ipsum dolor sit amet" - This text visually looks prominent like a heading. But not given heading tag
Expected:
If this is a heading, Provide appropriate heading tag
Additional information

The fix should be adding heading role, similar to what <dds-card-heading> does.

The fix should be adding heading role, similar to what <dds-card-heading> does.


Orka build return codes should propagate back

Orka builders don't propagate back a bad return code from the remote shell: https://gitlab.com/finestructure/swiftpackageindex-builder/-/jobs/6748188934
Builder version: 4.38.0
./build.sh: line 64: gtimeout: command not found

This shows as a success in the Gitlab UI. This is not a problem for build reporting. This build is simply being ignored. However, it makes it more difficult to see if things are working as expected when looking at the job queue in Gitlab.
This is not a blocker to run the third Swift 6 preview run.

Fixed in https://gitlab.com/finestructure/swiftpackageindex-builder/-/merge_requests/281
https://gitlab.com/finestructure/swiftpackageindex-builder/-/jobs/6830811781

Fixed in https://gitlab.com/finestructure/swiftpackageindex-builder/-/merge_requests/281


Deployment suddenly started failing

I started using this Github action last week and everything worked perfectly fine with the following configuration:
- name: Deploy to Skynet
    uses: kwypchlo/deploy-to-skynet-action@main
    with:
      upload-dir: build
      github-token: ${{ secrets.GITHUB_TOKEN }}
      registry-seed: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' && secrets.REGISTRY_SEED || '' }}

Since yesterday exactly the same build starts failing when I manually retrigger it in Github actions.
I retrieve an Error: Failed to deploy: Request failed with status code 400 and do not know where this is coming from, as I run exactly the same code as last week.
All help debugging this is very much appreciated 🙏

I will add an error response to the log so we know what's happening. Thanks for bringing my attention to that.
On the other side, that's most likely an issue with the portal itself and not the action so it might be that it will just fix itself for you once the bug in portal is found and fixed.

I added some debugging messages that will help us understand what's happening in #4
Example: https://github.com/kwypchlo/note-to-self/runs/2453334435?check_suite_focus=true

White this doesn't solve your issue, this shows it's a portal issue. I will be working with our team on resolving that asap.


gradient accumulation for training & finetuning

Added argument for gradient accumulation in training & fine-tuning.

Deleted, forgot to remove trace points


Thoughts on the awesome-courses (https://github.com/prakhar1989/awesome-courses) repository?

Following the curriculum tag here at the OSSU GitHub repository, I discovered the awesome-courses repository, whose description is:

List of awesome university courses for learning Computer Science!

Obviously, I see a direct overlap in intent.

The courses listed there do not appear in OSSU's list of courses (barring one or two in the whole list). Does it mean that the other list is complimentary, i.e. providing valuable additional material to students?
Is it worthwhile to include that repository in OSSU's other curricula page?
Most importantly, if any OSSU-ians have taken or attempted to take some courses listed in the  awesome-courses repository, can they please provide a brief critique/review so that it will appear as a version of record here, and we can potentially discuss their inclusion.

It's a very useful repo for finding alternative courses to the ones in OSSU. It's basically an entire repo of extra/courses, just with a couple more restrictions iirc. It doesn't belong in other curricula because it's not a curriculum, it's a bunch of courses purposely including a lot of overlap: it's curated for including as much as possible within its guidelines, not for a set of courses one person should take. I agree with you though that it should probably be linked somewhere in OSSU. Dunno where though.

Thank you for your thoughts. I have a related, but separate thought.
There should be a page in the Wiki which collates courses that were evaluated for inclusion, but didn't make it, along a short statement stating their reason for exclusion. That Wiki page should be linked to from the main README.md. This really helps for posterity wherein next generation of students can refer, and potentially avoid bringing up an RFC for courses that have already been dealt with 4 years before (and it would help not to have to dig through years of individual GitHub issues).

There should be a page in the Wiki which collates courses that were evaluated for inclusion, but didn't make it

I'm concerned that this could become unwieldy. I also imagine that this information should be discoverable by searching the Github issues.

PR #996 adds an FAQ entry that points students to awesome-courses. Leaving the PR open for two weeks to invite improvements, will merge afterwards.

I will note that Awesome Courses has not been updated in over a year. This despite the fact that there are open pull requests that are actionable. It may be necessary to remove the link to this repo in the future.


Add support to enable/disable feature flags using helm options

What kind of request is this (question/bug/enhancement/feature request):
enhancement
Steps to reproduce (least amount of steps as possible):
Currently right now when we upgrade using helm upgrade  there is no way to disable/enable feature flags.
We have to upgrade 1st then make an API call to disable it.
So right now if I don’t want a fleet installed when upgrading the Rancher application.

Helm upgrade rancher application from rancher helm charts..
curl --retry 3 --retry-delay 10 -s -X PUT  -H "Authorization: Bearer $RANCHERAPITOKEN" - -H 'Content-Type: application/json' -H 'Accept: application/json' -d "${PAYLOAD}" "https://${RANCHEREND}/v3/features/${FEATURE}
Clean up all the namespaces and other workloads that are now overhead for something I don’t want… like

Every object in fleet-system namespace including the namespace itself
Every object in rancher-operator-system namespace including the namespace itself

Bounce rancher leader pod on local kuberentes cluster that is running rancher app.

Result:
N/A
Other details that may be helpful:
The end goal would be adding the following flags to the Rancher Helm chart.
helm upgrade rancher .....
--set feature.fleet=disable \
--set feature.istio-virtual-service-ui=disable \
.....

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5.7
Installation option (single install/HA): HA

gz#16453

@mattmattox Can you please check https://rancher.com/docs/rancher/v2.5/en/installation/resources/feature-flags/#enabling-features-for-kubernetes-installs and verify if this ticket can be closed?

Based on offline discussion, closing the ticket.


feat: add collectAPIStats() to fuzz tests

Added collectAPIStats()to the Fuzz Tests to show the overview table of the API Endpoints at the end of the run.

Thank you for the PR, but we decided internally that it makes probably the most sense to have two seperate projects for the API stats and the normal testing, to showcase both.


Analytic expectations of squared-exponential kernel

Documentation
I am implementing the analytic expectations of the squared-exponential kernel in Eqs. 15-17 of Titsias and Lawrence, 2010 (i.e., gplvm).
I found that implementations in GPflow of expectations of the squared-exponential kernel are very efficient (module expectations/squared_exponentials.py). I quickly implemented these expectations with for loops and found that the GPflow implementations are much faster. However, I don't understand their rationale. For instance, to implement Eq. 16 of Titsias and Lawrence, 2010, the GPflow implementation performs a Cholesky decomposition, while no matrix solve is apparently needed to implement Eq. 16.
Is there any documentation on the mathematical formulas behind this code, or can someone provide me some hints about these implementations?
Many thanks, Joaquin

In the original papers, Titsias&Lawrence only considered distributions on the uncertain inputs that were independent over dimensions. We consider correlated Gaussians, since Xcov can be D x D. We take the Cholesky of these matrices. This generally isn't too bad, since D is usually much smaller than e.g. M.


Add Find Trailing Whitespace GitHub action

Trailing Whitespaces are really annoying this PR add a GitHub action that can be used to find them
Here: https://github.com/dic-iit/bipedal-locomotion-framework/runs/2241283783#step:3:224 an example of failing action
~~https://github.com/marketplace/actions/find-trailing-whitespace~~ Not used because of https://github.com/harupy/find-trailing-whitespace/issues/13

Most files seem to be  the consequence of my changing of the IDE and not retaining the configuration that handled these. I will be careful, thanks!

I will be careful, thanks!

Don't worry @prashanthr05 :smiley:  Now there is the action for that


Stikbold remapping

Hi again, wondering if you can help me out. I'm trying to remap buttons for a game called Stikbold and not having any luck. According to this tutorial the game works with x360ce which would lead me to believe it would work with Durazno?
http://steamcommunity.com/app/429330/discussions/0/350542683204957512/
I tried renaming the DLL to 1_4, kind of following what it says in the tutorial for x360ce but it doesn't work, also when I do that and then open Durazno it wont let me remap the buttons in Durazno anymore... When the DLL is 1_3 it lets me remap the buttons in Durazno but it has no effect on the game either way...
Thank you sir.

Yes, the config thingy only works with the dll named 1_3. That's because the usage wasn't meant to be local, so you make the config and just copy the necessary files to the game.
As for the game itself, I have no idea. There should be a log that says if Durazno is in use. The name of the dll should match what the game is looking for.


docs: move decrement to the left side

This makes more sense for left-to-right language readers I think.

@all-contributors add @kentcdodds for docs


GH-1495 Make default future callback configurable

#1495

I've added @NotNull public BiConsumer<Context, Object> defaultFutureCallback = createDefaultFutureCallback(); field to inner config, as it's won't be widely used feature.
createDefaultFutureCallback() is located in ContextResolver because it's associated with context resolution and that class is already in Kotlin, so it's just easier to provide this default impl using when. I don't think that this method should be located in Context directly, even through ContextResolver, because we don't want to expose this value outside of the context, it's just a value we can use as a fallback in servlet handler, so indeed it should be only accessible from configuration.

#1504


Go to Running Cell is great... but... could be improved to "Go to Last Run Cell".

Open a notebook that has a good number of cells (20+) that will take a few minutes to run.
Modify one of the cells in the middle (but won't take long to get to) to contain an error.
Run All, making sure that the cell with the error isn't visible on the screen.

When execution ends due to the error it encounters, it's confusing what happened. Did the notebook complete? Why isn't it running? There's no indication that an error occurred that stopped execution.
Another approach here would be to automatically scroll to the cell that errors out, but I think that would be a pretty rude behavior.
This happened to me in a real-life situation, so marking as nb-golden.

This is a nice command to have but I'm not sure if I want to see all the time on the toolbar.

Referenced in https://github.com/microsoft/vscode-jupyter/discussions/9572.

+1
I would love to have this feature!
The use case mentioned by greazer is the main one, and it happens quite frequently to me and my colleagues.
Another use case would be something like:

Have a notebook with multiple cells
Run some computation-heavy cells which take some time to finish
Do some work somewhere else in the notebook
See from the status bar that the previously running cell finished
Quickly jump to the output by pressing "Go to Last Executed Cell" without scrolling

Great feature req, I reckon.
The real issue here is "failing silently". Where one of the cells throws an error, the person running the code needs to be made aware of it - if it was up to me, you'd get a beep and jump to the error (so the traceback in the output is on the screen).
Not sure about:

What do you do when you are just running one (or a couple of) cells? Jumping in this scenario could get annoying.
What do you do if the cell is partially in view?
What do you do for warnings?


kovid top N --death not working

kovid top 10 --death is not working but kovid top 10 -d works OK.
Let's fix kovid top 10 --death
Output:
ERROR: "kovid top" was called with arguments ["10", "--death"]
Usage: "kovid top N"

Because the switch is --deaths. Not --death.

Aha! The owner of this feature speaks up.


Remove panics in srml-support on corrupted storage state.

In few places we panic in case of corrupted storage state.
https://github.com/paritytech/substrate/blob/429380ea7d109bce29d6aba2c66f33e79c61ea11/srml/support/src/storage/generator/linked_map.rs#L113-L114
https://github.com/paritytech/substrate/blob/429380ea7d109bce29d6aba2c66f33e79c61ea11/srml/support/src/storage/unhashed.rs#L23-L27
To remove them I see two strategy:

silently handle those error in those functions, like get would return None in case it can't decode and enumeration will stop in case it can't continue (or even maybe update the linkage)
provides some method with Result output. this would allow module programmer to make some logic to handle corrupted state.
make the types implement a trait which is:trait OnCorruptedState {
  fn on_corrupted_state(state: &[u8]) -> Option<Self>;
}

and this function would be called on when this happens

The question is more do we want to write specific code when state is corrupted ? or should silently fix the storage state by removing values.
note that our silent fix will be somewhat inconsistent like for linked_map if enumeration is broken by a corrupted linkage then some (key, value) are still part of the map (like accessible with get) but not part of the enumeration.

also with the first strategy:

silently handle those error in those functions, like get would return None in case it can't decode and enumeration will stop in case it can't continue (or even maybe update the linkage)

I wonder if there is some log feature in the runtime, like we could at least log than an error has happended.

I like your OnCorruptedState idea :)
If we could integrate this somewhat easily into the decl_storage! macro, we could by default just return the default value, but we could give the user the possibility to provide a closure that would be running as part of on_corrupted_state to give us the new value.

I reckong storage migration could also be a subset of OnCorruptedState ?

I reckong storage migration could also be a subset of OnCorruptedState ?

I can imagine having version in the encoding of the values, like one byte for the version ($Version++encode(value)) and if version failed to decode then this on corrupted state could be called. But I don't feel that this is the prefered way to do migration.

What's wrong with panicking? Don't we already use panics to bail out of invalid extrinsics and such?

maybe some more minor modules could panic, and we can just recover from it by some runtime upgrade. The worst thing I see is that if we can panic in some on_initialize of those kinds of minor modules. And with this PR it should be less harmfull

What's wrong with panicking? Don't we already use panics to bail out of invalid extrinsics and such?

yes - panics are (might, actually, i haven't checked recently) (mis-)used for bailing out of extrinsics that are invalid  before funds are charged, but conditionally on their inclusion.
however, there are two reasons why we never want to panic outside of this circumstance:

if we panic unconditionally (e.g. in on_initialize/on_finalize), then it basically means a bricked chain; by definition no block could be constructed without it panicking and therefore the chain is dead. assuming grandpa is being efficient, then this means we'd have to revert finality to fix the chain which is, well, about as problematic as it gets.
if we panic within a transaction, but after funds have been charged, then the panic will have the effect of creating a DoS vector for all validators. they'd be forced to execute the transaction without the possibility of including it into a block and thus getting paid for their efforts. spamming the network with well-crafted transactions that take close to a full block's weight to execute yet can never actually be included would be rather problematic.

thus, if at all possible we want to avoid panicking as a possibility and early exit in the case that we see something which doesn't add up. for transactions this means checking all your data before you write anything. for on_initialize/finalize it's tricker but i would again assume it's better to do nothing and continue with the rest of the processing because this at least allows for a governance transaction to come in and fix storage without reversion.
once we have the ability for on-chain logic to temporarily suspend finality, we should hook it into the assertion system so that a corrupted storage doesn't brick the chain but does halt finality for an extended period of time, allowing us the chance to fix with governance as well as the possibility of a non-finality-breaking reversion.
we shouldn't be attempting to proactively "repair" storage though as that's likely to create even more of a mess that governance would need to clean up.

current panic has been removed and no need for specific handling as stated above:

we shouldn't be attempting to proactively "repair" storage though as that's likely to create even more of a mess that governance would need to clean up.


Serialize -> Deserialize of struct crate a SpannedError

An simple Serializing and BackDeserialize does creat an error.
Did I do something wrong?
#[derive(Clone, Debug, Decode, Default, Deserialize, Encode, PartialEq, Serialize)]
#[serde(deny_unknown_fields)]
pub struct AvailableCards {
	pub left: u8,
	pub right: u8
}

#[derive(Clone, Debug, Deserialize, Serialize)]
struct MapProperties{
	#[serde(flatten)]
	cards: AvailableCards,
}

let map_properties = MapProperties{cards: AvailableCards{
	..Default::default()
}};
let map_properties = ron::to_string(&map_properties).unwrap();
println!("{map_properties}");
let map_properties: MapProperties = ron::from_str(&map_properties).unwrap();  //line 145

{"left":0,"right":0}
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: SpannedError { code: ExpectedIdentifier, position: Position { line: 1, col: 2 } }', /home/lukas/git/m3/map/src/lib.rs:145:76
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Some with serde_json works:
let map_properties = MapProperties{cards: AvailableCards{
	..Default::default()
}};
let map_properties = serde_json::to_string(&map_properties).unwrap();
println!("{map_properties}");
let map_properties: MapProperties = serde_json::from_str(&map_properties).unwrap();

Thank you for the report! This was fixed in #455, which is so far only available on the master branch. Until a new version of RON is published, can you switch your dependency to point to that? I've also added your failure case as a test case to ensure that it doesn't break in the future.

Thank you @LuckyTurtleDev for the test case - it was added to the test suite in #457


Application Launcher dropdown implementation should remove arrow

The new design for the application launcher does not include an arrow in the dropdown. See: http://www.patternfly.org/pattern-library/application-framework/masthead/#design
The application launcher design will be updated to reflect this change and the angular code should be updated as well here:
http://www.patternfly.org/angular-patternfly/#/api/patternfly.navigation.component:pfApplicationLauncher

Hi @lizsurette, are you saying the arrow in the Help dropdown is no longer in the dropdown?  Is this a Masthead Issue or an issue for the Application Launcher?  -thanks

Hey @dtaylor113 there is a bit of history on where this bug was identified over the in react repo here:
https://github.com/patternfly/patternfly-react/pull/319
But essentially, the design of the application launcher has changed with the new masthead design. The application launcher design along with the angular implementation needs to be updated to reflect the new masthead design. @mcarrano is adding an issue on the design side.

@dtaylor113 with that being said...I don't think we want that arrow next to the help icon either :) Check this base implementation out of the app launcher:
http://www.patternfly.org/pattern-library/application-framework/launcher/#code

ah, ok, in the App Launcher popup, no arrow pointing back up to the App Launcher icon in the masthead.  -thanks


CURRENT DEVELOPMENT STATUS

Hi guys,
I wanted to keep you updated about the status of the software.
So currently we have a beta going on that fixes most of the reported bugs (Please us it!)
But the best thing is that we are moving for NW.JS to Electron for the next big release.
That means that no further development will be made in the current dev branch V1.5.X and we don`t plan to make a stable out of it.
The new code is in the branch develop and we are still working on it to make a stable that will be released soon.
For those who want a preview of it, I suggest you try to build it and give it a shot.
Any comments/suggestions will be appreciated.
Cheers!

I am curious about the reasons behind the change to Electron, could you explain?

Not my decision, @Aluxian


Add prune support using a separate service and cron schedule

closes #22

@zoispag There are several points to this:

Of course it is possible to spawn a second go-cron instance in the background for the prune job. This prevents proper process management and container termination handling by Docker, as the second instance is not waited for by its parent process. This is a minor issue though which probably does not lead to problems in practice. Also, the output of both jobs is now tangled up.
The prune process needs a huge amount of memory, so it makes sense to run it on a different node with enough resources. You can also set different resource limits for this container (either using compose v3 limits in swarm mode or compose v2 limits for non-swarm mode with docker compose).
When using Docker swarm mode (as I am doing), the backup container has to be run all nodes while the prune process only needs to be run on one. That node, as said above, should have enough resources for the prune process. It can be selected effectively by setting (memory) resource reservations on the service.

If you don't have big issues with that approach, I prefer to keep this as two separate containers / services.

I am not using swarm, but I can see the reasoning behind. I am also aware that restic prune utilizes way too many resources. In my setup, I am using docker-compose, and for some of the combination of services (for example x.test and x.prod), I am using the same s3 bucket as a repo. Thus, I have to add a new container in docker-compose.override.yml for one of these combinations. The other approach would allow me to specify only the PRUNE_CRON as an ENV variable in docker-compose.override.yml. But I agree, not much of a hassle, since I still have to do something either way.

If you don't like the duplication of the env variables, you can use the env_file setting in the compose file.

Of course, there are no ENV variables in the compose file. The docker-compose.yml itself, is shared across more than 80 servers, which are happily backed up using resticker 😄


Implement Equal[A] for all instances of Show

Show tends to be similar to a specific "view" of the language. Comparing these is natural.
It would be as simple as a.show[X].isEqual(b.show[X]) but could be optimised on an individual basis.

Related to #717

Contrib has been stable for a while now and is working great. Let's defer feature requests like this ticket until we have someone driving the work.


get "Cannot find name 'Clipboard'" error when building using webpack

90% optimize assetsError in bail mode: [default] C:/Users/dlyu/rr-frontend/node_modules/angular2-clipboard/src/ngii-clipboard.directive.ts:8:15
Cannot find name 'Clipboard'.

I'm using the angular2-webpack-starter from @angularclass.

The project is updated. Please try again. let me know if the issue still exists. I will reopen the issue. Thx


Unable to resolve mapPropsToStyleNames

react-native, react and native-base version
    "native-base": "2.4.5",
    "react": "16.4.0",
    "react-native": "0.55.4",

Expected behaviour
No errors
Actual behaviour
Unable to resolve ../utils/mapPropsToStyleNames" from ".//node_modules/native-base/dist/src/basic/View.js`: The module `../utils/mapPropsToStyleNames` could not be found"

Steps to reproduce (code snippet or screenshot)

Screenshot of emulator/device
Is the bug present in both ios and android or in any one of them?
Using iOS simulator. I haven't tried Android, but I would assume it happens there too.
Any other additional info which would help us debug the issue quicker.
Just booting the project from yarn start and I get this. Running on MacOS 10.13.4

@jwoertink Try clearing cache before run
npm start -- --reset-cache
#1856

@SupriyaKalghatgi I tried that, but still get the same error. I even rm -rf node_modules then npm install and booted. I just renamed the directory in my node_modules/native-base to get my app to boot.

@jwoertink Can you put your app on github or snack, for us to look into

I can't push up the source, but maybe I can try and recreate a sample app. It might take me a bit, but I'll try and get something.

I'm hitting the same issue. Upgraded from 2.4.2 to 2.4.5 and I have "Utils" not "utils" in my path, so getting same error:
The module `../utils/mapPropsToStyleNames` could not be found
Filesystem has:
./node_modules/native-base/dist/src/Utils/mapPropsToStyleNames.js
./node_modules/native-base/dist/src/Utils/mapPropsToStyleNames.js.map
./node_modules/native-base/src/Utils/mapPropsToStyleNames.js

I had to yarn remove native-base then yarn add native-base to get the proper file structure (utils). I think the upgrade from 2.4.2 to 2.4.5 just didn't rename the folder properly.

you can rename folder from Utils to utils by yourself as temporary fix

@54vanya That isn't necessary, since this issue was fixed long back

@jwoertink Tried this?

The renaming folder? That's what I had to do to get it to work. I haven't had a chance to do a mock app yet to recreate it. After digging in, I think it's something with cache, but using --reset-cache doesn't work. Possibly something between yarn and npm maybe? No clue

@jwoertink Thousands of users using NativeBase with this version, no issues reported regarding this
We tried helping you, asked you to create sample project for us to check and help you
Anything else that you need from us?

@SupriyaKalghatgi true, but @kodayashi also just reported this issue too. We can just close it out for now. If I get some free time, I'll try to re-create in a sample app and can always re-open later. Unless anyone else runs in to this issue and is able to re-create somehow. Thanks for the help!

@jwoertink Thank you for cooperation
We cant help anyone out, unless we are able to reproduce it, thats how it works

almost similar to @kodayashi, I did upgrade from 2.4.2 to 2.5.2.
@SupriyaKalghatgi perhaps you could reproduce this issue by install 2.4.2 and then upgrade it to latest version.

In that case, @lonewolfffffff i will try to reproduce it by your way

I had the same issue with a fresh install of native base. Only renaming the Utils folder to utils helped.

Had the same issue. The issues seems to be present if you are running an old version of native-base definitely crops up in 2.4.2 for me. Just edit your package.json file to drop native-base. run yarn (or npm install), then run yard add native-base (or npm install --save native-base) to add it back, and it will install the latest version with all the fixes.

I found a folder that named Utils in the node_modules/native-base/dist/src instead utils (they are different of letter case)

I just ran into this issue when upgrading from 2.3 -> 2.8.1. I suspect it's an issue with npm or yarn caching modules because it was resolved when I wiped my npm cache then reinstalled 2.8.1.

Problem solved by rm -rf node_modules && yarn install.
Cache issue.


Call authenticate method on refresh page

https://github.com/feathersjs/feathers-client/issues/68
https://github.com/josx/aor-feathers-client/issues/35

thanks a lot!


python37: init at 3.7.0b1

Beta version of Python 3.7.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

The current version builds and works. Even though, we should:

[ ] use hash-based bytecode PEP 552
[ ] check the UTF-8 changes

Success on x86_64-linux (full log)
Attempted: python37
Partial log (click to expand)
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/7yyxibzvdanji3hc2471c2fqj8z0wqfy-python3-3.7.0b4/lib  /nix/store/7yyxibzvdanji3hc2471c2fqj8z0wqfy-python3-3.7.0b4/bin
patching script interpreter paths in /nix/store/7yyxibzvdanji3hc2471c2fqj8z0wqfy-python3-3.7.0b4
/nix/store/7yyxibzvdanji3hc2471c2fqj8z0wqfy-python3-3.7.0b4/bin/python3.7m-config: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
/nix/store/7yyxibzvdanji3hc2471c2fqj8z0wqfy-python3-3.7.0b4/lib/python3.7/config-3.7m-x86_64-linux-gnu/makesetup: interpreter directive changed from " /bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
/nix/store/7yyxibzvdanji3hc2471c2fqj8z0wqfy-python3-3.7.0b4/lib/python3.7/config-3.7m-x86_64-linux-gnu/install-sh: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
/nix/store/7yyxibzvdanji3hc2471c2fqj8z0wqfy-python3-3.7.0b4/lib/python3.7/ctypes/macholib/fetch_macholib: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/7yyxibzvdanji3hc2471c2fqj8z0wqfy-python3-3.7.0b4...
wrong ELF type
/nix/store/7yyxibzvdanji3hc2471c2fqj8z0wqfy-python3-3.7.0b4

Failure on x86_64-darwin (full log)
Attempted: python37
Partial log (click to expand)
    pid = forkpty(&master_fd, NULL, NULL, NULL);
          ^
./Modules/posixmodule.c:6234:11: warning: this function declaration is not a prototype [-Wstrict-prototypes]
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes    -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration   -I. -I./Include -I/nix/store/byjz3zsj2397x4bllp4axqcnc517jdl7-zlib-1.2.11-dev/include -I/nix/store/qggzkch99ab8dnzyv1dflvl97mqxqcd2-bzip2-<IP_ADDRESS>.1-dev/include -I/nix/store/lszb9xprsaj0qbb61i2603yhags07x3m-expat-2.2.5-dev/include -I/nix/store/gls4179iw8xlrvm3qwr3cwzpgy5rdshf-xz-5.2.3-dev/include -I/nix/store/si0g5b52xhrpdd8xjd67xdpskfgfscid-libffi-3.2.1-dev/include -I/nix/store/33pspxxdp0jc0q1hd4k629mpxi39f4f4-gdbm-1.14.1/include -I/nix/store/6xmmwfkbb1g0g420ndjr6bjd5sxx9wgf-sqlite-3.22.0-dev/include -I/nix/store/nblby1iqln9grw4yb03fmprch4k0kv48-readline-6.3p08-dev/include -I/nix/store/926k3c6zc5i7xv6f2fk15p408cs5hqld-ncurses-6.1-dev/include -I/nix/store/pf16lx06p07zklkdra52p7b5akpd35qj-openssl-1.0.2o-dev/include -I/nix/store/fgbq3pqgw4xqifc75wmvsz6vrs0z2pk1-CF-osx-10.10.5/include -I/nix/store/2yipfqi0jkvfnk69rih2dzccf01ly1jw-configd-osx-10.8.5/include -I/nix/store/byjz3zsj2397x4bllp4axqcnc517jdl7-zlib-1.2.11-dev/include -I/nix/store/qggzkch99ab8dnzyv1dflvl97mqxqcd2-bzip2-<IP_ADDRESS>.1-dev/include -I/nix/store/lszb9xprsaj0qbb61i2603yhags07x3m-expat-2.2.5-dev/include -I/nix/store/gls4179iw8xlrvm3qwr3cwzpgy5rdshf-xz-5.2.3-dev/include -I/nix/store/si0g5b52xhrpdd8xjd67xdpskfgfscid-libffi-3.2.1-dev/include -I/nix/store/33pspxxdp0jc0q1hd4k629mpxi39f4f4-gdbm-1.14.1/include -I/nix/store/6xmmwfkbb1g0g420ndjr6bjd5sxx9wgf-sqlite-3.22.0-dev/include -I/nix/store/nblby1iqln9grw4yb03fmprch4k0kv48-readline-6.3p08-dev/include -I/nix/store/926k3c6zc5i7xv6f2fk15p408cs5hqld-ncurses-6.1-dev/include -I/nix/store/pf16lx06p07zklkdra52p7b5akpd35qj-openssl-1.0.2o-dev/include -I/nix/store/fgbq3pqgw4xqifc75wmvsz6vrs0z2pk1-CF-osx-10.10.5/include -I/nix/store/2yipfqi0jkvfnk69rih2dzccf01ly1jw-configd-osx-10.8.5/include   -c ./Modules/_sre.c -o Modules/_sre.o
2 warnings and 2 errors generated.
make: *** [Makefile:1793: Modules/posixmodule.o] Error 1
make: *** Waiting for unfinished jobs....
clang-5.0: warning: argument unused during compilation: '-fno-strict-overflow' [-Wunused-command-line-argument]
builder for '/nix/store/9jp2akl2w46lscky4d0g6vrj2fg2ijsz-python3-3.7.0b4.drv' failed with exit code 2
error: build of '/nix/store/9jp2akl2w46lscky4d0g6vrj2fg2ijsz-python3-3.7.0b4.drv' failed

Success on aarch64-linux (full log)
Attempted: python37
Partial log (click to expand)
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/zj5zn76a37p2mihs2r4yy7zccfrvvcml-python3-3.7.0b4/lib  /nix/store/zj5zn76a37p2mihs2r4yy7zccfrvvcml-python3-3.7.0b4/bin
patching script interpreter paths in /nix/store/zj5zn76a37p2mihs2r4yy7zccfrvvcml-python3-3.7.0b4
/nix/store/zj5zn76a37p2mihs2r4yy7zccfrvvcml-python3-3.7.0b4/lib/python3.7/config-3.7m-aarch64-linux-gnu/install-sh: interpreter directive changed from "/bin/sh" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/sh"
/nix/store/zj5zn76a37p2mihs2r4yy7zccfrvvcml-python3-3.7.0b4/lib/python3.7/config-3.7m-aarch64-linux-gnu/makesetup: interpreter directive changed from " /bin/sh" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/sh"
/nix/store/zj5zn76a37p2mihs2r4yy7zccfrvvcml-python3-3.7.0b4/lib/python3.7/ctypes/macholib/fetch_macholib: interpreter directive changed from "/bin/sh" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/sh"
/nix/store/zj5zn76a37p2mihs2r4yy7zccfrvvcml-python3-3.7.0b4/bin/python3.7m-config: interpreter directive changed from "/bin/sh" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/zj5zn76a37p2mihs2r4yy7zccfrvvcml-python3-3.7.0b4...
wrong ELF type
/nix/store/zj5zn76a37p2mihs2r4yy7zccfrvvcml-python3-3.7.0b4

Would not this still need C.UTF-8 locale? https://github.com/NixOS/nixpkgs/issues/20192

Would not this still need C.UTF-8 locale? #20192

https://docs.python.org/3.7/whatsnew/3.7.html#pep-540-forced-utf-8-runtime-mode

When in UTF-8 mode, CPython ignores the locale settings, and uses the UTF-8 encoding by default. The error handlers for sys.stdin and sys.stdout streams are set to surrogateescape.
The forced UTF-8 mode can be used to change the text handling behavior in an embedded Python interpreter without changing the locale settings of an embedding application.
The UTF-8 mode is enabled by default when the locale is “C”. See PEP 538: Legacy C Locale Coercion for details.

So, yes. While your workstation typically has a UTF locale configured, this is or may not be the case on say servers or inside services.

Failure on x86_64-darwin (full log)
Attempted: python37
Partial log (click to expand)
    if (openpty(&master_fd, &slave_fd, NULL, NULL, NULL) != 0)
        ^
./Modules/posixmodule.c:6234:11: error: implicit declaration of function 'forkpty' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
    pid = forkpty(&master_fd, NULL, NULL, NULL);
          ^
./Modules/posixmodule.c:6234:11: warning: this function declaration is not a prototype [-Wstrict-prototypes]
2 warnings and 2 errors generated.
make: *** [Makefile:1793: Modules/posixmodule.o] Error 1
builder for '/nix/store/7lmwg1sb2b0gvkg5xmam08kx2sjcx8s5-python3-3.7.0b4.drv' failed with exit code 2
error: build of '/nix/store/7lmwg1sb2b0gvkg5xmam08kx2sjcx8s5-python3-3.7.0b4.drv' failed

Success on x86_64-linux (full log)
Attempted: python37
Partial log (click to expand)
gzipping man pages under /nix/store/ivymxqqgw85l74xrx28lbnmmp7w0ww4w-python3-3.7.0b4/share/man/
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ivymxqqgw85l74xrx28lbnmmp7w0ww4w-python3-3.7.0b4/lib  /nix/store/ivymxqqgw85l74xrx28lbnmmp7w0ww4w-python3-3.7.0b4/bin
patching script interpreter paths in /nix/store/ivymxqqgw85l74xrx28lbnmmp7w0ww4w-python3-3.7.0b4
/nix/store/ivymxqqgw85l74xrx28lbnmmp7w0ww4w-python3-3.7.0b4/bin/python3.7m-config: interpreter directive changed from "/bin/sh" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh"
/nix/store/ivymxqqgw85l74xrx28lbnmmp7w0ww4w-python3-3.7.0b4/lib/python3.7/ctypes/macholib/fetch_macholib: interpreter directive changed from "/bin/sh" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh"
/nix/store/ivymxqqgw85l74xrx28lbnmmp7w0ww4w-python3-3.7.0b4/lib/python3.7/config-3.7m-x86_64-linux-gnu/makesetup: interpreter directive changed from " /bin/sh" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh"
/nix/store/ivymxqqgw85l74xrx28lbnmmp7w0ww4w-python3-3.7.0b4/lib/python3.7/config-3.7m-x86_64-linux-gnu/install-sh: interpreter directive changed from "/bin/sh" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/ivymxqqgw85l74xrx28lbnmmp7w0ww4w-python3-3.7.0b4...
wrong ELF type

Success on aarch64-linux (full log)
Attempted: python37
Partial log (click to expand)
strip is /nix/store/qg2agrqkf240s656d207zqhipl0bc2id-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/2w9s10p7rn3dcp916khc08hj5lsgcf4x-python3-3.7.0b4/lib  /nix/store/2w9s10p7rn3dcp916khc08hj5lsgcf4x-python3-3.7.0b4/bin
patching script interpreter paths in /nix/store/2w9s10p7rn3dcp916khc08hj5lsgcf4x-python3-3.7.0b4
/nix/store/2w9s10p7rn3dcp916khc08hj5lsgcf4x-python3-3.7.0b4/lib/python3.7/config-3.7m-aarch64-linux-gnu/install-sh: interpreter directive changed from "/bin/sh" to "/nix/store/9rv2bzx7jz6wjbaxij5qq580qvzksj4i-bash-4.4-p19/bin/sh"
/nix/store/2w9s10p7rn3dcp916khc08hj5lsgcf4x-python3-3.7.0b4/lib/python3.7/config-3.7m-aarch64-linux-gnu/makesetup: interpreter directive changed from " /bin/sh" to "/nix/store/9rv2bzx7jz6wjbaxij5qq580qvzksj4i-bash-4.4-p19/bin/sh"
/nix/store/2w9s10p7rn3dcp916khc08hj5lsgcf4x-python3-3.7.0b4/lib/python3.7/ctypes/macholib/fetch_macholib: interpreter directive changed from "/bin/sh" to "/nix/store/9rv2bzx7jz6wjbaxij5qq580qvzksj4i-bash-4.4-p19/bin/sh"
/nix/store/2w9s10p7rn3dcp916khc08hj5lsgcf4x-python3-3.7.0b4/bin/python3.7m-config: interpreter directive changed from "/bin/sh" to "/nix/store/9rv2bzx7jz6wjbaxij5qq580qvzksj4i-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/2w9s10p7rn3dcp916khc08hj5lsgcf4x-python3-3.7.0b4...
wrong ELF type
/nix/store/2w9s10p7rn3dcp916khc08hj5lsgcf4x-python3-3.7.0b4

@FRidh I believe this is obsolete since  7261a66d713aabf30249535bfa53e5d205c4423e

Yep, closing.


gem_package recipe breaks chef_gem

After enabling gem_package recipe the chef_gem starts installing all gems to RVM's ruby instead of /opt/chef/embedded/lib/ruby/gems, just like gem_package. Spend half of the day today debugging database cookbook failure, it is failing on requiring mysql2 and pg gems right after chef_gem "mysql2" and chef_gem "pg".

Closing due to inactivity.
If this is still an issue please reopen or open another issue. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help!
Thanks,
Sous-Chefs


Research and implement Google Accelerated Mobile Pages (AMP) for posts

Research and implement Google Accelerated Mobile Pages (AMP) for.. posts? everything?
Seems like these are separate pages with separate AMP markup, referenced via meta tag in parent non-AMP document.
I don't like these, but they are getting SRP icons it looks like.
https://www.ampproject.org/docs/get_started/about-amp.html
cc @jsfowles just FYI

WONT FIX.  The more I read about AMP, the less I like it.  No SEO penalty for not implementing.


Option 1: Use alternate way to incorporate CDTS

Closes #469
Changes

Updated CDTS to version 5.0.2.
Used alternate way to incorporate CDTS to remove the soyutils.js file.
Removed the static CDTS files as they didn't appear to be doing anything.

Testing

Go to https://ramp4-pcar4.github.io/story-ramp/cdts/index-ca-en.html#/en/00000000-0000-0000-0000-000000000000 and https://ramp4-pcar4.github.io/story-ramp/cdts/index-ca-fr.html#/fr/00000000-0000-0000-0000-000000000000
Ensure that everything (including the WET template stuff) is respectful.

This change is

looks like a possible css clash? second slide on https://ramp4-pcar4.github.io/story-ramp/cdts/index-ca-en.html#/en/00000000-0000-0000-0000-000000000000

Rebased.


Documentation landing page cards wrongly formatted

Remove second hyperlink since it is not needed

This is fixed via the ansys-sphinx-theme --> Closing
Release is needed (fix is in dev right now). Pinging @AlejandroFernandezLuces

Release done 🙂

Thanks @AlejandroFernandezLuces!


Full cart and checkout component

User Story
As a user, I want to be able to see the cart and checkout process as a standalone page (or pages) because that's what I'm used to from other e-commerce shops.
Description & Motivation

Online shoppers are not accustomed to using a "mini checkout" the way it's implemented with the CIF Components. They're used to seeing a full-page to go through the checkout process.
Having the checkout process on a separate template that's more minimal with fewer distractions may also help with conversions.

Deliverables
Add a new "full checkout" component (potentially based on the existing mini-cart component) that can be dropped on a page on its own and guide the user through the checkout process. To allow for more flexibility and extensibility, there should also be a separate "full cart" component.
Acceptance Criteria

The full cart and full checkout components should have feature parity to the existing mini-cart component.
The cart/checkout pages should be configurable similar to how the category/product/search pages are configurable.

Thanks @paulrohrbeck this is actually planned for later 2021 (CIF-1465). (cc @martinbuergi )


Setting colors on app initial start

On app initial start (e.g newly installed or upon data cleared) the colors i set as "defaultValue" are not applied till I go to the settings page where color is set. How can I make the colors stick on a fresh install?
Thanks

I did some more digging, and the issue is not related to your library, but my preference not being set on create. Great library by the way!!!


Change default log level to warn

as info level causes too much of logs produced (400+ Mb for ~2 hours)

i'd prefer try downgrading some info/warning logs first, as missing info logs impacts debugging ability in devnet.
do you have data regarding the distribution of info logs? i am looking for something like "X% come from module A and Y% from module B".

@countvonzero here is INFO log lines distribution by module (600+ Mb):
proposalListener: 660587 (45.90%)
SVM: 454086 (31.55%)
mesh: 64318 (4.47%)
trtl: 58913 (4.09%)
sync: 48928 (3.40%)
atxDb: 35184 (2.44%)
....

proposalListener and SVM make most of it. And here is a distribution of messages for those 2 modules:
proposalListener:
[proposalListener] new ballot: 220149 (33.33%)
[proposalListener] ballot eligibility verified: 220148 (33.33%)
[proposalListener] processing ballot: 220020 (33.31%)
[proposalListener] processing proposal: 135 (0.02%)
...

SVM:
[SVM] update account: 220096 (48.47%)
[SVM] update rewards: 220090 (48.47%)
[SVM] apply layer to vm: 6947 (1.53%)
...

please let me know if anything of above can be removed.

here is INFO log line count distribution by module (600+ Mb):

is line count proportional to data size? i know some line log heavier than others. like when we receive a proposal/ballot, we call log.inline() on the whole object. that log line should have more data than other line.

please let me know if anything of above can be downgraded.

i cannot tell you which module can be downgraded. the point is that a sweeping measure at log level/module granularity does not work here. i'll recommend looking at the top offender modules/log lines here and see if it make sense to downgrade them.

some ideas:

the log.inline() on atx/ballot/proposal/tx can probably be downgraded. in these logs, logging a simple ID is probably sufficient.

the logged IDs (atx/proposal/ballot/block/tx) can be a short string.

in each gossip workflow, we'll have multiple layers of logging saying the same thing. take atx for example, we have

got new atx 5b2b9df516
validating nipost
processing atx
atx is valid
finished storing atx in epoch
stored and propagated new syntactically valid atx

this is overly verbose for one single object. similar for other objects (propsal/ballot/block/tx)

most of the SVM log can be downgraded (per account/reward update)

hare has tons of WARN/INFO log even before the node is synced (hare shouldn't be participating before the node is synced)

these are the low hanging fruits i can think of. cc @dshulyak

@countvonzero good point re: data size, cheers. Top modules by log size (in bytes) looks as follows:
proposalListener: 375586070 (62.63%)
SVM: 143314358 (23.90%)
atxDb: 19471943 (3.25%)
trtl: 18539898 (3.09%)
mesh: 15764322 (2.63%)
sync: 13190092 (2.20%)
...

and then top messages (by size in bytes) for top 2 modules (proposalListener and SVM):
[proposalListener] new ballot: 227067124 (60.46%)
[proposalListener] ballot eligibility verified: 80785116 (21.51%)
[proposalListener] processing ballot: 67544712 (17.98%)
[proposalListener] new proposal: 154288 (0.04%)
...
[SVM] update rewards: 72265308 (50.42%)
[SVM] update account: 67506049 (47.10%)
[SVM] rewards info for layer: 1819234 (1.27%)
...

@countvonzero

hare has tons of WARN/INFO log even before the node is synced (hare shouldn't be participating before the node is synced)

Did the node try to execute Hare or only the logging part somehow got executed?

@countvonzero

hare has tons of WARN/INFO log even before the node is synced (hare shouldn't be participating before the node is synced)

Did the node try to execute Hare or only the logging part somehow got executed?

the consensus process doesn't not start until the node is synced. so no, hare is not executed.
but it appears that hare is listening to hare message all the time, producing a lot of spam because it cannot verify the hare messages in the network.

Thx.

the consensus process doesn't not start until the node is synced. so no, hare is not executed. but it appears that hare is listening to hare message all the time, producing a lot of spam because it cannot verify the hare messages in the network.

maybe not all the time, but definitely minutes before the node is synced.
we may want to start exploring the sampling feature of zapcore for some of the modules so that only every Mth log is preserved.

i thought about it changing it to warn only for smapp users

svm logs

they were downgraded in the new vm version

i want to point out that we can't just drop log.Inline. this information is absolutely required to understand what is going on with the protocol. one option is to drop it for info level, but keep it for debug.
we can enable debug level for each module separately, but in order to do that we need to make debug actually readable in that module, right now debug level mostly just spits overwhelming amount of info.
the bottomline is that it won't be possible to merge this change if it removes log.Inline without adjusting logging more systematically

@evt lets restore inline for ballot and merge this change

bors merge


Update Accula SARS-Cov-2 Test* Test Time to 30 Minutes

Ming called the manufacturer and confirmed this is a 30-minute test. Can we update the time on this?

All set!


fence.i decode bugfix

Decoder doesn't recognize the full pattern of fence.i
According to the ISA manual: Page 32 (https://drive.google.com/file/d/1s0lZxUZaa7eV_O0_WsZzaurFLLww7ou5/view)
Implementations should ignore some number of bits -- BP instead only recognized zeros in their places (Page 131 above for the actual pattern)
The unused fields in the FENCE.I instruction, imm[11:0], rs1, and rd, are reserved for finer-grain
fences in future extensions. For forward compatibility, base implementations shall ignore these
fields, and standard software shall zero these fields.

Nice, thanks


Dataset problem

Hi,mevah,Thanks for your work,and what is frankfurt? How should i get it ?

There is no  frankfurt floder in gtFine

The frankfurt folder is not directly under the gtFine directory, but it is rather under the gtFine/val subdirectory.

O，thanks，but there is no frankfurt folder in gtFine/val,
------------------ 原始邮件 ------------------
发件人: "Ayca<EMAIL_ADDRESS>发送时间: 2020年4月14日(星期二) 下午2:13
收件人<EMAIL_ADDRESS>抄送: "张晓峰南京邮电大学"<512631874<EMAIL_ADDRESS>主题: Re: [mevah/ExPGAN] Dataset problem (#8)
The frankfurt folder is not directly under the gtFine directory, but it is rather under the gtFine/val subdirectory.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I downloaded checked the current version of the dataset on the Cityscapes website, and it includes the frankfurt folder as well.
I recommend downloading the gtFine_trainvaltest.zip file again from the following link:
https://www.cityscapes-dataset.com/file-handling/?packageID=1
But in any case, we did not use that folder for training, and it was used only for the evaluation and comparison of the performances across different models. Since the image sequences in the original test directory did not have ground truth pixel-level segmentation information, we selected one of the val folders (frankfurt) to be the final test set. So you don't have to worry about that folder.

OK，thanks a lot！
------------------ 原始邮件 ------------------
发件人: "Ayca<EMAIL_ADDRESS>发送时间: 2020年4月14日(星期二) 下午2:30
收件人<EMAIL_ADDRESS>抄送: "张晓峰南京邮电大学"<512631874<EMAIL_ADDRESS>主题: Re: [mevah/ExPGAN] Dataset problem (#8)
I downloaded checked the current version of the dataset on the Cityscapes website, and it includes the frankfurt folder as well.
I recommend downloading the gtFine_trainvaltest.zip file again from the following link:
https://www.cityscapes-dataset.com/file-handling/?packageID=1
But in any case, we did not use that folder for training, and it was used only for the evaluation and comparison of the performances across different models. Since the image sequences in the original test directory did not have ground truth pixel-level segmentation information, we selected one of the val folders (frankfurt) to be the final test set. So you don't have to worry about that folder.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Merge Staging

What is this?
many things
Why?
to have those many things in
How did you test it works without regressions?
If this is a new feature what may a critical error look like?
Things to consider to not repeat mistakes we've learned from many times

[ ] If critical errors fire do we ping team in some obvious way (e.g., slack)?
[ ] Are there debug logs + a way to see these logs if we need to debug?
[ ] Is this documented enough a dev could work on this code without getting stuck or having to ping you?

Confirming deployed manually as 0.2.0


fix: hiro api testnet url path

@alter-eggo I think this needs to be the old path? It seems out of sync with the extension?

Summary by CodeRabbit

Bug Fixes

Updated the testnet API base URL to ensure connectivity and functionality.

I'm not sure you can post new transactions to the old endpoint? 🤔 I have no balance with the new one, but no ability to broadcast txs using the old path.

Issue: https://github.com/leather-wallet/extension/issues/5529


Change Textobj: lineCharacterwise and entireBuffer to maintain cursor positions

Change requested
I tried this plug in with:
-- Own map preserves the cursor position
-- vim.keymap.set({ "o", "x" }, "al", '<cmd>lua require("various-textobjs").lineCharacterwise("outer")<CR>')
-- vim.keymap.set({ "o", "x" }, "il", '<cmd>lua require("various-textobjs").lineCharacterwise("inner")<CR>')

-- Own way prefers the position of the cursor on copy all
-- vim.keymap.set({ "o", "x" }, "A", '<cmd>lua require("various-textobjs").entireBuffer()<CR>')

But reverted to my own keymaps because they maintain the cursor position on copy the entire buffer or copy a line. I find it much less jarring, maybe others will benefit from this upgraded behavior?
vim.keymap.set({"x", "o"}, "il", ":<C-U>normal! ^vg_<CR>", {noremap = true})
vim.keymap.set({"x", "o"}, "al", ":<C-U>normal! 0vg_<CR>", {noremap = true})

-- utils.lua
-- Text object to select the whole buffer, used in normal/visual modes
function M.text_object_all()
    vim.g.cursor_position = vim.fn.winsaveview()
    vim.cmd("normal! ggVG")
    local pattern = "[cd]" -- 'c' or 'd'
    if not string.find(vim.v.operator, pattern) then
        -- Running the command straight does not work, have to pass it through feedkeys or defer it
        vim.defer_fn(
            function()
                vim.fn.winrestview(vim.g.cursor_position)
            end,
            0
        )
    end
end

-- Some other file
vim.keymap.set("o", "A", utils.text_object_all, {})

Sample Text
No change, just maintain the cursor position when copying a line or the entire buffer
Checklist

[X] The textobj would be useful to more users than just me. (You can use the API to create custom textobj.)
[X] This is a feature request to change an existing textobject, not a bug report. (Use the bug report form for those.)

I think it makes more sense to have the stickiness (= keeping the cursor position) be something managed by the operator, not by the text object. That way, it works independent of any text object.
You can achieve sticky yank operations either by using the yanky.nvim, or by using these. They work reliably with any text object, be it this plugin, a different plugin, or the builtin vim motions.
local cursorPreYank
vim.keymap.set({ "n", "x" }, "y", function()
	cursorPreYank = vim.api.nvim_win_get_cursor(0)
	return "y"
end, { desc = "Sticky Yank", expr = true })
vim.keymap.set("n", "Y", function()
	cursorPreYank = vim.api.nvim_win_get_cursor(0)
	return "y$"
end, { desc = "Sticky Yank", expr = true })

vim.api.nvim_create_autocmd("TextYankPost", {
	callback = function()
		if vim.v.event.operator == "y" and cursorPreYank then
			vim.api.nvim_win_set_cursor(0, cursorPreYank)
		end
	end,
})


Provide more info when waiting the dataplane

output:
https://logserver.rdoproject.org/14/214/4279db322a48ef29101e03c12727b72c4b56afa4/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/79ac2da/controller/data-plane-adoption-tests-repo/data-plane-adoption/tests/logs/test_with_ceph_out_2023-12-05T18:26:46EST.log
the idea is to show all the AEE pods, so that when it fails it will be clear which service failed

recheck

TASK [dataplane_adoption : wait for dataplane node set to be ready] ************
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (25 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (24 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (23 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (22 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (21 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (20 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (19 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (18 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (17 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (16 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (15 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (14 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (13 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (12 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (11 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (10 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (9 retries left).
FAILED - RETRYING: [localhost]: wait for dataplane node set to be ready (8 retries left).
changed: [localhost] => {"attempts": 19, "changed": true, "cmd": "set -euxo pipefail\n\n\nNODESET_NAME=openstack\nDEPLOYMENT_NAME=openstack\necho \"========= AEE Pods =========\"\noc get pod -l osdpd=${DEPLOYMENT_NAME}\nLAST_SERVICE_NAME=$(oc get osdpns ${NODESET_NAME} -o jsonpath='{.spec.services}' | jq -r last)\necho \"========= Last service name: ${LAST_SERVICE_NAME} =========\"\nLAST_SERVICE_POD=$(oc get pod -l job-name=${LAST_SERVICE_NAME}-${DEPLOYMENT_NAME} -o name)\necho \"========= Last service POD name: ${LAST_SERVICE_POD} =========\"\noc get ${LAST_SERVICE_POD} -o jsonpath='{.status.phase}{\"\\n\"}' | grep Succeeded\noc get osdpd openstack -o jsonpath='{.status.deployed}{\"\\n\"}' | grep true\n", "delta": "0:00:01.150474", "end": "2023-12-05 19:05:15.465982", "msg": "", "rc": 0, "start": "2023-12-05 19:05:14.315508", "stderr": "+ NODESET_NAME=openstack\n+ DEPLOYMENT_NAME=openstack\n+ echo '========= AEE Pods ========='\n+ oc get pod -l osdpd=openstack\n++ oc get osdpns openstack -o 'jsonpath={.spec.services}'\n++ jq -r last\n+ LAST_SERVICE_NAME=ovn\n+ echo '========= Last service name: ovn ========='\n++ oc get pod -l job-name=ovn-openstack -o name\n+ LAST_SERVICE_POD=pod/ovn-openstack-66df9\n+ echo '========= Last service POD name: pod/ovn-openstack-66df9 ========='\n+ oc get pod/ovn-openstack-66df9 -o 'jsonpath={.status.phase}{\"\\n\"}'\n+ grep Succeeded\n+ grep true\n+ oc get osdpd openstack -o 'jsonpath={.status.deployed}{\"\\n\"}'", "stderr_lines": ["+ NODESET_NAME=openstack", "+ DEPLOYMENT_NAME=openstack", "+ echo '========= AEE Pods ========='", "+ oc get pod -l osdpd=openstack", "++ oc get osdpns openstack -o 'jsonpath={.spec.services}'", "++ jq -r last", "+ LAST_SERVICE_NAME=ovn", "+ echo '========= Last service name: ovn ========='", "++ oc get pod -l job-name=ovn-openstack -o name", "+ LAST_SERVICE_POD=pod/ovn-openstack-66df9", "+ echo '========= Last service POD name: pod/ovn-openstack-66df9 ========='", "+ oc get pod/ovn-openstack-66df9 -o 'jsonpath={.status.phase}{\"\\n\"}'", "+ grep Succeeded", "+ grep true", "+ oc get osdpd openstack -o 'jsonpath={.status.deployed}{\"\\n\"}'"], "stdout": "========= AEE Pods =========\nNAME                                       READY   STATUS      RESTARTS   AGE\nconfigure-network-openstack-gdndp          0/1     Completed   0          13m\nconfigure-os-openstack-ntx8x               0/1     Completed   0          10m\ndownload-cache-openstack-qxgh9             0/1     Completed   0          17m\ninstall-os-openstack-s95tx                 0/1     Completed   0          11m\nlibvirt-openstack-586pl                    0/1     Completed   0          5m44s\nnova.compute.extraconfig-openstack-88f8d   0/1     Completed   0          3m18s\novn-openstack-66df9                        0/1     Completed   0          2m10s\nrun-os-openstack-k6xc6                     0/1     Completed   0          8m15s\nvalidate-network-openstack-nts9f           0/1     Completed   0          12m\n========= Last service name: ovn =========\n========= Last service POD name: pod/ovn-openstack-66df9 =========\nSucceeded\ntrue", "stdout_lines": ["========= AEE Pods =========", "NAME                                       READY   STATUS      RESTARTS   AGE", "configure-network-openstack-gdndp          0/1     Completed   0          13m", "configure-os-openstack-ntx8x               0/1     Completed   0          10m", "download-cache-openstack-qxgh9             0/1     Completed   0          17m", "install-os-openstack-s95tx                 0/1     Completed   0          11m", "libvirt-openstack-586pl                    0/1     Completed   0          5m44s", "nova.compute.extraconfig-openstack-88f8d   0/1     Completed   0          3m18s", "ovn-openstack-66df9                        0/1     Completed   0          2m10s", "run-os-openstack-k6xc6                     0/1     Completed   0          8m15s", "validate-network-openstack-nts9f           0/1     Completed   0          12m", "========= Last service name: ovn =========", "========= Last service POD name: pod/ovn-openstack-66df9 =========", "Succeeded", "true"]}

https://logserver.rdoproject.org/14/214/4279db322a48ef29101e03c12727b72c4b56afa4/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/79ac2da/controller/data-plane-adoption-tests-repo/data-plane-adoption/tests/logs/test_with_ceph_out_2023-12-05T18:26:46EST.log


.multirust has moved back to home directory

The .multirust directory was moved to %localappdata% on windows, to follow platform conventions, and to avoid cluttering the home directory, but it has since been moved back.
I think there was also a plan to unify the .multirust and .cargo directories too?

For consistency with where .cargo lives, .multirust is now in %USERPROFILE%\.multirust. If we want to change conventions here it needs to be done in both cargo and rustup.
There's no plan to unify .multirust and .cargo exactly. ~/.cargo/bin is where the rustup bins are installed - for consistency with other rust bins - but other than that rustup doesn't care about `~/.cargo.

OK, this should be tied to rust-lang/cargo#1976 then.


firewall configuration

hi. add the ability to change the firewall configuration for up\down in the wg config.

To add further context, do you mean you want to be able to change the firewall rules, e.g. the PreUp and PostDown rules from within WGDashboard?
Otherwise the configured wireguard configuration directory hosts all the .conf files waiting to be changed if needed!

To add further context, do you mean you want to be able to change the firewall rules, e.g. the PreUp and PostDown rules from within WGDashboard?
Otherwise the configured wireguard configuration directory hosts all the .conf files waiting to be changed if needed!

@DaanSelen  Honestly I'm starting to think if allow WGDashboard to set Post&Pre Up/Down is safe to do so since there's no safeguard on what command it will run, what do you think?

To add further context, do you mean you want to be able to change the firewall rules, e.g. the PreUp and PostDown rules from within WGDashboard?
Otherwise the configured wireguard configuration directory hosts all the .conf files waiting to be changed if needed!

@DaanSelen Honestly I'm starting to think if allow WGDashboard to set Post&Pre Up/Down is safe to do so since there's no safeguard on what command it will run, what do you think?

My opinion on this matter is, to add an "advanced" menu perhaps, I'd like a in-browser editor which just opens the file as a text editor, but of course this is no guarantee that everything is working as intended.
To make it user friendly perhaps make a template which is copied over with a couple different variables which makes the interface itself functional at the least.
If you have more questions, ask them!

To add further context, do you mean you want to be able to change the firewall rules, e.g. the PreUp and PostDown rules from within WGDashboard?
Otherwise the configured wireguard configuration directory hosts all the .conf files waiting to be changed if needed!

@DaanSelen Honestly I'm starting to think if allow WGDashboard to set Post&Pre Up/Down is safe to do so since there's no safeguard on what command it will run, what do you think?

My opinion on this matter is, to add an "advanced" menu perhaps, I'd like a in-browser editor which just opens the file as a text editor, but of course this is no guarantee that everything is working as intended.
To make it user friendly perhaps make a template which is copied over with a couple different variables which makes the interface itself functional at the least.
If you have more questions, ask them!
I think it's enough to add 2 text fields, for interface settings
1 for postup;
2 for predown'
Where there will simply be a line with the default rules.
And if necessary, someone will change it.
iptables -t nat -A POSTROUTING -o ip route | awk '/default/ {print $5; exit}'-j MASQUERADE; ip rule add fromip addr show $(ip route | awk '/default/ { print $5 }') | grep "inet" | grep -v "inet6" | head -n 1 | awk '/inet/ {print $2}' | awk -F/ '{print $1}' table main; etc

2 Text fields for PreUp and for PostDown are also fine, and @andrex4k what do you mean with:
iptables -t nat -A POSTROUTING -o ip route | awk '/default/ {print $5; exit}'-j MASQUERADE; ip rule add fromip addr show $(ip route | awk '/default/ { print $5 }') | grep "inet" | grep -v "inet6" | head -n 1 | awk '/inet/ {print $2}' | awk -F/ '{print $1}' table main; etc

2 текстовых поля для предварительной настройки и для последующей настройки также в порядке, и @andrex4k что вы имеете в виду под:
iptables -t nat -A POSTROUTING -o ip route | awk '/default/ {print $5; exit}'-j MASQUERADE; ip rule add fromip addr show $(ip route | awk '/default/ { print $5 }') | grep "inet" | grep -v "inet6" | head -n 1 | awk '/inet/ {print $2}' | awk -F/ '{print $1}' table main; etc

This is just an example.

Like the Dockerfile in my fork: https://github.com/DaanSelen/WGDashboard/tree/main
Line 63:71?


Package react-native-webview has been ignored because it contains invalid configuration

Bug description:

I am trying to use react-native-webview and following step. But it doesn't work.
yarn add react-native-webview
cd ios && pod install && cd .. # CocoaPods on iOS needs this extra step
There is problem.

To Reproduce:

Expected behavior:

Screenshots/Videos:

Environment:

OS: macOS
OS version: 12.3
react-native version: 0.67.4
react-native-webview version: 11.18.0

BTW duplicate of issue 2426

same problem for me on macOS
arn run v1.22.17
$ react-native run-android
warn Package react-native-webview has been ignored because it contains invalid configuration. Reason: Cannot find module 'react-native-test-app/package.json'
Require stack:
- /Users/midknight/epitech/area/mobile-app/node_modules/react-native-webview/react-native.config.js
- /Users/midknight/epitech/area/mobile-app/node_modules/cosmiconfig/node_modules/import-fresh/index.js
- /Users/midknight/epitech/area/mobile-app/node_modules/cosmiconfig/dist/loaders.js
- /Users/midknight/epitech/area/mobile-app/node_modules/cosmiconfig/dist/createExplorer.js
- /Users/midknight/epitech/area/mobile-app/node_modules/cosmiconfig/dist/index.js
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /Users/midknight/epitech/area/mobile-app/node_modules/react-native/cli.js
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 1017 file(s) to forward-jetify. Using 10 workers...
info JS server already running.
info Installing the app...

is it the same as #2421 ?

yes

To temporarly fix it, replace in your package.json this line "react-native-webview": "^11.18.0" by "react-native-webview": "11.17.2"

This error message typically occurs when the "react-native-webview" package is not properly configured in your project. To fix this issue, you can try the following steps:
Make sure that you have installed the "react-native-webview" package using npm or yarn.
Check that the package is correctly imported in your project.
If you are using a version of React Native that is less than 0.60, you need to link the "react-native-webview" package. You can do this by running the command "react-native link react-native-webview" in your project's root directory.
If you are using a version of React Native that is greater than or equal to 0.60, linking is not necessary. So, you can make sure that you are using the latest version of react-native-webview.
If none of these steps work, you can try uninstalling and reinstalling the package, or you can check if there are any other dependencies causing conflicts.
Make sure that you are using the latest version of React Native.
If none of the above steps work, please share the version of react-native and react-native-webview you are using.
Support my blog: https://Nairobinewsnow.com