Tools: Interoperability test suite: Added simple interface chip tests / checks

Description
This new functionality allows users to perform simple interface chip tests / checks in order to determine if mbed device is in-line with various levels of mbed 2.0 / mbed-enabled compatibility.
Limitations

This feature only works with mbed-ls module and --auto switch. If mbed-ls is installed users can use new option --oper to force interoperability tests on all connected devices.
Interoperability test results can be imported only to JUnit. No HTML, JSON exporters yet. Feel free to add them.

New command line option --oper
New command line switch --oper=SCOPE comes with few flavors:

basic - check for basic compatibility.
mbed-enabled - set of checks for mbed-enabled standard compatibility.
Note: mbed-enabled standard is being developed now and requirements are not set in stone so
pedantic - set of detailed checks. Note: it is not yet implemented.
all - Run all checks / tests.

Add --report-junit=FILE_NAME to --auto --oper=SCOPE to export results to JUnit format output file.
To see all available interoperability test suite options use:
$ singletest.py --help
Usage: singletest.py [options]

This script allows you to run mbed defined test cases for particular MCU(s)
and corresponding toolchain(s).

 Use toolchains
                        names separated by comma, 'default' or 'all' to select
                        toolchains
  --oper=OPERABILITY_CHECKS
                        Perform interoperability tests between host and
                        connected mbed devices. Available test scopes are:
                        'mbed-enabled','all','basic'
.
.
.

Examples:
New interoperability test suite is called by adding --oper switch to singletest.py --auto command:
$ singletest.py --auto --oper=basic

or
$ singletest.py --auto --oper=mbed-enabled

or
$ singletest.py --auto --oper=all

Examples:
FRDM-K64F interoperability basic test suite portfolio (tests/checks examples):
$ singletest.py --auto --oper=basic
MBEDLS: Detecting connected mbed-enabled devices...
MBEDLS: Detected K64F, port: COM61, mounted: I:
MBEDLS: Detected K64F, port: COM61, mounted: I:
Running interoperability test suite, scope 'basic'
+----------+----------------------+--------+-------+------------------------------------------------+
| Platform | Test Case            | Result | Scope | Description                                    |
+----------+----------------------+--------+-------+------------------------------------------------+
| K64F     | FILE_EXIST(MBED.HTM) | PASS   | basic | File 'I:mbed.htm' exists                       |
| K64F     | TARGET_ID            | PASS   | basic | TargetID '02400203D94B0E7724B7F3CF' found      |
| K64F     | TARGET_ID_DECODE     | PASS   | basic | TargetID '0240' decoded as 'K64F'              |
| K64F     | TARGET_ID_MATCH      | PASS   | basic | TargetID (USBID) and TargetID (mbed.htm) match |
+----------+----------------------+--------+-------+------------------------------------------------+

FRDM-K64F interoperability mbed-enabled test suite portfolio (tests/checks examples):
$ singletest.py --auto --oper=mbed-enabled
MBEDLS: Detecting connected mbed-enabled devices...
MBEDLS: Detected K64F, port: COM61, mounted: I:
MBEDLS: Detected K64F, port: COM61, mounted: I:
Running interoperability test suite, scope 'mbed-enabled'
+----------+-------------------------+--------+--------------+-------------------------------------------------------------------+
| Platform | Test Case               | Result | Scope        | Description                                                       |
+----------+-------------------------+--------+--------------+-------------------------------------------------------------------+
| K64F     | FILE_EXIST(DETAILS.TXT) | ERROR  | mbed-enabled | File 'I:DETAILS.TXT' not found                                    |
| K64F     | FILE_EXIST(MBED.HTM)    | PASS   | basic        | File 'I:mbed.htm' exists                                          |
| K64F     | FILE_EXIST(MBED.HTM)    | PASS   | mbed-enabled | File 'I:mbed.htm' exists                                          |
| K64F     | TARGET_ID               | PASS   | basic        | TargetID '02400203D94B0E7724B7F3CF' found                         |
| K64F     | TARGET_ID_DECODE        | PASS   | basic        | TargetID '0240' decoded as 'K64F'                                 |
| K64F     | TARGET_ID_LEN           | PASS   | mbed-enabled | TargetId (USBID) '02400203D94B0E7724B7F3CF' is 24 chars long      |
| K64F     | TARGET_ID_LEN           | PASS   | mbed-enabled | TargetId (mbed.htm) '02400203D94B0E7724B7F3CF' is 24 chars long   |
| K64F     | TARGET_ID_MATCH         | PASS   | basic        | TargetID (USBID) and TargetID (mbed.htm) match                    |
| K64F     | FILE_EXIST(FAIL.TXT)    | INFO   | mbed-enabled | File 'I:FAIL.TXT' not found                                       |
| K64F     | FW_HASH_SEC             | INFO   | mbed-enabled | TargetId (USBID) Hash of secret is 'D94B0E7724B7F3CF'             |
| K64F     | FW_HASH_SEC             | INFO   | mbed-enabled | TargetId (mbed.htm) Hash of secret is 'D94B0E7724B7F3CF'          |
| K64F     | FW_PLAT_CODE            | INFO   | mbed-enabled | TargetId (USBID) Platform Code is '40'                            |
| K64F     | FW_PLAT_CODE            | INFO   | mbed-enabled | TargetId (mbed.htm) Platform Code is '40'                         |
| K64F     | FW_VEN_CODE             | INFO   | mbed-enabled | TargetId (USBID) Vendor Code is '02'                              |
| K64F     | FW_VEN_CODE             | INFO   | mbed-enabled | TargetId (mbed.htm) Vendor Code is '02'                           |
| K64F     | FW_VER                  | INFO   | mbed-enabled | TargetId (USBID) Firmware Version is '0203'                       |
| K64F     | FW_VER                  | INFO   | mbed-enabled | TargetId (mbed.htm) Firmware Version is '0203'                    |
| K64F     | FW_VER_STR              | INFO   | mbed-enabled | TargetId (USBID) Version String is 0240.0203.D94B0E7724B7F3CF     |
| K64F     | FW_VER_STR              | INFO   | mbed-enabled | TargetId (mbed.htm) Version String is 0240.0203.D94B0E7724B7F3CF  |
+----------+-------------------------+--------+--------------+-------------------------------------------------------------------+

This is awesome!!

Yes, this is needed !
My 5 cents: singletest is becoming too big on arguments with various functionality, shall we start thinking about simplifying it ?

@0xc0170 : Singletest.py is just a CLI app. So it has already too many parameters :P
But good news is I wrote this piece of code as separate Python module so we can always decouple in the future with minimal effort.

Hi.
I meet an error with this function.
My target id is 48 chars long and your test tool expected 24 chars.
OK, I look at here (https://github.com/ARMmbed/mbed-ls#targetid-as-device-unique-identifier)
"Should be longer than four ASCII characters (two bytes of hex data)"
Sorry but I do not understand why target id should need be 24 chars long.
Thanks

OK, I look at here (https://github.com/ARMmbed/mbed-ls#targetid-as-device-unique-identifier)
"Should be longer than four ASCII characters (two bytes of hex data)"
Sorry but I do not understand why target id should need be 24 chars long.

cc @bridadan @sg-

This functionality (interoperability tests) in the codebase has existed for quite some time unmaintained, so there may be outstanding issues with it.

OK, I look at here (https://github.com/ARMmbed/mbed-ls#targetid-as-device-unique-identifier)
"Should be longer than four ASCII characters (two bytes of hex data)"
Sorry but I do not understand why target id should need be 24 chars long.

I did not write this requirement, however the motivation behind this is to create a sufficiently unique string that can be used to uniquely identify the mbed. This is necessary so you can use mbed enabled boards in large scale testing setups.

@bridadan : Thanks for your reply. I think my target id is global uniquely


Add isRequestOk to render callback

Atm, to catch an error you must do:
if (error || (response && !response.ok) {}

This will make it so you can do:
if (error || !isResponseOk) {}

Small change but I think folks will find it useful.
//cc @alansouzati @marlonpp

Mmm...gonna hold off on this for now. The new guide ( #112 ) gives a good indication of what to do. I don't necessarily think that this additional attribute helps too much.
I'm open to this change, though! Give the initial comment a :+1: if you'd like to see this introduced.


[terraform-ibm-observability-da] Add a test to test existing resources

Add a test to test the following 2 use cases:

using existing COS and COS buckets
using existing COS and KMS key (so the DA creates new COS bucket and encrypts them with an existing KMS key)

Take the same approach that was taken in the SCC DA test -> https://github.com/terraform-ibm-modules/terraform-ibm-scc-da/blob/be22e36f2ad23a26af718d4a34b65f9b821a6ca7/tests/pr_test.go#L112

For the first test is it supposed to be one bucket or multiple buckets for one or all the services (e.g. log archive, and activity tracker)?

Found a bug in Instances solution where the bucket_config_map is being set to null when existing resources are used, however its length is checked several times causing errors. A fix will be addressed in the PR.

PR has been merged. Closing issue.


Add ONNX Gather op support

Pull Request Template
Checklist

[x] Confirm that run-checks script has been executed.

Related Issues/PRs
#600
Changes
Added support for ONNX Gather op
Testing
End to end test in burn-import/onnx-tests/tests/onnx_tests.rs and codegen test in burn-import/src/burn/node/gather.rs

OK. I have rebased so that candle-core is fixed on CI.

OK. CI is passing now.
@nathanielsimard ready to be merged.

@CohenAriel Thank you for your contribution! It's merged.


Test release process by publishing compiler and Miden SDK crates

### Tasks (according to CONTRIBUTING.md)
- [x] Run `release-plz update` in the repo root folder to update the compiler crates versions and generate changelogs.
- [x] Run `release-plz update` in the `sdk` folder to update the SDK crates versions and generate changelogs.
- [x] Create a release PR naming the branch with the `release-plz-` suffix (its important to use this suffix to trigger the crate publishing on CI in step 4).
- [x] Review the changes in the release PR, commit edits if needed and merge it into the main branch.
- [ ] The CI will automatically run `release-plz release` after the release PR is merged to publish the new versions to crates.io.
- [ ] Set a git tag for the published crates to mark the release.

@bitwalker Well, the first attempt to publish https://github.com/0xPolygonMiden/compiler/pull/249#pullrequestreview-2186336971 is failed:
error: failed to publish to registry at https://crates.io/

    Caused by:
      the remote server responded with an error (status 400 Bad Request): The following category slugs are not currently supported on crates.io: Compilers

      See https://crates.io/category_slugs for a list of supported slugs.

I've run the --dry-run (I should've done it earlier 🤦)  and besides that, we're going to need to specify the version along the path for all the deps:
  2024-07-19T13:34:37.502097Z ERROR  failed to release package

Caused by:
    failed to publish midenc-session:     Updating crates.io index
    error: all dependencies must have a version specified when publishing.
    dependency `midenc-hir-symbol` does not specify a version
    Note: The published dependency will use the version from crates.io,
    the `path` specification will be removed from the dependency declaration.

I'm making a new release PR with these fixes.

The latest publishing attempt - https://github.com/0xPolygonMiden/compiler/actions/runs/10043779504/job/27757299114
Issues:

miden-assembly does not have version set;
git tags are pushed despite the git_tag_enable=false in the release-plz.toml.

We cannot set the version for VM crates in our deps since we depend on the unreleased version of the VM (v.0.10.0) on the following features in particular:

https://github.com/0xPolygonMiden/miden-vm/pull/1363
https://github.com/0xPolygonMiden/miden-vm/pull/1360

Which, in turn, depends on the assembler refactoring https://github.com/0xPolygonMiden/miden-vm/pull/1277, so backporting probably is not an option.
@bobbinth Do we have any ETA for the VM v.0.10.0 release? It seems that we can release only after the VM v.0.10.0 release.

@greenhat As far as I'm aware, if 0.10.0 is the version in the VM crates Cargo.toml, we can absolutely use that as the version in our Cargo.toml if we're using a git dependency, since that's what the version must match, not what is currently published to crates.io - at least as far as I understand the Cargo resolver.
Does it actually raise an error if you try to depend on a crate in a git repo which hasn't been published to crates.io? That doesn't seem right.

@greenhat As far as I'm aware, if 0.10.0 is the version in the VM crates Cargo.toml, we can absolutely use that as the version in our Cargo.toml if we're using a git dependency, since that's what the version must match, not what is currently published to crates.io - at least as far as I understand the Cargo resolver.

Yes, it should work when you are building locally. However, publishing to crates.io will use the registry version. In our case, it'd be 0.10.0, which has not yet been published on crates.io. See https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#multiple-locations :
It is possible to specify both a registry version and a git or path location. The git or path dependency will be used locally (in which case the version is checked against the local copy), and when published to a registry like crates.io, it will use the registry version. Other combinations are not allowed.

Does it actually raise an error if you try to depend on a crate in a git repo which hasn't been published to crates.io? That doesn't seem right.

I haven't tried it yet because version 0.9.1(published) is set in the VM crates in the next branch of the VM repo. We can try to set it to 0.10.0 version in VM crates and try to publish our crates. From my experience and the Cargo book excerpt above it should raise an error.

@bobbinth Do we have any ETA for the VM v.0.10.0 release?

We'll publish v0.10 as soon as MAST refactoring of the assembler is done. There are probably 3 - 4 PRs let on this though - so, maybe some time closer to the end of next week.
If we do publish compiler crates using git dependencies, we should make sure to reference a specific commit rather than the next branch as I'm anticipating some breaking changes in the assembler between now and v0.10 release.

@bobbinth Do we have any ETA for the VM v.0.10.0 release?

We'll publish v0.10 as soon as MAST refactoring of the assembler is done. There are probably 3 - 4 PRs let on this though - so, maybe some time closer to the end of next week.
If we do publish compiler crates using git dependencies, we should make sure to reference a specific commit rather than the next branch as I'm anticipating some breaking changes in the assembler between now and v0.10 release.

I don't think git dependency will work for a published crate. Do you mind if I make a PR to the VM repo and set the version of VM crates to 0.10.0 to test it?
We could do a "soft" release while we're waiting for the VM v0.10 release.  By "soft", I mean that instead of installing our extension via
cargo install cargo-miden

a user will need to use our repo and run
cargo install --git https://github.com/0xPolygonMiden/compiler cargo-miden

Do you mind if I make a PR to the VM repo and set the version of VM crates to 0.10.0 to test it?

That would be great!

Confirmed. The last publishing attempt https://github.com/0xPolygonMiden/compiler/actions/runs/10195526684/job/28204408562 failed due to the VM crates for version 0.10.0 are not found on crates.io:
  2024-08-01T09:16:58.465701Z ERROR  failed to release package

Caused by:
    failed to publish midenc-hir:     Updating crates.io index
       Packaging midenc-hir v0.0.1 (/home/runner/work/compiler/compiler/hir)
       Verifying midenc-hir v0.0.1 (/home/runner/work/compiler/compiler/hir)
        Updating crates.io index
    error: failed to verify package tarball

    Caused by:
      failed to select a version for the requirement `miden-assembly = "^0.10"`
      candidate versions found which didn't match: 0.9.2, 0.9.1, 0.9.0, ...
      location searched: crates.io index
      required by package `midenc-hir v0.0.1 (/home/runner/work/compiler/compiler/target/package/midenc-hir-0.0.1)`

I suppose we will publish a release after VM v0.10.0 is published then.

@bobbinth Could you please create two new crates at crates.io:

midenc-runner new crate for the VM executor;
miden-base-sys new crate for the rollup part of the SDK instead of miden-tx-kernel-sys which can be deleted;

Thanks!

midenc-runner was renamed midenc-debug FYI

Both crates (1, 2) are now on crates.io.

@bobbinth Could you please create the new crate at crates.io for miden-sdk-alloc? Thanks!

@bobbinth Could you please create the new crate at crates.io for miden-sdk-alloc? Thanks!

Done! (here).

The publishing test completed successfully - https://github.com/0xPolygonMiden/compiler/actions/runs/10611124186/job/29409979512


Common config

So this is my idea of the configuration done right :-) It's gonna change a bit with my device_platforms PR, but this is it for now.
This PR replaces #11 as it was a mess when #10 got pulled in.
@alexa-pi/coreteam What do you think?

Damn, branched off a wrong branch :-/


[mtoon] Outlines

https://github.com/vrm-c/vrm-specification/blob/master/specification/VRMC_materials_mtoon-1.0/README.md#outline
The spec mentions outlines typically being implemented in a separate pass rather than part of the same mtoon shader.
Maybe we can use an existing outline crate like https://github.com/komadori/bevy_mod_outline

done using bevy_mod_outline. its not quite the same as other VRM implementations but its a start, likely will have to write our own outline shader to get a better effect.


EIO: i/o error, write on beta 16

Hello,
Am getting a lot of
Error: EIO: i/o error, write
at Error (native)-
If i delete partitions on sdcard manually and try to write again sometimes is a hit or miss but error goes way.
Etcher version: beta16

Operating system and architecture: ubuntu 16.04
Do you see any meaningful error information on DevTools?

Can you provide more details about your SD card?
Is it possible it's a fake, or is faulty? Or if the SD card isn't faulty, perhaps your SD card-reader is faulty?
Have a look at http://oss.digirati.com.br/f3/ - if that reports errors with your SD card&reader combo then I don't think there's much that Etcher can do.
If you have multiple SD cards, or another SD reader, it's always worth swapping things about to see if that improves things :)

Yeah, it sounds like a faulty SDCard, or SDCard reader. Lets do some further investigation if this keeps failing after retrying with a different SDCard or reader.
As a side note, maybe we should intercept EIO error and output a more friendly message?

I believe this issue has been fixed with https://github.com/resin-io-modules/etcher-image-write/pull/73

in my case error has been solved.
note: Be sure that img file has been extract with 7zip.


feature: support dressing ui

Did you check the docs?

[X] I have read all the trouble.nvim docs

Is your feature request related to a problem? Please describe.
Hi, can we support dressing ui? instead of only bottom/top/left/right.
Describe the solution you'd like
support dressing ui instead of only bottom/top/left/right.
Describe alternatives you've considered
there are several ui library: dressing, noice, nui, etc. please support them.
Additional context
No response

Your request makes no sense. dressing.nvim overrides input  & select. Noice.nvim is something entirely different.
So no

hi, what about floating window?

Neither dressing.nvim, not noice.nvim expose API's or integration points for other plugins to provide floating windows.
I'm not interested in adding a floating window ui to trouble

Thanks for reply.


Microsoft.Web/sites@2022-09-01: Status Tracking Behaviour is not useful

Is your feature request related to a problem? Please describe.
When deploying an app (in this case a python app) to azure app services via bicep the script waits for the build, deployment and start of the application.
If the application is malfunctioning (not starting) the deployment process is waiting for it to recover (see below log). In case the app never recovers the script stops to wait after 12 minutes and continues.
This behaviour stalls the deployment and hinders a timely redeployment without an apparent benefit.
Describe the solution you'd like

Make the timeout configurable via a parameter or environment variable
(fail the deployment if status of the app does not start - probably also configurable)

Log:
$ azd deploy
Deploying services (azd deploy)
Deploying service backend
Deploying service backend (Copying deployment package)
Deploying service backend (Compressing deployment artifacts)
Deploying service backend (Uploading deployment package)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Running build process)
Deploying service backend (Starting runtime process, 0 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Starting runtime process, 1 in progress instances, 0 successful instances)
Deploying service backend (Deployment with tracking status failed to start within the allotted time.Resuming deployment without tracking status.)
Deploying service backend (Fetching endpoints for app service)
  (✓) Done: Deploying service backend
  - Endpoint: https://xxxxxxxxxxxxxxxxxx.azurewebsites.net/
SUCCESS: Your application was deployed to Azure in 12 minutes 17 seconds.
You can view the resources created under the resource group rg-businessgpt in Azure Portal:
https://portal.azure.com/#@/resource/subscriptions/xxxxxx/resourceGroups/xxxxxxxxxx/overview

Unfortunately our backend does not support timeout configuration for resource deployments and currently have no plan to add support for this.


Fix pull merge 500 error caused by git-fetch breaking behaviors

Fixes #8133
The git version before 1.8.4 would not update remote refs automatically.
That causes the following git-diff-tree command to get 'bad revision' errors.
Use refspec for git-fetch explicitly to avoid the problem.

Backport for v1.9

Original PR #8161


gopass: 1.9.2 -> 1.10.0

Motivation for this change
https://github.com/gopasspw/gopass/releases/tag/v1.10.0
Things done

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

[X] NixOS
[X] 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 nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Thanks for updating this. Note the breaking changes and the new binaries in $out/bin/. I'd suggest this patch in addition to the current:
diff --git c/pkgs/tools/security/gopass/default.nix i/pkgs/tools/security/gopass/default.nix
index 11337a49be4..5dbb0ce7fc6 100644
--- c/pkgs/tools/security/gopass/default.nix
+++ i/pkgs/tools/security/gopass/default.nix
@@ -42,8 +42,10 @@ buildGoModule rec {
   '';

   postFixup = ''
-    wrapProgram $out/bin/gopass \
-      --prefix PATH : "${wrapperPath}"
+    for bin in $out/bin/*; do
+      wrapProgram $bin \
+        --prefix PATH : "${wrapperPath}"
+    done
   '';

   meta = with stdenv.lib; {

LGTM


Add mcf-ansi-highlighter-flow plugin

Sorry but it seems like my plugin is not available at flow. Readme says "Once your submission is approved by the Flow Launcher Team it will be available immediately in Flow.". But I can't find my plugin in plugin store or in the query "pm install". Do I just need to wait or it's some kind of an issue? I restarted the flow launcher, reloaded the plugin data, refreshed the plugin store, checked for updates - I have the latest version.


Amazon Codebuild error while building YAML_FILE_ERROR Message: YAML file does not exist

Any help with this error:
While running Amazons CodeBuild using the Meanjs github repo,i am getting an error message in the 'Download Source" phase:
Message: YAML file does not exist
it seems that amazon is requesting a buildspec.yml file to complete the build
Any help with finding this file in this repo?

Depending on the Project Language you have to create buildspec.yml file. Follwing is for PHP(Laravel)
version: 0.1
phases:
pre_build:
commands:
- composer update
build:
commands:
- php artisan serve


Add a persistent GCS bucket for m2lines hub

For https://2i2c.freshdesk.com/a/tickets/218
Also update docs on 'PERSISTENT_BUCKET'

Terraform plan is:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # google_storage_bucket.user_buckets["persistent"] will be created
  + resource "google_storage_bucket" "user_buckets" {
      + force_destroy               = false
      + id                          = (known after apply)
      + location                    = "US-CENTRAL1"
      + name                        = "m2lines-persistent"
      + project                     = "m2lines-hub"
      + self_link                   = (known after apply)
      + storage_class               = "STANDARD"
      + uniform_bucket_level_access = (known after apply)
      + url                         = (known after apply)
    }

  # google_storage_bucket.user_buckets["persistent-staging"] will be created
  + resource "google_storage_bucket" "user_buckets" {
      + force_destroy               = false
      + id                          = (known after apply)
      + location                    = "US-CENTRAL1"
      + name                        = "m2lines-persistent-staging"
      + project                     = "m2lines-hub"
      + self_link                   = (known after apply)
      + storage_class               = "STANDARD"
      + uniform_bucket_level_access = (known after apply)
      + url                         = (known after apply)
    }

  # google_storage_bucket_iam_member.member["prod.persistent"] will be created
  + resource "google_storage_bucket_iam_member" "member" {
      + bucket = "m2lines-persistent"
      + etag   = (known after apply)
      + id     = (known after apply)
      + member =<EMAIL_ADDRESS>      + role   = "roles/storage.admin"
    }

  # google_storage_bucket_iam_member.member["staging.persistent-staging"] will be created
  + resource "google_storage_bucket_iam_member" "member" {
      + bucket = "m2lines-persistent-staging"
      + etag   = (known after apply)
      + id     = (known after apply)
      + member =<EMAIL_ADDRESS>      + role   = "roles/storage.admin"
    }

Plan: 4 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  ~ buckets = {
      + persistent         = "m2lines-persistent"
      + persistent-staging = "m2lines-persistent-staging"
        # (2 unchanged elements hidden)
    }

terraform for LEAP:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # google_storage_bucket.user_buckets["persistent"] will be created
  + resource "google_storage_bucket" "user_buckets" {
      + force_destroy               = false
      + id                          = (known after apply)
      + location                    = "US-CENTRAL1"
      + name                        = "leap-persistent"
      + project                     = "leap-pangeo"
      + self_link                   = (known after apply)
      + storage_class               = "STANDARD"
      + uniform_bucket_level_access = (known after apply)
      + url                         = (known after apply)
    }

  # google_storage_bucket.user_buckets["persistent-staging"] will be created
  + resource "google_storage_bucket" "user_buckets" {
      + force_destroy               = false
      + id                          = (known after apply)
      + location                    = "US-CENTRAL1"
      + name                        = "leap-persistent-staging"
      + project                     = "leap-pangeo"
      + self_link                   = (known after apply)
      + storage_class               = "STANDARD"
      + uniform_bucket_level_access = (known after apply)
      + url                         = (known after apply)
    }

  # google_storage_bucket_iam_member.member["prod.persistent"] will be created
  + resource "google_storage_bucket_iam_member" "member" {
      + bucket = "leap-persistent"
      + etag   = (known after apply)
      + id     = (known after apply)
      + member =<EMAIL_ADDRESS>      + role   = "roles/storage.admin"
    }

  # google_storage_bucket_iam_member.member["staging.persistent-staging"] will be created
  + resource "google_storage_bucket_iam_member" "member" {
      + bucket = "leap-persistent-staging"
      + etag   = (known after apply)
      + id     = (known after apply)
      + member =<EMAIL_ADDRESS>      + role   = "roles/storage.admin"
    }

Plan: 4 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  ~ buckets = {
      + persistent         = "leap-persistent"
      + persistent-staging = "leap-persistent-staging"
        # (2 unchanged elements hidden)
    }

I think create a persistent bucket is a great fix for solving the issue.  Users can then manage space within that bucket the same as they currently do with the scratch bucket.


[Paladin] Want to add a new logo to the Paladin SRC repository

Hello,
I would like to add a functional logo to the SRC repo for the Paladin character sheet, however uploads are blocked, I'm not allowed to do so.
Would it be possible to give me the rights to do so?

Thanks in advance

Created a pull request


Add Character Controller

A character controller should use input from either an input axis, a key or a button to control a character motor. The controller would not have a direct effect on the scene.

Implemented in cf82d12625981225c65790dbaa412d6fd1fdfd51


[observability]:  allow configurable bucket settings for distributions

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

/area observability
Describe the feature
https://github.com/dapr/dapr/blob/d3df68746dd1ae98ba6eaf7cc9a4b5e1a82af5fa/pkg/diagnostics/http_monitoring.go#L43-L44
Some people might consider this to be an excessive number of buckets, and it introduces a tremendous amount of unnecessary cardinality.
I'm already setting https://docs.dapr.io/operations/observability/metrics/metrics-overview/#high-cardinality-metrics to false, but 34 different buckets, per app, per method, per namespace, per service, per status.  It's a lot.  I care about like
5, 50, 500, 5000
Please make this configurable by the user.
Release Note

RELEASE NOTE:

I'm not a maintainer but I do think this is a good idea.
Would you be interested in opening a PR?

I'm not a maintainer but I do think this is a good idea.

Doh, my bad. :)

Would you be interested in opening a PR?

I can probably get around to it this weekend.

I can probably get around to it this weekend.

Awesome :)
Open to other options, but I would probably suggest adding it to the Configuration CRD: https://github.com/dapr/dapr/blob/master/pkg/apis/configuration/v1alpha1/types.go
Then you can run make code-generate to have the CRDs generated from that. Note the command puts the YAMLs in a different folder, so you'll have to manually copy-paste the changes to the https://github.com/dapr/dapr/blob/master/charts/dapr/crds/configuration.yaml file
Also, the types.go file above is used for code generation, but then the configuration sent to the app is copied to this struct: https://github.com/dapr/dapr/blob/master/pkg/config/configuration.go

I updated the PR a little bit tonight.  Probably need some feedback from a maintainer before I spend any more time on it.


How to compile my components?

I have this file after run: php artisan custom-assets:publish

And i modified this but i can´t see in dashboard, i think that i have to add other command after modify my component

Try to run the command twice
https://github.com/Muetze42/nova-assets-changer?tab=readme-ov-file#running


[BUG] Getting error when trying to build chibisafe on docker

Describe the bug
When running docker compose to build chibisafe with some translationt pt_BR, the build fails
Error lines:
root@iccsv05-envio:/home/ubuntu# docker-compose up
Building chibisafe
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
            Install the buildx component to build images with BuildKit:
            https://docs.docker.com/go/buildx/

Sending build context to Docker daemon  3.584kB
Step 1/24 : FROM node:20-alpine as builder
 ---> 4b21504f2506
Step 2/24 : RUN apk add --no-cache libc6-compat git
 ---> Using cache
 ---> 1d8b50cf4b9f
Step 3/24 : WORKDIR /app
 ---> Using cache
 ---> 47ae32294075
Step 4/24 : COPY . .
 ---> Using cache
 ---> 9a75882ede49
Step 5/24 : COPY package.json yarn.lock turbo.json tsconfig.json ./
COPY failed: file not found in build context or excluded by .dockerignore: stat package.json: file does not exist
ERROR: Service 'chibisafe' failed to build : Build failed

To Reproduce

git clone the repository
edit docker-compose.yml to build service chibisafe as below:

services:
  chibisafe:
    #image: chibisafe/chibisafe:latest
    build:
      context: ./chibisafe/docker
      dockerfile: Dockerfile
    environment:
      - BASE_API_URL=http://chibisafe_server:8000
    expose:
      - 8001
    restart: unless-stopped

Save and run it up as usual
Expected behavior
It's expected to see the build using local files and bring services up
--
Error trying to build with buildx:
root@iccsv05-envio:/home/ubuntu# docker-compose up
Building chibisafe
[+] Building 0.6s (9/19)                                                                                docker:default
 => [internal] load build definition from Dockerfile                                                                                0.2s
 => => transferring dockerfile: 934B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/node:20-alpine                                                                                0.1s
 => [builder 1/7] FROM docker.io/library/node:20-alpine                                                                                0.2s
 => [internal] load build context                                                                                0.1s
 => => transferring context: 1.47kB                                                                                0.0s
 => CACHED [builder 2/7] RUN apk add --no-cache libc6-compat git                                                                                0.0s
 => CACHED [builder 3/7] WORKDIR /app                                                                                0.0s
 => CACHED [builder 4/7] COPY . .                                                                                0.0s
 => ERROR [builder 5/7] COPY package.json yarn.lock turbo.json tsconfig.json ./                                                                                0.0s
------
 > [builder 5/7] COPY package.json yarn.lock turbo.json tsconfig.json ./:
------
Dockerfile:7
--------------------
   5 |     WORKDIR /app
   6 |     COPY . .
   7 | >>> COPY package.json yarn.lock turbo.json tsconfig.json ./
   8 |
   9 |     RUN yarn workspaces focus @chibisafe/next
--------------------
ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref dd9d218e-5be2-43f0-88c1-a4e2cfb3fb39::rgrkyh88qjp91cgcmro4cnqi7: "/turbo.json": not found
ERROR: Service 'chibisafe' failed to build : Build failed

The issue was related to context and dockerfile path, fixed to:
      context: ./chibisafe
      dockerfile: ./docker/Dockerfile


CSS Next error with css variables

Hey, I am trying to use cssnext and I am facing few problems.

Custom property ignored: not scoped to the top-level :root element
variable '--foo-bar' is undefined and used without a fallback

Basically I have few variables defined at :root. Now at certain blocks I am trying to update the values of these variables and at some places I am trying to define new variables. Its giving me the above mentioned errors. I have attached the necessary screenshot. Can you please help.

This is a limitation of this transformation. See docs for more explanation https://github.com/postcss/postcss-custom-properties#postcss-custom-properties-


Convert README.md to README.rst

I have converted the README file to reStructuredText.

Thanks for the patch! I forgot that this was a problem for python-xkcd.
I prefer markdown to reStructuredText, though, so what I think I'll do (and what I've done for another project) is use pypandoc to dynamically convert my markdown readme into rST when long_description is generated. This was suggested here at the end of a very long discussion about the prospect of adding markdown rendering support to PyPI.
So I'll fix this and push a new release to PyPI momentarily, then close this PR.


[5.2 branch] XCTSkip and related APIs

Introduce XCTSkip and related APIs for skipping tests
5.2 release branch merge request

Explanation: This includes the XCTSkip and related APIs in the 5.2 release, for greater API parity with Xcode's XCTest.
Scope: Additive change to API, no impact to existing source.
Radar: rdar://problem/56671272
Risk: Low, requires clients to adopt the new API to get new behaviors
Testing: New unit tests added
Reviewer: @briancroom

@swift-ci Please test


Jump to login error message on login failure

Implements JOINDIN-675

Can one of the admins verify this patch?

ok to test

Thank you!


Activity of the function f

Should it be active or constant?
See https://github.com/SciML/SciMLBenchmarks.jl/pull/988 for the discussion

Duplicate of #339


feat(accountsdb): improved struct/var naming

improved naming of structs/vars after taking a look back over the code
main changes were made to the index:

move disk_allocator into AccountIndex
move bin logic into ShardedPubkeyRefMap and rename 'bins' to 'shards'
improve reference allocator definition (now is an enum, Ram or Disk with a corresponding config)
rename maps to be more key-value specific -- (ie, reference_memory -> slot_reference_map)

other smaller changes include:

improve recycle_fba allocator config to be more specific
improve hash equality check
support single-threaded hash calculation

Moving DiskMemoryAllocator into index is great, makes its usage much clearer
Nice job on the renames, the new naming is definitely preferable
logging in the index init is useful
AccountsDb init is much cleaner

Agreed with @InKryption on his comments, happy to approve once they're resolved.


[Event Hubs] Prepare for May Release

Summary
The focus of these changes is to prepare the Event Hubs core package for the May release.

API change check
API changes are not detected in this pull request.

/check-enforcer evaluate


video size very low

video colorization very good and very impressive . but render image low size 768x432 . and video size also same. how to in increase the image size and video size. thank you..

Hi, since this is research work and we train the network with low-resolution images. If you want to test on higher resolution, please set the command-line argument --image_size properly. By default, it is set to [432, 768].

I am noted Thank you.


How to create sync

How to create sync for textract.fromFileWithPath
I want execute code after file gets read.How to make it sync?

All the options there are JavaScript related. Could wrap it in a promise and use async/await? Could use a promisify library?


TypeError: Cannot read property 'apply' of undefined

We tried following the Migration steps for RXJS 6. We are getting the below error
TypeError: Cannot read property 'apply' of undefined.
Our application uses RxJS 5.6. We need your help on this.

Make sure you're using TSLint 5.9+.


added uiuc license

the template from wikipedia actually has placeholders in the third bullet point, which I replaced by "the copyright holder" since I saw the plugin only replaces the first occurance of a placeholder and didn't see a quick way to change that.
happy for suggestions.

Thanks.


bugfix: shift AABB coordinates for boxes

Hello,
I noticed that the AABB coordinates of boxes do not seem to take the position of the box into account.
Here is an example that shows the bug:
const Crash = require('crash-colliders');
let crash = new Crash();
let listener = (a, b, res, cancel) => {
    console.log("CRASH");
};
crash.onCollision(listener);
let box = new crash.Box(new crash.Vector(100, -30), 200, 200);
let circle = new crash.Circle(new crash.Vector(100, -30), 28);
crash.insert(box);
crash.insert(circle);
crash.moved(box);
crash.moved(circle);
console.log(crash.search(circle));
for (let id in crash.rbush.toJSON().children) {
    console.log(crash.rbush.toJSON().children[id].aabb);
}
crash.check();

They should crash, but the output is:
[]
{ x1: 0, y1: 0, x2: 200, y2: 200 }
{ x1: 72, y1: -58, x2: 128, y2: -2 }

As you can see, the AABB coordinates are wrong.
I suspected that this could also be due to a version mismatch of SAT, but it seems to be correct (it is 0.5.0).

I'm sorry I'm only seeing this now, must have slipped through my inbox without me noticing...
Anyway, I can reproduce the bug and that patch seems to fix it, so I'll merge it and publish to NPM.
Thanks!


Shortcut refactoring + more (554, 519, 526, 555, 595)

[JIRA 554] #12/22/2014 being entered into editor is now supported. #date still works to pop up date selector as well. Only #date appears in right panel. Now infrastructure supports regular expression specified value shortcuts through new getTriggerRegExp. A shortcut can provide both string triggers (#date) and a regular expression trigger (actual date). I added a UI test case for entering an actual date into the editor.
[JIRA 519,526] Parsing of notes containing structured dates is now supported. Parser was refactored to support the string triggers and regular expressions as well as provided by shortcuts. Test cases were added for parsing notes with dates.
[JIRA 555] Parsing now also detects unexpected # or @ expressions and returns a list of them from the parse method in addition to the SHR patient. An existing test case already tested for this already so once all test cases were updated for parser API changing to return both the SHR entries and the unexpected structured phrases, that test case passed and verifies that the unexpected tag is returned.
[JIRA 575, 595] Pasting of plain text structured phrases now works as well; however, @condition and #date cause issues due to the portal pop-up. @condition[[Lobular Carcinoma...]] can be used but I left the issue open for this so we can revisit how those are handled. I think 595 can be marked fixed but 575 should stay open. Also, test cases need to be added for pasting which can be done as part of 575.

Please log a detailed jira bug Dylan. good one. I think this is a general problem? In other words, this problem is not specific to dates?

Thanks! Yeah I think a separate JIRA will be good. It's a general problem with how we've approached regex's for AutoReplace

This looks really good to me! One thing that I noticed is:
[JA1]:  If you copy and paste a date structured phrase, the date is pasted twice.
I'm not sure if this is related to some of the pasting issue that Greg suggested remain open. If so, this might be fine to hold off on.
Besides that, all the test cases passed, the parsing seems to be working correctly, and I can enter in dates using #10/10/2017 and they becomes structured phrases and update the patient information.

Thanks for reviewing Julia. I'll take a look at JA1 before we merge.

JA1 fixed and all tests still pass. It would be nice to add some copy and paste test cases so maybe I'll try to do that. I'll need to get a lot better at testcafe!

I'd vote to merge it now.

Sounds good! Merging now!


Update recipe to include trackpy requirement

Added the dependency trackpy to the conda recipe. This is in ParticleSpy's dependencies in setup.py.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

Thanks Tom. I take it you meant add to the maintainers list in this PR?

You will need to add your GitHub username to the end of the meta.yaml file.

Also please remove your last commit. Thanks!

@conda-forge-bot please rerender

@conda-forge-admin please rerender

I just realised that you didn't bump the build number. Now the packages on conda-forge won't get updated with the added dependency. 😢
Do you plan on making a new release of particlespy soon? Otherwise you will need to create a new PR to ensure new packages are uploaded.
Apologies, should have spotted this earlier!

I need to do a quick bug fix this week so will do a new release. I should update the conda recipe to include some files too though (probably before the release on pypi), so will also bump the build number then.

Ok sounds good. By the way, shortly after you push your new release to PyPI, you can expect to see an automagically generated PR here that will bump the recipe to the same new release.


Were are tests for this starter?

Describe the feature request
I missed a test suite. Do you have plans to add one?
I desired I'm open to contribute tests to this project.
Background
For instance at first I misconfigured this starter and got a meaningless NPE.
Solution suggestions
No response

@ajdergute Thanks for bringing this up. It would be great if you can contribute tests to this. Otherwise I can start adding them some time next week.

Great! I will try some stuff, hopefully soon.


I am getting an error message that I cannot debug

Hi Jasper,
I cannot seem to run the attached json in the tool. The error message does not point me to the problem.
I created the json locally using a similar approach as in your integration notebook on Kaggle.
Do you know what goes wrong?
Cannot load episode from run76.json
Cannot set properties of undefined (setting '0')
run76.zip

Fixed in 281d5048c81b46cd8b7314a1ed20957975d0315a, thanks for reporting the issue!

thanks, that was fast!


Add support for basic XR Rigs

Create base Avatar Driver script
Create Avatar Driver for basic XR Rig
Rename Avatar Driver for XR-Tools Player Body
Added Basic XR Rig demo scene

lgtm


use className in props when provided

Although className is included as part of the Loader props it was not used as class for the loaded = false condition.
I need to provide my own class for the component and I would like to have this merged.
I wrote a simple small test, but I was not able to run the test infrastructure. I found some dependencies issues while I tried to do that. I tried to update the libraries as well but it doesn't make the situation any better.
I was also wondering whether would be possible to have travisCI integration for this project.
refers to #19

Hi @mikekauffman ,
Thanks for the feedback.
Since I am not able to test this branch if you agree with this underlined feature and you also have spotted and correct some issues. I would be happy if you discard my PR and implement separately in master. If you can't do that I would need some help to setup the test environment.
Please let me know your thoughts

Hi @mikekauffman,
Thanks for the new release 2.2.0 I am just testing it now. It seems working.
We might need to update the REAME to advise to use props parentClassName since the prop className is not used at all.


Invariant Violation: Module AppRegistry is not a registered callable module

I am getting below runtime error on IOS platform:

"react-native": "0.63.4"
"react-native-config": "^1.4.5"

I have env.development, env.staging, env.production & each & every has build pre-action.
example of env.development:
cp "${PROJECT_DIR}/../.env.development" "${PROJECT_DIR}/../.env"
"${SRCROOT}/../node_modules/react-native-config/ios/ReactNativeConfig/BuildXCConfig.rb" "${SRCROOT}/.." "${SRCROOT}/tmp.xcconfig"

yes, the envs are empty, I think the issues from #607 still persist


tutanota-desktop: init at 3.88.3

Motivation for this change
Adding Tutanota official desktop client. Using AppImage for now as I wasn't able to build it through source yet.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[X] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

I haven't tested this but it looks good! Thank you.
Did you try building it from source btw?

@jtrees FYI, if you get to try it, you might find a warning regarding secret storage. This is intended if you don't have a keychain installed :).
Regarding building from source, I tried, but the main issue I got into is that as this is a JavaScript project, I generally use node2nix to build it. One of the problems is that the package lock file has an empty key which makes it unrecognizable. So, if I try to run with only the package.json, besides adapting one of the dependencies URLs (the opsec library), there is a dependency out of the project reach that fails.
The other option would be getting the tar file from the releases section at their repo, but I honestly couldn't execute the binary through NixOS. That's why I went with the AppImage, just to have something done, but in case someone can build it or set up the tar successfully, then it's just a matter of adapting it.

@jtrees FYI, if you get to try it, you might find a warning regarding secret storage. This is intended if you don't have a keychain installed :).
Regarding building from source, I tried, but the main issue I got into is that as this is a JavaScript project, I generally use node2nix to build it. One of the problems is that the package lock file has an empty key which makes it unrecognizable. So, if I try to run with only the package.json, besides adapting one of the dependencies URLs (the opsec library), there is a dependency out of the project reach that fails.
The other option would be getting the tar file from the releases section at their repo, but I honestly couldn't execute the binary through NixOS. That's why I went with the AppImage, just to have something done, but in case someone can build it or set up the tar successfully, then it's just a matter of adapting it.

I see. Yes, it's good to have the AppImage as a stop-gap solution. Thanks again.
It is it a bit troubling that such a security-sensitive application cannot be built properly from source though. Did you report the issue upstream?

It is it a bit troubling that such a security-sensitive application cannot be built properly from source though. Did you report the issue upstream?

Honestly I haven't had the time to do a thorough analysis of the issue. When I tried to use node2nix, the only thing I did was comparing the error and seeing the package.json of the project, to see if it was something I could fix, but the library having the issue was not listed there. I'd rather pinpoint to the exact issue to avoid getting an immediate closed issue there.
Also, as I'm also trying to port other JS based projects to NixOS, someone provided other options to try building besides node2nix. I hope I can get it done this weekend.

/marvin opt-in

/status needs_reviewer

Doing a nox-review pr 139454 gives me a mismatched checksum:
hash mismatch in fixed-output derivation '/nix/store/d8nfs5d3cc7fcpzvlagwybxs3m528bzx-tutanota-desktop-3.88.3.AppImage':
  wanted: sha256:1fdszc4rxv0ywmbn3r2l0vzf9dh79sv9a35w2wbhkq78k0khwkih
  got:    sha256:0iv6xvfw0rhamdwy3wvgdakpcc99d94rcs5y0bqwphcr47lwf2rk

Doing a nox-review pr 139454 gives me a mismatched checksum:

They updated the version (now it is 3.88.4). The main issue is that their AppImage download link goes directly to the release version (no version is specified on the URL), which makes it troublesome if there is an update.


Fix to #3180 - A column has been specified more than once in the order by list. Columns in the order by list must be unique.

Problem happens for specific combination of nested include statements. When we include collection, we inject ORDER by clauses. We choose them based on the QuerySource of the tables in the select expression. If select expression has multiple tables, added by previous include reference, both tables have the same QuerySource. This makes the choice of order by table ambiguous and may lead to us ordering by the same column twice.
Fix is to add additional metadata to TableExpressionBase that represents the type of entity it is associated with.
The fix doesn't remove the issue entirely. It can still appear in some cases with self reference includes (where Tables have the same type), or if Includes are done on a subquery (which doesn't have IEntityType associated with it)

@anpete

@maumar Close this?


chore(test): make test descriptions consistent

Components are called: <%= classifiedModuleName %>Directive and it was bothering me that the rest were like: Service: <%= classifiedModuleName %>.
Another change I'd like to make but would like approval first, is to wrap the first generated test in another describe like so:
describe('.constructor()', () => {
  it('should create', () => {
    expect(component).toBeTruthy();
  });
});

I think it makes tests a little more organised and easier to read. I got the idea from reading the Http specs within angular/angular: https://github.com/angular/angular/blob/master/modules/%40angular/http/test/http_spec.ts#L108

@johnpapa @Brocco @filipesilva What do you think?  We use that standard in our own tests (describe('ClassName', () => ...)), so I don't see why our generated projects should be different. I'll defer to the styleguide for this one though.

@hansl you mean wrapping the it in a describe ? yes, i agree 100% helps for output organization and the eventual and imminent beforeEach-ness

@johnpapa No, look at the changes.
Basically the tests generated by the CLI right now look like this:
describe('Component: Blah', () => {
  // ...
});```

With this PR it would look like this:
```typescript
describe('BlahComponent', () => {
  // ...
});```

(the name of the class itself is `BlahComponent`, but the user likely ran `ng generate component blah`)

sorry, a few different things in the comments.
yes, i agree. FooComponent is a much better naming convention

LGTM.


Create spaceflights-pyspark-viz

Motivation and Context
Subtask of https://github.com/kedro-org/kedro/issues/2838
Spaceflights pyspark with Kedro-Viz features enabled:

Matplotlib
Ploty
Experiment Tracking

How has this been tested?
Created a project locally using: kedro new --starter=/Users/merel_theisen/Projects/kedro-starters/spaceflights-pyspark-viz/ and did kedro run
Checklist

[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Assigned myself to the PR
[ ] Added tests to cover my changes

I do have a question - are these __init__.py files needed?

spaceflights-pyspark-viz/init.py
spaceflights-pyspark-viz/{{ cookiecutter.repo_name }}/init.py
spaceflights-pyspark-viz/{{ cookiecutter.repo_name }}/src/init.py
Didn't see them in the current spaceflights or Add spaceflights-pyspark starter #147

Good spot! I think my IDE added those automatically.


WIP: Dedepe widget docs.

- Summary

- Test plan

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Deploy preview for netlify-cms-www ready!
Built with commit fcef282d856d1dc9e0ef530d8494c67dd82f8ad2
https://deploy-preview-1211--netlify-cms-www.netlify.com

Deploy preview for cms-demo ready!
Built with commit fcef282d856d1dc9e0ef530d8494c67dd82f8ad2
https://deploy-preview-1211--cms-demo.netlify.com


Update GREL script documentation

The documentation for the GREL script is due an update especially because of the newest changes.

The documentation is now updated.


Import Error DLL failed

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 (64bit)
TensorFlow installed from (source or binary): install using conda in command window as admin
TensorFlow version: 2.3.1
Python version: 3.8.5
Installed using virtualenv? pip? conda?: installed using conda then created virtual env
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory: RTX 2060 16GB

Describe the problem
I have installed tensorflow on my windows desktop with anaconda. As a result I followed the steps from a youtube video by Jeff Heaton. Now I would like to run Tensorflow in  VS code and it will not work. I get an import error that says the following ImportError: DLL load failed while importing _pywrap_tensorflow_internal: %1 is not a valid Win32 application.
Provide the exact sequence of commands / steps that you executed before running into the problem
The only code I have is an import line "import tensorflow as tf" when I run the script by using ctl+F5, I get the error. When I type "python test.py" in the no errors are thrown. (test.py is the name of my file)
Creating and install packages and tensorflow for environment steps

Run CMD as admin
conda create -n tensorflow-cpu python=3.8
conda activate tensorflow-cpu
conda install jupyter matplotlib numpy pandas scipy
pip install tensorflow
got lots of messages that the requirement was already met.
python
import tensorflow as tf
tf.version
2.3.1
quit()
code (opens VS code)
create new file
import tensorflow as tf (autofill in works)
run
no error
add other packages (import matplotlib, pandas etc...)
autofill no longer works
create new file
import tensorflow as tf (autofill doesn't work)
run (error outputted in terminal)
run python test.py in terminal (no error)

Any other info / logs
Jeff heaton video link: https://www.youtube.com/watch?v=RgO8BBNGB8w&t=474s

When I go back to cmd and run "code" again and open a new VS code window, it works again. Can someone explain?

@ObeyedSky622
Looks like this is not issue with Tensorflow installation as you are able to import without any issues.
This seems to be issue with VS code. Thanks!

@ravikyram Then why when I run the code by pressing F5 I get the error and run I run in terminal I don't get anything? I also ran the script in IDLE and got the same error.

@ObeyedSky622
Could you please create a new virtual environment and try running the code and see if the issue still persists.If you facing the issue request you to share the error log. Thanks!

Yes. I have created 2 new environments already. Here is the full error:
Traceback (most recent call last):
File "C:\Users\bre13\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow.py", line 64, in
from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: %1 is not a valid Win32 application.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "d:\VS_code_files\ml_files\functionLib.py", line 8, in
import tensorflow as tf
File "C:\Users\bre13\AppData\Roaming\Python\Python38\site-packages\tensorflow_init_.py", line 41, in
from tensorflow.python.tools import module_util as module_util
File "C:\Users\bre13\AppData\Roaming\Python\Python38\site-packages\tensorflow\python_init.py", line 40, in
from tensorflow.python.eager import context
File "C:\Users\bre13\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\eager\context.py", line 35, in
from tensorflow.python import pywrap_tfe
File "C:\Users\bre13\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tfe.py", line 28, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users\bre13\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow.py", line 83, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users\bre13\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow.py", line 64, in
from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: %1 is not a valid Win32 application.
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

@ObeyedSky622
What is make/model of your cpu?
I suspect your cpu model does not support AVX instructions sets.See hardware requirements
Make sure to download the latest microsoft visual c++ redistributable from here.
.Also, please follow the instructions from to install from Tensorflow website.
Please, check Your CPU/Python is on 32 bits?Please, refer #36167
Thanks!

Yes, I figured the issue out. When I clicked download for python it auto-downloaded the 32-bit version and not the 64-bit. I uninstalled python and installed the correct version.

@ObeyedSky622
TF supports 64 bit only.
Please, close this thread if your issue was resolved. Thanks!


Implement integration with actor registry.

As part of the new message handling we need to be able to integrate with new actor registry and receive actor information from registry.
Currently actor registry does not publish any events. We need to discuss with architects and Titans how we solve this issue.

Is not linked to an epic because we have not prioritized actor registry.


Big error on Godot 4.3

When I compile for my android I get this error:
modules/gdscript/gdscript.cpp:2203 - Condition "!named_globals.has(p_name)" is true.
modules/gdscript/gdscript.cpp:2203 - Condition "!named_globals.has(p_name)" is true.
modules/gdscript/gdscript.cpp:2203 - Condition "!named_globals.has(p_name)" is true.
modules/gdscript/gdscript.cpp:2203 - Condition "!named_globals.has(p_name)" is true.
modules/gdscript/gdscript.cpp:2203 - Condition "!named_globals.has(p_name)" is true.
modules/gdscript/gdscript.cpp:2203 - Condition "!named_globals.has(p_name)" is true.
Failed to create an autoload, script 'res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd' is not compiling.
editor/editor_autoload_settings.cpp:577 - Condition "!info->node" is true. Continuing.
Failed to create an autoload, script 'res://addons/GodotPlayGameServices/autoloads/players_client.gd' is not compiling.
editor/editor_autoload_settings.cpp:577 - Condition "!info->node" is true. Continuing.
Failed to create an autoload, script 'res://addons/GodotPlayGameServices/autoloads/achievements_client.gd' is not compiling.
editor/editor_autoload_settings.cpp:577 - Condition "!info->node" is true. Continuing.
Failed to create an autoload, script 'res://addons/GodotPlayGameServices/autoloads/leaderboards_client.gd' is not compiling.
editor/editor_autoload_settings.cpp:577 - Condition "!info->node" is true. Continuing.
Failed to create an autoload, script 'res://addons/GodotPlayGameServices/autoloads/snapshots_client.gd' is not compiling.
editor/editor_autoload_settings.cpp:577 - Condition "!info->node" is true. Continuing.
Failed to create an autoload, script 'res://addons/GodotPlayGameServices/autoloads/events_client.gd' is not compiling.
editor/editor_autoload_settings.cpp:577 - Condition "!info->node" is true. Continuing.

Hi @MTGPROD I'm sorry to hear that.
I need more context to try to understand what might be happening. Did you have the plugin implemented in godot 4.2 already or this is a new project you started directly in godot 4.3? Did you follow the steps in the readme and the implementation guide inside the demo project?
Any other information you can provide will be helpful. Let's see if we can figure this out.

To be honest, I started my project in 4.2 and plugins like these were not working on it so I upgraded the project to 4.3. But I continue to struggle. I tried many many "Play Services" plugins which were all forks of the same non working plugin. So I found a fork of yours without 4.3 support, tried anyways, didn't worked, so now I installed the Godot4.3-compatible version of your plugin, and there is it.
I tried using the plugin in the ready of my first scene and nothing happened, even tho the console written "Plugin found!" in adb logcat.
So yeah I think my project is pretty unstable because of the deletion/adding of plugins multiple times.
For the why the scripts do not compile it is because it doesn't recognize the GodotPlayGameServices singleton (i guess it's a singleton)
  res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd:31 - Parse Error: Identifier "GodotPlayGameServices" not declared in the current scope.
  res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd:32 - Parse Error: Identifier "GodotPlayGameServices" not declared in the current scope.
  res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd:35 - Parse Error: Identifier "GodotPlayGameServices" not declared in the current scope.
  res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd:44 - Parse Error: Identifier "GodotPlayGameServices" not declared in the current scope.
  res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd:45 - Parse Error: Identifier "GodotPlayGameServices" not declared in the current scope.
  res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd:51 - Parse Error: Identifier "GodotPlayGameServices" not declared in the current scope.
  res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd:52 - Parse Error: Identifier "GodotPlayGameServices" not declared in the current scope.
  res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd:64 - Parse Error: Identifier "GodotPlayGameServices" not declared in the current scope.
  res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd:65 - Parse Error: Identifier "GodotPlayGameServices" not declared in the current scope.
  modules/gdscript/gdscript.cpp:2936 - Failed to load script "res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd" with error "Parse error". (User)
  Failed to create an autoload, script 'res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd' is not compiling.
  Failed to create an autoload, script 'res://addons/GodotPlayGameServices/autoloads/sign_in_client.gd' is not compiling.
  editor/editor_autoload_settings.cpp:577 - Condition "!info->node" is true. Continuing.

Theses errors spawn in the console at start of godot project.
I fought that the plugin weren't enabled but it seems to be:

My game id is configured:

I was wonder how to implement this in my game and I found the demo project, thanks to you, but now It's the plugin that don't compile :(

Hi @MTGPROD if I'm understanding it correctly, you removed code from the plugin? The plugin can't work like that, it needs all the autoloads. Why did you do it? Is there something that clashes with something else in your project?  I could take another approach and put everything under the same autoload, but that would be a major change.
I will suggest to start a fresh new project and install only the plugin to test if it works there, just following the instructions in the README. Please, try that and let me know how it goes 😃
Also, I just uploaded a patch for the plugin fixing the version number, thanks for noticing the error!

I just restarded my computeur and the situation seems to be fine, all autoloads are there and "working" (no errors on the console)
But when exporting the game with the SignIn code from the demo code you provided, there's no signin window in my game.
 So I'm a little confused.
I did all the google cloud things etc etc it works, even with other plugins.

Oh, sorry for the misunderstanding! For what I can see in the logs, it's complaining about a singleton named IP, that already exists. Where is this singleton coming from? What plugins are you using? I will try to install them in a project of mine to see if there's any clashes with my plugin.

Okay so, I have admob plugin, SilentWolf plugin and yours, in godot it appears like below:

Now that you say it, I think there's a potential conflict between SilentWolf and your plugin.. Since I do not need silentwolf anymore I can remove it, but if people want to add both for google play players + silentwolf ones it will be impossible...

Okay, after removing SilentWolf from my project the conflict disappeared, however I have no SignIn pop up, nothing happens at start.
Here's the logcat:
09-11 18:25:15.749  5650  5721 I godot   : Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
09-11 18:25:16.593  5650  5721 I godot   : OpenGL API OpenGL ES 3.1 v1.r15p0-00rel0.bdd9e62cdc8c88e0610a16b5901161e9 - Compatibility - Using Device: ARM - Mali-T720
09-11 18:25:16.668  5650  5721 I godot   :
09-11 18:25:38.570  5650  5721 I godot   : Plugin found!

Ok, it makes sense there's a conflict between Silent Wolf and mine. They do the same things with different backends after all! Thanks a lot for bringing this to my attention, I think I'll put a warning in my plugin while I try to figure out if it's worth to fix it.
For your problem, if the plugin logs the Plugin found! line that's good. Do you have the Google Play app installed in your phone with a user logged in there? Also, in logcat, do you see anything else filtering with this expression: package:com.jacobibanez.godot.test.game package:com.google.android.gms?

Yeah I have all the google play things done, your expression do not work so I did adb logcat -s com.jacobibanez.godot.test.game and same the other package and nothing

Is there something wrong with my AndroidManifest.xml ?
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools"
    android:versionCode="1"
    android:versionName="1.0"
    android:installLocation="auto" >

    <supports-screens
        android:smallScreens="true"
        android:normalScreens="true"
        android:largeScreens="true"
        android:xlargeScreens="true" />

    <uses-feature
        android:glEsVersion="0x00030000"
        android:required="true" />

    <application
        android:label="@string/godot_project_name_string"
        android:allowBackup="false"
        android:icon="@mipmap/icon"
        android:appCategory="game"
        android:isGame="true"
        android:hasFragileUserData="false"
        android:requestLegacyExternalStorage="false"
        tools:ignore="GoogleAppIndexingWarning" >
        <profileable
            android:shell="true"
            android:enabled="true"
            tools:targetApi="29" />

        <!-- Records the version of the Godot editor used for building -->
        <meta-data
            android:name="org.godotengine.editor.version"
            android:value="${godotEditorVersion}" />

        <meta-data
            android:name="com.google.android.gms.ads.APPLICATION_ID"
            android:value="ca-app-pub-1538496811363588~2408127446" />

        <!-- <meta-data
            android:name="com.google.android.gms.games.APP_ID"
            android:value="1044387828401" />

        <meta-data
            android:name="com.google.android.gms.version"
            android:value="@integer/google_play_services_version"/> -->

        <activity
            android:name=".GodotApp"
            android:label="@string/godot_project_name_string"
            android:theme="@style/GodotAppSplashTheme"
            android:launchMode="singleInstancePerTask"
            android:excludeFromRecents="false"
            android:exported="true"
            android:screenOrientation="landscape"
            android:configChanges="orientation|keyboardHidden|screenSize|smallestScreenSize|density|keyboard|navigation|screenLayout|uiMode"
            android:resizeableActivity="false"
            tools:ignore="UnusedAttribute" >

            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
    </application>

</manifest>

I never used logcat from the console (I use android studio) so I'm not sure how you filter packages, but you should definitely be seeing something from the Google package for sure.
Also, how does your code that uses the plugin look like?
About your manifest, you don't have to manually edit it if you use the new dock that the plugin creates. I would recommend redownloading the android build template.

I used the logcat of Android studio, to find out admob plugin is deprecated lol

My godot logs on android studio

Here's the logs of the expression you provided for logcat:
2024-09-12 08:37:25.954  7271-7282  .gms.persisten          com.google.android.gms.persistent    I  Background concurrent copying GC freed 343588(14MB) AllocSpace objects, 0(0B) LOS objects, 49% free, 14MB/28MB, paused 187us total 783.333ms
2024-09-12 08:37:30.925  7271-9123  PackageManager          com.google.android.gms.persistent    V  [4276071b-346d-4510-bc1d-bf16c360668c] Phase1 called; posting
2024-09-12 08:37:30.925  7271-7271  PackageManager          com.google.android.gms.persistent    D  [4276071b-346d-4510-bc1d-bf16c360668c] Phase1 request; prefix: [-2130968576, -1721069568, -1552310272, -1010991104, -703688704, -142594048, 32677888, 94052352, 145063936, 199421952, 321712128, 410742784, 946360320,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>], userId: 0
2024-09-12 08:37:30.942  7271-13942 PackageManager          com.google.android.gms.persistent    V  [d43146e0-a2b6-456c-ab27-0ffd0976b623] Phase1 called; posting
2024-09-12 08:37:30.942  7271-7271  PackageManager          com.google.android.gms.persistent    D  [d43146e0-a2b6-456c-ab27-0ffd0976b623] Phase1 request; prefix: [-2130968576, -1823723520, -1552310272, -1327525888, -1084518400, -986521600, -744370176, -698515456, -464322560, -321957888, -285040640, -46837760,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>], userId: 0
2024-09-12 08:37:32.437 19882-19882 BoundBrokerSvc          com.google.android.gms               D  onBind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
2024-09-12 08:37:32.437 19882-19882 BoundBrokerSvc          com.google.android.gms               D  Loading bound service for intent: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
2024-09-12 08:37:32.501 19882-19882 BoundBrokerSvc          com.google.android.gms               D  onUnbind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
2024-09-12 08:37:37.338 19882-19882 BoundBrokerSvc          com.google.android.gms               D  onBind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
2024-09-12 08:37:37.338 19882-19882 BoundBrokerSvc          com.google.android.gms               D  Loading bound service for intent: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
2024-09-12 08:37:37.395 19882-16137 AdvertisingIdClient     com.google.android.gms               D  AdvertisingIdClient already created.
2024-09-12 08:37:37.400 19882-16137 AdvertisingIdClient     com.google.android.gms               I  shouldSendLog<PHONE_NUMBER>
2024-09-12 08:37:37.401 19882-16137 AdvertisingIdClient     com.google.android.gms               I  GetInfoInternal elapse 5ms
2024-09-12 08:37:37.546 19882-19882 BoundBrokerSvc          com.google.android.gms               D  onUnbind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
2024-09-12 08:37:39.404 19882-19882 BoundBrokerSvc          com.google.android.gms               D  onBind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
2024-09-12 08:37:39.404 19882-19882 BoundBrokerSvc          com.google.android.gms               D  Loading bound service for intent: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
2024-09-12 08:37:39.725 19882-19882 BoundBrokerSvc          com.google.android.gms               D  onUnbind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
2024-09-12 08:37:39.985  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  onBind: Intent { act=com.google.android.gms.instantapps.START pkg=com.google.android.gms }
2024-09-12 08:37:39.985  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  Loading bound service for intent: Intent { act=com.google.android.gms.instantapps.START pkg=com.google.android.gms }
2024-09-12 08:37:40.489  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  onBind: Intent { act=com.google.android.gms.phenotype.service.START pkg=com.google.android.gms }
2024-09-12 08:37:40.490  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  Loading bound service for intent: Intent { act=com.google.android.gms.phenotype.service.START pkg=com.google.android.gms }
2024-09-12 08:37:40.703  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  onUnbind: Intent { act=com.google.android.gms.instantapps.START pkg=com.google.android.gms }
2024-09-12 08:37:40.706  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  onUnbind: Intent { act=com.google.android.gms.phenotype.service.START pkg=com.google.android.gms }
2024-09-12 08:37:41.097  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  onBind: Intent { act=com.google.android.gms.common.telemetry.service.START dat=chimera-action: cmp=com.google.android.gms/.chimera.PersistentApiService }
2024-09-12 08:37:41.097  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  Loading bound service for intent: Intent { act=com.google.android.gms.common.telemetry.service.START dat=chimera-action: cmp=com.google.android.gms/.chimera.PersistentApiService }
2024-09-12 08:37:41.106  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  onBind: Intent { act=com.google.android.gms.phenotype.service.START pkg=com.google.android.gms }
2024-09-12 08:37:41.108  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  Loading bound service for intent: Intent { act=com.google.android.gms.phenotype.service.START pkg=com.google.android.gms }
2024-09-12 08:37:41.317  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  onBind: Intent { act=com.google.android.gms.auth.account.workaccount.START dat=chimera-action: cmp=com.google.android.gms/.chimera.PersistentApiService }
2024-09-12 08:37:41.317  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  Loading bound service for intent: Intent { act=com.google.android.gms.auth.account.workaccount.START dat=chimera-action: cmp=com.google.android.gms/.chimera.PersistentApiService }
2024-09-12 08:37:41.452  7271-13942 PackageManager          com.google.android.gms.persistent    V  [00d113f1-3b0a-4523-ab71-8c07092d7c79] Phase1 called; posting
2024-09-12 08:37:41.452  7271-7271  PackageManager          com.google.android.gms.persistent    D  [00d113f1-3b0a-4523-ab71-8c07092d7c79] Phase1 request; prefix: [-2130968576, -2029850624, -1948659712, -1852477440, -1552310272, -1429458944, -577855488, -191750144, -166928384, -164945920, 203276288, 539660288, 946147328,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>], userId: 0
2024-09-12 08:37:41.489  7271-13945 PackageManager          com.google.android.gms.persistent    V  [0b63d898-2bef-4396-be75-b0d6309569fb] Phase1 called; posting
2024-09-12 08:37:41.492  7271-7271  PackageManager          com.google.android.gms.persistent    D  [0b63d898-2bef-4396-be75-b0d6309569fb] Phase1 request; prefix: [-2130968576, -1701249024, -1609068544, -1552310272, -1234538496, -1031393280, -78815232, 177192960, 336166912,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>], userId: 0
2024-09-12 08:37:41.953  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  onUnbind: Intent { act=com.google.android.gms.common.telemetry.service.START dat=chimera-action: cmp=com.google.android.gms/.chimera.PersistentApiService }
2024-09-12 08:37:41.955  7271-7271  BoundBrokerSvc          com.google.android.gms.persistent    D  onUnbind: Intent { act=com.google.android.gms.phenotype.service.START pkg=com.google.android.gms }

I have the somewhat complete startup logs
2024-09-12 10:15:56.177 28838-29294 ProfileInstaller        com.MelonCorp.FlappyMelon            D  Installing profile for com.MelonCorp.FlappyMelon
2024-09-12 10:15:56.197 28695-1418  SignInPerformer-6       com.google.android.gms               I  signIn(com.MelonCorp.FlappyMelon): sign-in timing strategy suppressed an interactive prompt: PromptGrantResult{comment=No grant: Cooldown since last grant}. [CONTEXT service_id=1 ]
2024-09-12 10:15:56.199 28695-1418  SignInPerformer-6       com.google.android.gms               I  Reporting resolvable error with suppressed resolution for [com.MelonCorp.FlappyMelon] [CONTEXT service_id=1 ]
2024-09-12 10:15:56.257 28695-1418  GamesConnectSignInOp    com.google.android.gms               I  signIn(com.MelonCorp.FlappyMelon): Returning suppressed SIGN_IN_REQUIRED for request fbz{gamePackageName=com.MelonCorp.FlappyMelon, gameUid=10181, gamePlayServicesClientLibraryVersion=12451000, sdkVariation=2101523, requestedScopes=[], callingIdentity=CallingIdentity{uid=10181, pid=28838, packageName=com.MelonCorp.FlappyMelon, playServicesClientLibraryVersion=12451000}, requestedAccount=Optional.absent(), forceResolveAccountKey=null, requestedServiceMode=0} [CONTEXT service_id=1 ]
2024-09-12 10:15:56.869 28838-28855 orp.FlappyMelo          com.MelonCorp.FlappyMelon            I  Background young concurrent copying GC freed 20761(1369KB) AllocSpace objects, 6(184KB) LOS objects, 35% free, 2808KB/4325KB, paused 3.247ms total 201.454ms
2024-09-12 10:15:59.166 28838-28855 orp.FlappyMelo          com.MelonCorp.FlappyMelon            I  Background young concurrent copying GC freed 8325(801KB) AllocSpace objects, 0(0B) LOS objects, 15% free, 3661KB/4325KB, paused 2.467ms total 146.837ms
2024-09-12 10:15:59.653 28838-28855 orp.FlappyMelo          com.MelonCorp.FlappyMelon            I  Background young concurrent copying GC freed 7849(762KB) AllocSpace objects, 0(0B) LOS objects, 15% free, 3659KB/4325KB, paused 5.015ms total 82.986ms
2024-09-12 10:16:00.120 28838-29060 Godot                   com.MelonCorp.FlappyMelon            V  OnGodotSetupCompleted
2024-09-12 10:16:00.505 28838-29060 orp.FlappyMelo          com.MelonCorp.FlappyMelon            I  The ClassLoaderContext is a special shared library.
2024-09-12 10:16:00.533 28838-29060 orp.FlappyMelo          com.MelonCorp.FlappyMelon            I  The ClassLoaderContext is a special shared library.
2024-09-12 10:16:00.554 28838-29060 orp.FlappyMelo          com.MelonCorp.FlappyMelon            I  The ClassLoaderContext is a special shared library.
2024-09-12 10:16:13.975 28838-29060 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Verification of android.content.ContentProvider com.google.android.gms.chimera.GmsAppComponentFactory.instantiateProvider(java.lang.ClassLoader, java.lang.String) took 115.548ms
2024-09-12 10:16:14.424 28838-29060 DynamiteModule          com.MelonCorp.FlappyMelon            I  Considering local module com.google.android.gms.ads.dynamite:0 and remote module com.google.android.gms.ads.dynamite:242402501
2024-09-12 10:16:14.453 28838-29060 DynamiteModule          com.MelonCorp.FlappyMelon            I  Selected remote version of com.google.android.gms.ads.dynamite, version >= 242402501
2024-09-12 10:16:14.477 28838-29060 DynamitePackage         com.MelonCorp.FlappyMelon            D  Instantiated singleton DynamitePackage.
2024-09-12 10:16:14.478 28838-29060 DynamitePackage         com.MelonCorp.FlappyMelon            D  Instantiating com.google.android.gms.ads.ChimeraMobileAdsSettingManagerCreatorImpl
2024-09-12 10:16:14.644 28838-29086 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
2024-09-12 10:16:14.709 28838-29060 Ads                     com.MelonCorp.FlappyMelon            I  Updating ad debug logging enablement.
2024-09-12 10:16:14.721 28838-29060 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
2024-09-12 10:16:14.722 28838-29086 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
2024-09-12 10:16:14.722 28838-29086 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Lsun/misc/Unsafe;->getObject(Ljava/lang/Object;J)Ljava/lang/Object; (greylist, linking, allowed)
2024-09-12 10:16:14.750 28838-29086 Ads                     com.MelonCorp.FlappyMelon            W  Update ad debug logging enablement as false
2024-09-12 10:16:14.978 28838-28855 orp.FlappyMelo          com.MelonCorp.FlappyMelon            I  Background concurrent copying GC freed 6245(369KB) AllocSpace objects, 7(764KB) LOS objects, 65% free, 3274KB/9418KB, paused 287us total 272.947ms
2024-09-12 10:16:14.988 28838-29060 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
2024-09-12 10:16:15.041 28838-29083 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
2024-09-12 10:16:15.050 28838-29060 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
2024-09-12 10:16:15.088 28838-29060 godot                   com.MelonCorp.FlappyMelon            I  Plugin found!
2024-09-12 10:16:15.089 28838-29060 GodotPlayGameServices   com.MelonCorp.FlappyMelon            D  Initializing Google Play Game Services
2024-09-12 10:16:15.089 28838-29060 SignInProxy             com.MelonCorp.FlappyMelon            D  Checking if user is authenticated
2024-09-12 10:16:15.127 28838-29060 Godot                   com.MelonCorp.FlappyMelon            V  OnGodotMainLoopStarted
2024-09-12 10:16:15.244 28838-28838 WebViewFactory          com.MelonCorp.FlappyMelon            I  Loading com.android.webview version 93.0.4577.82 (code 457708200)
2024-09-12 10:16:15.544 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Landroid/os/Trace;->isTagEnabled(J)Z (greylist, reflection, allowed)
2024-09-12 10:16:15.545 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Landroid/os/Trace;->traceBegin(JLjava/lang/String;)V (greylist, reflection, allowed)
2024-09-12 10:16:15.545 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Landroid/os/Trace;->traceEnd(J)V (greylist, reflection, allowed)
2024-09-12 10:16:15.545 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Landroid/os/Trace;->asyncTraceBegin(JLjava/lang/String;I)V (greylist, reflection, allowed)
2024-09-12 10:16:15.545 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Landroid/os/Trace;->asyncTraceEnd(JLjava/lang/String;I)V (greylist, reflection, allowed)
2024-09-12 10:16:15.567 28838-28838 cr_WVCFactoryProvider   com.MelonCorp.FlappyMelon            I  Loaded version=93.0.4577.82 minSdkVersion=21 isBundle=false multiprocess=true packageId=2
2024-09-12 10:16:15.745 28838-28838 cr_LibraryLoader        com.MelonCorp.FlappyMelon            I  Successfully loaded native library
2024-09-12 10:16:15.749 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden field Ljava/util/Collections$SynchronizedCollection;->mutex:Ljava/lang/Object; (greylist-max-o, reflection, denied)
2024-09-12 10:16:15.749 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden field Ljava/util/Collections$SynchronizedCollection;->c:Ljava/util/Collection; (greylist, reflection, allowed)
2024-09-12 10:16:15.750 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Ljava/util/Collections$SynchronizedSet;-><init>(Ljava/util/Set;Ljava/lang/Object;)V (greylist-max-o, reflection, denied)
2024-09-12 10:16:15.750 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Ljava/util/Collections$SynchronizedCollection;-><init>(Ljava/util/Collection;Ljava/lang/Object;)V (greylist-max-o, reflection, denied)
2024-09-12 10:16:15.772 28838-28838 cr_CachingUmaRecorder   com.MelonCorp.FlappyMelon            I  Flushed 7 samples from 7 histograms.
2024-09-12 10:16:15.829 28838-28838 cr_VariationsUtils      com.MelonCorp.FlappyMelon            I  Loaded seed with age 5983s
2024-09-12 10:16:15.934  2666-2695  ActivityManager         system_server                        I  Start proc 29639:com.android.webview:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:0/u0i131 for  {com.MelonCorp.FlappyMelon/org.chromium.content.app.SandboxedProcessService0:0}
2024-09-12 10:16:16.357 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Landroid/webkit/WebChromeClient;->onThemeColorChanged(Landroid/webkit/WebView;I)V (blacklist, reflection, denied)
2024-09-12 10:16:16.806 28838-28838 SignInProxy             com.MelonCorp.FlappyMelon            D  User authenticated: false
2024-09-12 10:16:16.891 28838-29692 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Landroid/media/AudioManager;->getOutputLatency(I)I (greylist, reflection, allowed)
2024-09-12 10:16:16.961 28838-29692 cr_media                com.MelonCorp.FlappyMelon            W  Requires BLUETOOTH permission
2024-09-12 10:16:18.050 28838-28838 orp.FlappyMelo          com.MelonCorp.FlappyMelon            W  Accessing hidden method Lsun/misc/Unsafe;->compareAndSwapObject(Ljava/lang/Object;JLjava/lang/Object;Ljava/lang/Object;)Z (greylist, linking, allowed)
2024-09-12 10:16:18.063 28838-28838 Ads                     com.MelonCorp.FlappyMelon            I  JS: The jsLoaded GMSG has been sent (https://googleads.g.doubleclick.net/mads/static/mad/sdk/native/production/sdk-core-v40-impl.html:788)
2024-09-12 10:16:18.064 28838-28838 chromium                com.MelonCorp.FlappyMelon            I  [INFO:CONSOLE(788)] "The jsLoaded GMSG has been sent", source: https://googleads.g.doubleclick.net/mads/static/mad/sdk/native/production/sdk-core-v40-impl.html (788)

Everything looks good in the code, but if the is_authenticated parameter is false, it should call the SingInClient.sign_in() method and then a log with Signing in/ User signed in: true should appear, and I don't see that.
Can you try making a calle directly to the SingInClient.sign_in() method in your ready function, outside of the lambda connecting to the signal, and see what happens? This shouldn't be done like that, because your code already does the call in the else branch of the if, but I don't know what else to try, je vais plaurer aussi 😢
Also, are you sure you are logged in in your google play account in the google play app in your phone?


Add an option to not give the chips focus when hitting backspace in the input field

This PR adds an option to the chips directive to disable the behavior of giving focus to the last chip when hitting backspace in the input field.
Imagine the user enters some text in the input field and holds the backspace to remove everything. The current implementation will start removing chips also since the focus moves automatically from the input field to the chips when all characters in the input field are removed.
I prefer the approach that the input field and chips are different entities. So that the user has to click arrow keys to move from the input field to chips.  Also see the similarity with using the arrow keys when the user is already inside the chips. The navigate method will only navigate between chips and will never give focus to the input field which makes sense :-)

Like I mentioned in the previous review. flag is not required. we can let the left and right arrow to navigate inside the input field instead of selecting the last chip. If user want to select the last chip from inside the chip he can press the Esc button.


[RESTEASY-2766] Upgrade Resteasy to support vert.x 4 (#2622)

[RESTEASY-2766] Vert.x 4 support added

Vert.x 4.0.0.CR2 -> 4.0.0

Testing if the Vert.X 4 upgrade is the related to the windows ci failures we have on master

This is not needed anymore. Regression isolated and fixed in https://issues.redhat.com/browse/RESTEASY-2868