Error installing node.js: The Node.js binary could not be verified.

When I run the build I receive the following error:
Sending build context to Docker daemon     75MB
Step 1/15 : FROM launcher.gcr.io/google/nodejs
 ---> d8132d024114
Step 2/15 : RUN install_node v12.16.2
 ---> Running in 80fefff9837f
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 22.0M  100 22.0M    0     0  8969k      0  0:00:02  0:00:02 --:--:-- 8969k
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4029  100  4029    0     0  11964      0 --:--:-- --:--:-- --:--:-- 11991
gpg: Signature made Wed Apr 8 19:22:22 2020 UTC using RSA key ID 5599653C gpg: Can't check signature: public key not found
The Node.js binary could not be verified.
This means it may not be an officially released Node.js binary
or may have been tampered with.

Aborting the installation.

The installation can be forced using the --ignore-verification-failure
flag. However, it is strongly recommended that you install a version
of Node.js that can be verified.

Node installation failed: /opt/gcp/runtime/bootstrap_node exited with a non-zero exit code: 1
The command '/bin/sh -c install_node v12.16.2' returned a non-zero code: 1

I have the following configuration:
# Dockerfile extending the generic Node image with application files for a
# single application.
FROM launcher.gcr.io/google/nodejs

# Check to see if the the version included in the base runtime satisfies
# '>=8.12.0', if not then do an npm install of the latest available
# version that satisfies it.
# RUN /usr/local/bin/install_node '>=12.13.0'
RUN install_node v12.16.2

When I do what is suggested it installs the node:
RUN install_node v12.16.2 --ignore-verification-failure

but clearly there is a problem somewhere.

Any update on this? I'm seeing the same error with the latest Google Cloud SDK (309.0.0)

seems the issue with node 14.10.0. you can try node version 14.9.0 then it works!

Hello @plegner
in our case, it was the same as for @aiimtechdev - App Engine installed Node 14.10.0 because we had "node": "14.x" in the package.json. Seems like the latest release has some issues.
I fixed deploy by changing the engine to a fixed version:
"engines": {
    "node": "14.9"
}

If you are using 12.x - try some of the previous version that worked.
Hope it will help!

Thanks, @prowwid! We were using ">=12.0.0" and had lots of successfully released with that until this week. Fixing the version also worked for us 😄

This error also occurs with the latest release of Node 10 10.23.0 which was released by @richardlau. His signing key is missing in the KEYS file https://github.com/GoogleCloudPlatform/nodejs-docker/blob/master/runtime-image/contents/KEYS, it was added back in july in the Node repo https://github.com/nodejs/node/pull/34397/files

In addition to my signing key, whoever maintains this repository may also want to add the keys for @ruyadorno (https://github.com/nodejs/node/pull/34628) and @danielleadams (https://github.com/nodejs/node/pull/35545) who have also been recently onboarded as releasers and may sign future releases: https://github.com/nodejs/node/blob/master/README.md#release-keys

Taking a look at this.

Okay, fixed in staging:
onmccasland-macbookpro2:nodejs-docker donmccasland$ docker run -it gcr.io/google-appengine/nodejs@sha256:058266594604d7967a371094f0631c32f93908c37e20c3354d22f1b3a63c9a17 /bin/bash
root@d9eee9e2f7c8:/app# install_node v10
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 20.2M  100 20.2M    0     0  10.6M      0  0:00:01  0:00:01 --:--:-- 10.6M
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100  4232  100  4232    0     0  14452      0 --:--:-- --:--:-- --:--:-- 14493
node-v10.23.0-linux-x64.tar.gz: OK
Installed Node.js v10.23.0
Starting the release process..

Fixed.

Occurring in GAE flex again with 14.x set.
Step #1: INFO[0047] RUN /usr/local/bin/install_node '14.x'
Step #1: INFO[0047] cmd: /bin/sh
Step #1: INFO[0047] args: [-c /usr/local/bin/install_node '14.x']
Step #1:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #1:                                  Dload  Upload   Total   Spent    Left  Speed
100 32.3M  100 32.3M    0     0  43.1M      0 --:--:-- --:--:-- --:--:-- 43.2M
Step #1:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #1:                                  Dload  Upload   Total   Spent    Left  Speed
100  3835  100  3835    0     0  24299      0 --:--:-- --:--:-- --:--:-- 24426
Step #1: gpg: Signature made Tue May 11 23:13:29 2021 UTC using RSA key ID 643B6201 gpg: Can't check signature: public key not found
Step #1: The Node.js binary could not be verified.
Step #1: This means it may not be an officially released Node.js binary
Step #1: or may have been tampered with.
Step #1:
Step #1: Aborting the installation.
Step #1:
Step #1: The installation can be forced using the --ignore-verification-failure
Step #1: flag. However, it is strongly recommended that you install a version
Step #1: of Node.js that can be verified.
Step #1:
Step #1: Node installation failed: /opt/gcp/runtime/bootstrap_node exited with a non-zero exit code: 1
Step #1: error building image: error building stage: waiting for process to exit: exit status 1
Finished Step #1
ERROR
ERROR: build step 1 "gcr.io/kaniko-project/executor@sha256:f87c11770a4d3ed33436508d206c584812cd656e6ed08eda1cff5c1ee44f5870" failed: step exited with non-zero status: 1

I confirm: 14.17.0 is having that same issue. Note: 14.16.0 works fine.

I've the same problem using Google App Engine Flex & Standard: if I downgrade to 14.16. using "engines": { "node": "^14"  } in my package.json I'd work but if I deploy the package in another environment using the standard environment it would again result in an error-message because of the wrong version:
The 'package.json' configuration file must specify a supported nodejs14 version that is compatible with the runtime specified in the deployment. Please pin your application to a compatible major version of the runtime via the 'engines.node' property. Supported 'engines.node' values for the runtime 'nodejs14' are: [14.x.x, 14.X.X, 14.x, 14.X, 14.*.*, 14.*, ~14, ~14.0, ~14.0.0, 14, ^14, ^14.0, ^14.0.0, >=14, >=14.0, >=14.0.0, >14.0, >14.0.0, >=1, >=1.0, >=1.0.0, >1, >1.0, >1.0.0, >=2, >=2.0, >=2.0.0, >2, >2.0, >2.0.0, >=3, >=3.0, >=3.0.0, >3, >3.0, >3.0.0, >=4, >=4.0, >=4.0.0, >4, >4.0, >4.0.0, >=5, >=5.0, >=5.0.0, >5, >5.0, >5.0.0, >=6, >=6.0, >=6.0.0, >6, >6.0, >6.0.0, >=7, >=7.0, >=7.0.0, >7, >7.0, >7.0.0, >=8, >=8.0, >=8.0.0, >8, >8.0, >8.0.0, >=9, >=9.0, >=9.0.0, >9, >9.0, >9.0.0, >=10, >=10.0, >=10.0.0, >10, >10.0, >10.0.0, >=11, >=11.0, >=11.0.0, >11, >11.0, >11.0.0, >=12, >=12.0, >=12.0.0, >12, >12.0, >12.0.0, >=13, >=13.0, >=13.0.0, >13, >13.0, >13.0.0].

So this should be updated in both environments.

Seems even v14.16 now has key issues (expired):
gpg: Signature made 02/23/21 13:00:40 GMT Standard Time using RSA key ID A1AB005C
gpg: Good signature from "Beth Griggs<EMAIL_ADDRESS>[expired]
gpg:                 aka "Beth Griggs<EMAIL_ADDRESS>[expired]
gpg: Note: This key has expired!
Primary key fingerprint: 4ED7 78F5 39E3 634C 779C  87C6 D706 2848 A1AB 005C

@pete-beresford-bzy, Hmm...I extended my key back in March but it seems it hasn't properly propagated/synced with the servers - I'll try resyncing/resubmitting.

Why can't AppEngine just pick the last supported version of Node if a range like 14.x is specified in package.json?
Even if we manually specify a supported version like 14.16, the engines key is automatically updated by scripts like Renovate, and it is quite annoying if that leads to unpredictable deployment failures…

Are there still issues with 14.7.0? Like @BethGriggs my key was synced a few months ago (Back in January, it looks like https://github.com/nodejs/node/pull/36793), but I've just recently resubmitted/resynched it again to confirm.

Same as what @brunogabuzomeu said, we tempoarily solved it by using =16.10.0 which still works.

Same issue here, GAE Flex with "engines": { "node": "14.x"},. Was working on monday (2021-10-11).
I guess KEYS file need to be updated again.
I will try downgrading to unblock deployment, but I'm definitvely not a fan of this solution.
Could KEY file updates be automated to prevent such issue to periodically happen ?

I had same issue for node12.22.7 today.
I have specified node: ^12.22.1 in package.json and failed.
Next I ran with node: 12.22.7 and it failed.
Finally I ran with node: 12.22.6 and it worked.
according to the nodejs releases, 12.22.7 has been released at 2021/10/12, so I guess that's where it got broken.

I checked the key list, it seems Danielle's key is in:
https://github.com/GoogleCloudPlatform/nodejs-docker/blob/master/runtime-image/bin/gen_keys.sh#L23
https://github.com/nodejs/node#release-keys

@chiefy ah, thanks a lot! I haven't check repository close enough 🤦🏽♂
I'll keep in my mind in case we have next update.

@donmccasland
I haven't seen any updates on https://github.com/GoogleCloudPlatform/nodejs-docker/pull/225.
Is there any thing that I can help?

works for me now with 14.18.2. I think this issue is good to close

It should probably remain open until ongoing fix is found.
On Fri, 3 Dec 2021 at 12:50, Oleksii Kachan @.***>
wrote:

works for me now with 14.18.2. I think this issue is good to close
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/nodejs-docker/issues/214#issuecomment-985147480,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADDR7UZ5ZJQ5BNUBPEHMPDUPAO4VANCNFSM4MI6GDGA
.

Specifying "engines": { "node": "14.18.0" }, still throws the error for me on GAE Flex during build:

Step #1: Step #1: error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "14.18.0". Got "12.19.0"

Is this fix supposed to fix the build processes as well?

@geiszla your issue seems irrelevant to this issue. The fix mentioned in abo ve is about using latest version fails due to GPG key mismatch.
Your issue is about mismatch of runtime node version and engine version specified in package.json.

I am sseing a similar issue for 16.4.x
It seems to have started from 2022-03-26
Step #1: INFO[0022] COPY . /app/
Step #1: INFO[0022] Taking snapshot of files...
Step #1: INFO[0023] RUN /usr/local/bin/install_node '>=16.4.x'
Step #1: INFO[0023] cmd: /bin/sh
Step #1: INFO[0023] args: [-c /usr/local/bin/install_node '>=16.4.x']
Step #1:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #1:                                  Dload  Upload   Total   Spent    Left  Speed
100 40.9M  100 40.9M    0     0   102M      0 --:--:-- --:--:-- --:--:--  102M
Step #1:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #1:                                  Dload  Upload   Total   Spent    Left  Speed
100  4009  100  4009    0     0  41326      0 --:--:-- --:--:-- --:--:-- 41760
Step #1: gpg: Signature made Tue Mar 22 14:38:58 2022 UTC using RSA key ID E57C7D57 gpg: Can't check signature: public key not found
Step #1: The Node.js binary could not be verified.
Step #1: This means it may not be an officially released Node.js binary
Step #1: or may have been tampered with.
Step #1:
Step #1: Aborting the installation.
Step #1:
Step #1: The installation can be forced using the --ignore-verification-failure
Step #1: flag. However, it is strongly recommended that you install a version
Step #1: of Node.js that can be verified.

am sseing a similar issue for 16.4.x

@chiefy apologies, I should have provided more context. I have raised an issue with GCP, who have managed to reproduce it. https://issuetracker.google.com/issues/227382491
As it was a similar error to the one reported here, and this is a GCP repo, I had assumed this would be an appropriate place to report it.  I have since learnt that there are many GCP nodejs repos, and I am not sure this is the one used by the AppEngine flex environment that I am using.

@niciliketo the 😕 was for the maintainers, sorry. Disappointing this hasn't been taken care of yet?

FYI, fix is almost ready. We plan to release it to prod tomorrow 4/5/2022.

@jinglundong update?

I verified this fix in prod with "16.4.x" in package.json and "runtime: node" in app.yaml. This should have been fixed. Please let me know if this is still an issue for you.
We are going to add end to end tests that execute this fuzzy version behavior. Hope we detect this type of issue faster next time.

@jinglundong Still not working on our side

@jinglundong thanks for the update.
I tried using 14.x and 14.18.x and neither worked.
It did work with 16.13.x as you had verified for v16

@jinglundong Still not working on our side

Sorry to hear that. Could you share instructions to reproduce the problem?

@jinglundong here is the node version from my package.json
  "engines": {
    "node": "14.x",
    "npm": ">=6.0.0"
  }

app.yaml
runtime: nodejs

manual_scaling:
  instances: 1

resources:
  cpu: 1
  memory_gb: 0.5
  disk_size_gb: 10

I couldn't reproduce the error with
  "engines": {
    "node": "14.x",
    "npm": ">=6.0.0"
  }

When I deploy, the version picked were: "Installed Node.js v14.19.1" and "Installed<EMAIL_ADDRESS>with binaries". Could you try this combination. Another idea is to use node >= 14.x.

@jinglundong I have almost the same configuration:
  "engines": {
    "node": "14.x",
    "npm": ">=6.0.0"
  }

runtime: nodejs

env: flex

# Resources configuration (for each server)
resources:
  cpu: 1
  memory_gb: 2
  disk_size_gb: 10

# Configuration of automatic scaling
# block max_num_instance (3)
automatic_scaling:
  min_num_instances: 1
  max_num_instances: 1
  cool_down_period_sec: 180
  cpu_utilization:
    target_utilization: 0.6
# [END app_yaml]

Step #1: yarn install v1.22.18
Step #1: [1/5] Validating package.json...
Step #1: error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "14.x". Got "12.19.0"
Step #1: error Found incompatible module.
Step #1: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Step #1: error building image: error building stage: waiting for process to exit: exit status 1
Finished Step #1

@ishak-lm I think this is a different issue. "The engine "node" is incompatible with this module. Expected version "14.x". Got "12.19.0" is not complaining about the pgp key. Could you file another issue and try the specific version that I suggested? node: 14.19.1 and npm: 8.6.0?
I'm going to close this issue for now. If anyone's still seeing Can't check signature: public key not found The Node.js binary could not be verified. please reopen.

Just to note, this is going to have to be re-opened the next time a new GPG key is added, the problem wasn't solved.

That is correct. I'm listing a few ideas below following my preferred order, but I haven't had a chance to figure out the details. Please advice if anyone has better solutions.

We have a plan to simplify how we build Flex applications. I believe it's going to solve this problem, or at least be able to fix it in a few days. This is the actual fix, but it will likely take around two quarters.
If new keys are added and announced before they are being used (which would cause the GPG check failure), we are happy to monitor that list of keys more closely. This is a short term solution.
We may have a way to detach from latest, and pin to a relatively new node version. Not always using the latest version of node may cause problems for some users too.

A heads-up, nodejs 18.0.0 is out today. Our internal test seems to be telling me that we don't support it automatically. A mitigation could be limit the nodejs version to < 18.0.0.

Experiencing this error today with Node 18.5.0.

Sorry to hear that. We plan to support Node 18 before year end 2022. The solution was to modernize how we support and build Flex node applications. Our goal is to accelerate the new version support in the future. We will keep this issue updated, especially when Node 18 is ready for private/public preview.

Is there an explicit list of which specific minor versions of Node aren't going to trigger this problem?

I experienced this issue today. I couldn't see anywhere which version the system was attempting to install anywhere in the logs.
In the failing case, I saw:
Step #2: INFO[0105] RUN /usr/local/bin/install_node '14.x'
Step #2: INFO[0105] cmd: /bin/sh
Step #2: INFO[0105] args: [-c /usr/local/bin/install_node '14.x']
Step #2:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #2:                                  Dload  Upload   Total   Spent    Left  Speed
100 32.9M  100 32.9M    0     0  77.6M      0 --:--:-- --:--:-- --:--:-- 77.7M
Step #2:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #2:                                  Dload  Upload   Total   Spent    Left  Speed
100  3835  100  3835    0     0  35435      0 --:--:-- --:--:-- --:--:-- 35841
Step #2: gpg: Signature made Fri Sep 23 16:05:56 2022 UTC using RSA key ID E57C7D57 gpg: Can't check signature: public key not found
Step #2: The Node.js binary could not be verified.
Step #2: This means it may not be an officially released Node.js binary
Step #2: or may have been tampered with.

Looking at the date of September 23rd and our restriction to Node 14.x, it looks like 14.20.1 was released on that day, but it would have been helpful if the logs showed which version was being attempted.
In a successful installation (package.json engine version restricted to 14.19), the immediate next step shows the full installed version number:
Step #2: INFO[0102] RUN /usr/local/bin/install_node '14.19'
Step #2: INFO[0102] cmd: /bin/sh
Step #2: INFO[0102] args: [-c /usr/local/bin/install_node '14.19']
Step #2:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #2:                                  Dload  Upload   Total   Spent    Left  Speed
100 32.9M  100 32.9M    0     0  59.2M      0 --:--:-- --:--:-- --:--:-- 59.1M
Step #2:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #2:                                  Dload  Upload   Total   Spent    Left  Speed
100  3835  100  3835    0     0  19242      0 --:--:-- --:--:-- --:--:-- 19271
Step #2: node-v14.19.3-linux-x64.tar.gz: OK
Step #2: Installed Node.js v14.19.3

This started failing again today for node 16.x. Observed that node published a release circa 11AM today.
Step #2: gpg: Signature made Wed Oct 12 14:48:44 2022 UTC using RSA key ID 94EC4689 gpg: Can't check signature: public key not found
Step #2: The Node.js binary could not be verified.
Step #2: This means it may not be an officially released Node.js binary
Step #2: or may have been tampered with.
Step #2:
Step #2: Aborting the installation.
Step #2:
Step #2: The installation can be forced using the --ignore-verification-failure
Step #2: flag. However, it is strongly recommended that you install a version
Step #2: of Node.js that can be verified.
Step #2:
Step #2: Node installation failed: /opt/gcp/runtime/bootstrap_node exited with a non-zero exit code: 1
Step #2: error building image: error building stage: waiting for process to exit: exit status 1
Finished Step #2

What can we do to be insulated from this error without having to pin versions in our application itself?

tl;dr: I can take a look at the new key and probably update it. To mitigate the problem, please pin it to the previous patch version of Node.js 16.17.x or Node.js 16.17.1. https://nodejs.org/en/download/releases/
I haven't looked into the exact problem, but I'd suspect that it's broken because there's a new pgp key in Node.js 16.18. This means our builder (or nodejs itself) is not entirely backward compatible between minor version upgrades.
This is a known issue where we don't really have a short term automation on our side. The best option in to pin to a patch version of nodejs version. Because new pgp keys are getting added along with new patch version of nodejs. We don't have a way to detect that, or block anyone from picking it up immediately when they have something like 16.x.
We are still working on a project to improve our build system. Once that's complete, we should be able to control this behavior - we will qualify the new minor or patch version before the builder using it.

@jinglundong
Thanks for sharing.
We've used that pinned solution in the past and have, indeed, already deployed such a fix today.
I recognize that this isn't your problem per se, but I do want to explicitly point out the fact that a recommendation to fix a deployment issue in one Google Infrastructure component actually introduces a new issue in a separate Google infrastructure component.
Google Cloud Functions deployments will raise an error if a package.json when engine is not a whole number (anything other than 12,14,16, etc..) ... but the solution recommended here requires specifying an engine value other than the above (e.g. 16.17.1).
The result is that, without additional work, app engine deploys succeed and function deployments fail. This is in a monorepo where splitting the systems is impractical, even if possible.
To support both, our build systems basically do a sed to modify the pinned version for AppEngine to just a whole number for Functions.
In any case, thansk for hearing me out.
We really appreciate the work y'all do to keep GCP stable and performant.

Hi folks - We're hitting this issue as well with our NodeJS app engine deployment. We were running 16.x. Unfortunately, pinning doe not appear to be working on our end.
Here's a trace:
Step #2: INFO[0017] Taking snapshot of full filesystem...
Step #2: INFO[0024] Using files from context: [/workspace]
Step #2: INFO[0024] COPY . /app/
Step #2: INFO[0024] Taking snapshot of files...
Step #2: INFO[0026] RUN /usr/local/bin/install_node '^16.17.x'
Step #2: INFO[0026] cmd: /bin/sh
Step #2: INFO[0026] args: [-c /usr/local/bin/install_node '^16.17.x']
Step #2:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #2:                                  Dload  Upload   Total   Spent    Left  Speed
100 32.3M  100 32.3M    0     0  90.4M      0 --:--:-- --:--:-- --:--:-- 90.6M
Step #2:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Step #2:                                  Dload  Upload   Total   Spent    Left  Speed
100  4035  100  4035    0     0  46219      0 --:--:-- --:--:-- --:--:-- 46379
Step #2: gpg: Signature made Wed Oct 12 14:48:44 2022 UTC using RSA key ID 94EC4689 gpg: Can't check signature: public key not found
Step #2: The Node.js binary could not be verified.
Step #2: This means it may not be an officially released Node.js binary
Step #2: or may have been tampered with.
Step #2:
Step #2: Aborting the installation.
Step #2:
Step #2: The installation can be forced using the --ignore-verification-failure
Step #2: flag. However, it is strongly recommended that you install a version
Step #2: of Node.js that can be verified.
Step #2:
Step #2: Node installation failed: /opt/gcp/runtime/bootstrap_node exited with a non-zero exit code: 1
Step #2: error building image: error building stage: waiting for process to exit: exit status 1
Finished Step #2
ERROR
ERROR: build step 2 "gcr.io/kaniko-project/executor@sha256:f87c11770a4d3ed33436508d206c584812cd656e6ed08eda1cff5c1ee44f5870" failed: step exited with non-zero status: 1

We updated the key at https://github.com/GoogleCloudPlatform/nodejs-docker/pull/254 and https://github.com/GoogleCloudPlatform/nodejs-docker/pull/256. I verified this in prod with a 16.x app that got resolved to 16.18.1. Please let us know if you have any other questions.
To be clear, this doesn't solve the problem of 18.x. Node.js 18 support requires a bigger effort. We have it planned in the first half of 2023.

@jinglundong is there any reason why it would not even try and run an install of the node version specifed in the package.json? We have our engine specified and have tried pinning to 16.17.1 but it doesn't even attempt an install. Please see the output below:
FETCHSOURCE
BUILD
Starting Step #0 - "fetcher"
Step #0 - "fetcher": Already have image (with digest): gcr.io/cloud-builders/gcs-fetcher
Step #0 - "fetcher": Fetching manifest gs://staging.****************.appspot.com/ae/5d15c126-2759-4b47-926a-5ee0ae1a4f93/manifest.json.
Step #0 - "fetcher": Processing 112 files.
Step #0 - "fetcher": ******************************************************
Step #0 - "fetcher": Status:                      SUCCESS
Step #0 - "fetcher": Started:                     2022-11-08T04:47:33Z
Step #0 - "fetcher": Completed:                   2022-11-08T04:47:33Z
Step #0 - "fetcher": Requested workers:    200
Step #0 - "fetcher": Actual workers:       112
Step #0 - "fetcher": Total files:          112
Step #0 - "fetcher": Total retries:          0
Step #0 - "fetcher": GCS timeouts:           0
Step #0 - "fetcher": MiB downloaded:         0.49 MiB
Step #0 - "fetcher": MiB/s throughput:       2.57 MiB/s
Step #0 - "fetcher": Time for manifest:    104.01 ms
Step #0 - "fetcher": Total time:             0.30 s
Step #0 - "fetcher": ******************************************************
Finished Step #0 - "fetcher"
Starting Step #1
Step #1: Pulling image: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:8e2b8eef87fae1bc4b80206cc84139a52973433daafef5ba30ae84f2f85d01b6
Step #1: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:8e2b8eef87fae1bc4b80206cc84139a52973433daafef5ba30ae84f2f85d01b6: Pulling from gcp-runtimes/nodejs/gen-dockerfile
Step #1: Digest: sha256:8e2b8eef87fae1bc4b80206cc84139a52973433daafef5ba30ae84f2f85d01b6
Step #1: Status: Downloaded newer image for gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:8e2b8eef87fae1bc4b80206cc84139a52973433daafef5ba30ae84f2f85d01b6
Step #1: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:8e2b8eef87fae1bc4b80206cc84139a52973433daafef5ba30ae84f2f85d01b6
Step #1: Checking for Node.js.
Finished Step #1
Starting Step #2
Step #2: Already have image (with digest): gcr.io/kaniko-project/executor@sha256:f87c11770a4d3ed33436508d206c584812cd656e6ed08eda1cff5c1ee44f5870
Step #2: INFO[0000] Removing ignored files from build context: [node_modules .dockerignore Dockerfile npm-*****.log yarn-error.log .git .hg .svn app.yaml]
Step #2: INFO[0000] Downloading base image gcr.io/google-appengine/nodejs@sha256:f4979bc91ed28ae6fc489b5377fb87d628263fe7a7da971b134c03aff47327b2
Step #2: INFO[0017] Taking snapshot of full filesystem...
Step #2: INFO[0024] Using files from context: [/workspace]
Step #2: INFO[0024] COPY . /app/
Step #2: INFO[0024] RUN NODE_ENV=*********** yarn install ||   ((if [ -f yarn-error.log ]; then       cat yarn-error.log;     fi) && false)
Step #2: INFO[0024] cmd: /bin/sh
Step #2: INFO[0024] args: [-c NODE_ENV=*********** yarn install ||   ((if [ -f yarn-error.log ]; then       cat yarn-error.log;     fi) && false)]
Step #2: yarn install v1.22.19
Step #2: [1/5] Validating package.json...
Step #2: error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "16.17.1". Got "12.19.0"
Step #2: error Found incompatible module

@m-s-morgan Hi Matt, if my following analysis is moving towards the right direction, could you file a different issue?
I'm seeing the error at step #2, which looks like a version conflict between yarn v1.22.19 and nodejs 16.18.1.
Step #2: yarn install v1.22.19
Step #2: [1/5] Validating package.json...
Step #2: error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "16.17.1". Got "12.19.0"

A few actionable ideas:

Would you be able to start the app locally? Like yarn start.
Do you mind sharing the related section of your package.json and/or the lock file?

@m-s-morgan I wasn't able to reproduce somehow. However, the most likely suspect is
<% if (config.canInstallDeps) { %>
  <% if (config.useYarn) { %>
RUN NODE_ENV=development yarn install || \
  ((if [ -f yarn-error.log ]; then \
      cat yarn-error.log; \
    fi) && false)
  <% } else { %>
# You have to specify "--unsafe-perm" with npm install
# when running as root.  Failing to do this can cause
# install to appear to succeed even if a preinstall
# script fails, and may have other adverse consequences
# as well.
# This command will also cat the npm-debug.log file after the
# build, if it exists.
RUN NODE_ENV=development npm install --unsafe-perm || \
  ((if [ -f npm-debug.log ]; then \
      cat npm-debug.log; \
    fi) && false)
  <% } %>
<% } %>
RUN npm run gcp-build
  <% if (config.canInstallDeps) { %>
RUN rm -Rf node_modules
  <% } %>

in here
is being called somehow before the RUN /usr/local/bin/install_node '16.17.1' .

@m-s-morgan I think https://github.com/GoogleCloudPlatform/nodejs-docker/issues/233#issuecomment-1309663883 is the tracking bug for the issue you are experiencing. I shared more details from my investigation with Kenneth.

@jinglundong @kennethye1 I'm assuming the yarn install here
  <% if (config.useYarn) { %>
RUN NODE_ENV=development yarn install || \

is causing the issue. The first thing that command does is check the package.json. The node binary installed by the runtime is 12.19.0 and the package.json has the node version pinned to 16.17.1. This of course is going to cause a failure. I believe the docker file needs to install the specified config node version before running the above code as it does a few steps later.

Let's track this issue at https://github.com/GoogleCloudPlatform/nodejs-docker/issues/233 if you don't mind.

you can change engine's sub node version to fix it.
in my case, I fixed node: 14.16

How is this still an issue, trying to use node v16 and getting this, trying to use node LTS v18 and getting glib errors https://github.com/GoogleCloudPlatform/buildpacks/issues/198
almost impossible to use app engine for anything critical these days

Hi @REPTILEHAUS, I've updated the KEYS. For nodejs 18 and later, please follow https://cloud.google.com/appengine/docs/flexible/nodejs/runtime#newversions.


Joins being dropped when specifying multiple fields in select_related

Hello again. I have an issue with using multiple tables in select_related that results in the incorrect SQL being generated.
Using these tables as an example (irrelevant fields omitted):
class User(orm.Model, BaseUser):
    pass

class Track(orm.Model):
    pass

class Post(orm.Model):
    track = orm.ForeignKey(Track, allow_null=True)
    author = orm.ForeignKey(User)

And using this query to illustrate:
posts = await Post.objects.select_related(['track','author']).all()

With this query, some JOIN expressions are dropped from the resulting SQL, so it looks something like this:
SELECT [fields] FROM track, post JOIN "user" ON "user".id = post.author

What I'd expect to see is the track table also getting a JOIN expression, rather than just appearing in the FROM. This results in the incorrect behaviour of, as far as I can make out, joining every combination of track and post together. (I didn't even realise this was valid SQL, so I've learned something.)
I believe the issue is redefining select_from here, in models.py:
def build_select_expression(self):
        tables = [self.table]
        select_from = self.table

        for item in self._select_related:
            model_cls = self.model_cls
            select_from = self.table # this is the culprit
            for part in item.split("__"):
                model_cls = model_cls.fields[part].to
                select_from = sqlalchemy.sql.join(select_from, model_cls.__table__)
                tables.append(model_cls.__table__)

I think the core problem is the redefinition of select_from on line 76, as this stops the joins from being built up each time through the loop. So if that line is removed, it seems to solve the issue.

Hi,
This project seems stale and from what I saw on encode page it's not a priority right now. Since I was tired with reinventing the wheel and needed something as soon as possible I created ormar package, that was inspired by this one.
Ormar bases its validation on pydantic so it can be used directly with fastapi as response and request models.
This issue was implemented in ormar, so feel free to check it  out: https://github.com/collerek/ormar


Switch CircleCI build VM to 14.04 and make the CI tests pass

The 14.04 VM includes go1.6 which uses vendor/.

This is not the first time that joffrey/docker-py tests fail. In the past we fixed things w/o pinning. Given that the purpose of the tests is to check that the proxy is faithfully handling all docker traffic - regardless of version - I rather think pinning is a bad idea.

The pinning to 1.8.1 is required because the latest version of joffrey/docker-py tests requires 1.24 Docker API (=> 1.12.x Docker). Unfortunately, 1.12.x Docker is very unreliable and hangs from time to time during a run of the smoke tests.
I've created a separate issue for switching back to joffrey/docker-py:latest and 1.12.1 Docker: https://github.com/weaveworks/weave/issues/2499

the latest version of joffrey/docker-py tests requires 1.24 Docker

@martynas That is a bug in docker-py. The docker-py tests are annotated with version information, so only tests for the right version should be run.

We should not be pinning the joffrey/docker-py image.

Hmm. The docker-py tests really ought to work out the server version by themselves. Alas I cannot find any code in docker-py that actually does that. I was convinced we had run into this sort of problem before, but have not been able to find an issue/pr in weave or docker-py for it, so I must have been imagining it.
I am perplexed what the purpose of the version annotations in the tests is when there is no way to actually run the tests with a version other than DEFAULT_DOCKER_API_VERSION, which is set to 1.24 in the latest docker-py.

https://github.com/docker/docker-py/issues/1183


Accept any type that can be turned into a path reference for load

This commit makes a2lfile::load more flexible in what it accepts as type for a file path. This includes &str, &OsStr, &OsString, &String and &Path. See for more details.
The change is unlikely to break existing code in practice, i.e.,
a2lfile::load(&std::ffi::OsString::from("example.a2l"), ...);

still works.
The downside, of course, is that it makes the type signature more complicated, but it's the same type signature as File::open.

Thumbs up, I like it!


[GraphEdit] Add a note about the behavior of get_children()

Stopgap measure for #91857.
Possible long term solutions could be:

Add a get_graph_elements() method which only returns the graph elements
Add a get_connection_layer_index() method to retrieve the index of the connection layer (to filter it out manually)
Implement internal nodes at arbitrary positions

Needs a rebase to fix CI.

Thanks!


net: Dial ignores second result of Context.Deadline()

What version of Go are you using (go version)?

$ go version
go version devel +3f21c2381d Thu Nov 14 01:57:00 2019 +0000 linux/amd64

Actually, the issue is pretty old. I've reproduced it on both 1.12 and 1.13 versions.
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/sz/.cache/go-build"
GOENV="/home/sz/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/sz/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/sz/src/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/sz/src/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/sz/src/go/src/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build617450948=/tmp/go-build -gno-record-gcc-switches"

What did you do?
https://play.golang.org/p/oMNspjAQkeX
What did you expect to see?
It is expected to get "Connection refused" error.
What did you see instead?
"i/o timeout" is returned.

I will submit a PR with fix shortly.


Ignore secrets that will be deleted after rendering

Changes in this PR:

I ran python-black on hooks/forbid_secrets.py
hooks/forbid_secrets.py now ignores kustomize patches to delete a secret

Example:
kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
patchesStrategicMerge:
  - patches/example.yaml

patches/example.yaml
apiVersion: v1
kind: Secret
metadata:
  name: mysql-secret
$patch: delete

Output from tests
$  python3 hooks/forbid_secrets.py tests/secret-fail.yaml
Unencrypted Kubernetes secret detected in file: tests/secret-fail.yaml
$  python3 hooks/forbid_secrets.py tests/secret-pass.yaml
$  echo $?
0
$  python3 hooks/forbid_secrets.py tests/secret-kustomize-pass.y*
$  python3 hooks/forbid_secrets.py tests/secret-kustomize-pass.yaml
$  echo $?
0

Hey, thanks for the PR, would it be possible to add an example to the tests folder?

@onedr0p  Yes, give me a moment

@onedr0p tests added

Thanks, I am pulling this PR and will look it over. Expect a release soon. 👍🏼

Thanks @onedr0p


Update sbt to 1.6.2

Updates org.scala-sbt:sbt from 1.5.8 to 1.6.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Codecov Report

Merging #122 (7a62df2) into master (acc035a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #122   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            9         9
=========================================
  Hits             9         9

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update acc035a...7a62df2. Read the comment docs.

Superseded by #134.


[PSA] Map extern in psa

Map extern is somewhat counter-intuitive because we have tables in P4. However, we cannot apply tables in the parser. There may be use cases of parsing a packet differently depending on the ingress port. A common example being a packet from the controller with some controller-defined header.
However, as we have discussed at length, we cannot rely on the value of the ingress_port in standard metadata, so we need to have a mapping (outside P4) from the ingress_port to some logical notion of a singleton port. If we want to do this mapping in the parser, I don't see any other option except an extern.
So, I would like to propose the following extern:
// BEGIN:Map_extern
extern Map<K, V> {
/// Create a map with at most size entries.
Map(bit<32> size);
/// Get value from key.
V at(in K key);
}
The map can be populated through P4Runtime API (like we do for action profiles and selectors) or through some other config mechanism. We can discuss the actual control plane API, but it would essential add, modify and remove the key, value pairs.
Targets may implement the map extern using a hardware table, just as they may do for action profiles and selectors.

Why not use a register?

Good point! I didn't realize we can have an arbitrary index into a register. One minor issue is that ideally, we don't want the dataplane to be able to modify the register. But I suppose this is use case dependent.

There is also the ValueSet extern which is defined in the PSA, intended for use in parsers only, which lets the control plane populate a set of values that at P4 forwarding time can be used to determine whether a value (like ingress_port) is in that set or not.  I would have thought that using this for ingress-port-specific modifications to how packets were parsed is one of the prime use cases for this extern.

Thanks Andy and Mihai. We can use register to map ingress_port to some controller-defined port number and ValueSet to make parser decisions. I am closing this issue now.

Actually, on a closer read of the PSA spec, I noticed that the register extern is intended to be used as a HW register file, with an index range of 0 to size-1.
"access to an index of a register that is at least the size of the register is out of bounds.  An out of
bounds write has no effect on the state of the system.  An out of bounds read returns an undefined value."
So, at least as per the current spec, we cannot really use register as a map. I am also mildly concerned about the dataplane program being able to modify the register contents.
@jafingerhut @cc10512 are we OK with generalizing the definition of register to be a map in PSA?

IMHO, the implementation of value_set provides the mapping mechanism you will need. In addition, this mapping is software-programmed (think hardware MMU managed by the OS, here OS is your controller, MMU is the value_set). Instead of redefining a new primitive, we should think about reusing existing primitive as much as possible.

+1 on @jafingerhut  and @hanw responses. ValueSet is exactly the extern you need. Please, note that if you define it to take PortId_t as the input, then the APIs/Driver can perform the remapping for you as per our earlier discussion.

@samar-abdi If your goal is to have some ingress ports support parsing of some kinds of headers in packets, but those headers should not be parsed in packets received from other ports, and you want that set of ports to be configurable by the control plane, ValueSet alone can do this, without any need to use the Register extern.  One way would be to create a ValueSet instance "supports_protocol_foo", where the 'key' is wide enough to take a PortId_t type.  In the parser code you could do an assignment like "meta.my_meta.foo_supported = supports_protocol_foo.is_member(istd.ingress_port);", then later transition select statements in the parser can use meta.my_meta.foo_supported as the only field, or one of several fields, to select the next parser state.
The latest version of the PSA specifies that the Register extern is only required to be supported in the Ingress and Egress control blocks, and need not be supported in parsers (see the table in Section 4.1 "Restrictions on where externs may be used" -- that text isn't necessarily final, as everything in the latest PSA isn't yet final).

Thanks @jafingerhut @hanw. I agree that selective parsing can be done with value-sets. That enables using a table to do the mapping from standard metadata ports to controller-defined ports after parsing.


cex.io: added 'fetchOpenOrders()'

Not sure I understand this build process completely.
So I updated ccxt.js and it works for me. It seems there is an issue with a transpiler or I'm supposed to build it in some unusual way?

@mkutny hi! Thx for the pull request! I'm merging it! )
As for your question, the transpilation process and the rules are here: https://github.com/ccxt-dev/ccxt/blob/master/CONTRIBUTING.md#derived-exchange-classes
    parseOrder(order) { // ← space before ( missed
      return {
        'id':        order.id,        // ← extra spaces violate PEP8
        'datetime':  this.iso8601(parseInt(order.time)), // ← dot access instead of key access, no spaces
        'timestamp': order.time,      // ← dot access instead of key access,
        'status':    'open',
        'symbol':    order.symbol1 + '/' + order.symbol2,
        'type':      undefined,
        'side':      order.type,
        'price':     order.price,
        'amount':    order.amount,
        'filled':    order.amount - order.pending,
        'remaining': order.pending,
        'trades':    undefined,
        'fee':       undefined,
        'info':      order,
      }
    },

    async fetchOpenOrders(symbol = undefined, params = {}) { // space missed before (
      if (!symbol)
          throw new ExchangeError (this.id + ' requires a symbol');
                                                                               // ← an empty line inside the derived method
      await this.loadMarkets();
      const orders = await this.privatePostOpenOrders(symbol); // ← this method accepts a dictionary
      return this.parseOrders(orders);
                                                                               // ← another empty line
    },

Basically, the general rule is that the transpiler works with regexps line by line and the spacing is critical for PEP8 and for several special cases. But don't worry, I'll merge it anyway. Thx a lot!

Ok, it has arrived in v.1.9.73+! )
Let us know if you have any difficulty with it. Thx for your help, it is very welcome and it really means a lot to us!
Cheers!

@mkutny looks like it's there ) Please update to 1.9.75+ before trying it. Best wishes.

Now it works like a charm, great!


removed  windows  path

as per user report #5312 , so i   removed the invalid path and added the correct path.

@RAJU2529 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@MicrosoftGuyJFlo: I'm sorry - only the author of this article, @eross-msft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@PRMerger14 . When this PR #5314  will merge.

@RAJU2529 : I am fairly certain that @PRMerger14 is only a bot and will not respond to regular comments from users, unless they contain special commands or macros. I will do what I can to add some focus to this.

#sign-off

@illfated: I'm sorry - only the author of this article, @eross-msft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Yes, I know. My comment is based on an agreement with the MS Docs team.

#sign-off

@MicrosoftGuyJFlo: I'm sorry - only the author of this article, @eross-msft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


ofnet support portRange

Describe the problem/challenge you have
Per issue #1325, we want to support a range of ports in Antrea NetworkPolicy CRDs and we need support from ofnet.
Since OVS provides port/mask format as a solution of a range of ports, ofnet should also support port/mask format and provide related interfaces.

/cc @Dyanngg


🚀 Feature Request: next-on-pages --remote D1

Describe the solution
Could --remote flag be supported for next-on-pages projects using D1 please?
I'd like this to work:
npm run pages:build && wrangler pages dev .vercel/output/static --compatibility-date=2024-01-17 --compatibility-flag=nodejs_compat --d1 DB=[db-id] --remote
Maybe I'm missing something but it seems tricky to clone the remote db back to my local dev environment.  Happy to be shown a better way!

This would be nice!
Here is my issue:
https://github.com/cloudflare/workers-sdk/issues/3505#issuecomment-1975219478

Closing as duplicate of https://github.com/cloudflare/workers-sdk/issues/4929


Update responses section with controllers metadata information

Update responses section to describe how to add OpenAPI response metadata for controller-based apps.

Internal previews

📄 File
🔗 Preview link

aspnetcore/fundamentals/openapi/aspnetcore-openapi.md
Generate OpenAPI documents

@Rick-Anderson @tdykstra @captainsafia I think this is ready for review / feedback.


Nested Formular Error with CalCellValue

Description
Cannot use nested function with calculate cell value. It produces incorrect result.
Try this function: =IF((ROUNDUP(IF(A1=16,(A2*2+4*0.3+1+1),IF(A1=4,(A2+2*0.3+1+1),(A3*SQRT(A1/2)+(SQRT(A1/2)*0.3)+1+1))),0))<=A4,(ROUNDUP(IF(A1=16,(A2*2+4*0.3+1+1),IF(A1=4,(A2+2*0.3+1+1),(A3*SQRT(A1/2)+(SQRT(A1/2)*0.3)+1+1))),0)),-1)
It works in excel but will not work with the plugin. It gives this error: IF accepts at most 3 arguments
Excelize version:
v2.5.0

Thanks for your feedback, I have fixed this issue, please try upgrade to the master branch code, and this patch will be released in the next version.


[Bug] Add transform to example notebook in context of Issue#283

Search before asking

[X] I searched the issues and found no similar issues.

Component
Transforms/Other
What happened + What you expected to happen
In the context of Issue: https://github.com/IBM/data-prep-kit/issues/283

Add a separate notebook to show case the functionality.
Add the transform to example notebook showing code data processing pipeline.

Reproduction script
Not Applicable as of now.
Anything else
Needed to showcase the functionality.
OS
Ubuntu
Python
3.10.x
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Done.


Empty  builder.Salary

// result
Hello, World!
{"Id":1,"Name":"John","Address":"123 Main St","Jajo":["test"],"Orders":[{"Product":"Shoes","Price":50},{"Product":"Shirt","Price":25}],"Ignored":0,"Salary":{"Amount":0,"Currency":""}}

Thanks for pointing out that, it was a failed experiment 😅 I will remove that and work on it in a separated branch

@mmisu thank you for pointing it out, it is now fixed. this is the new output

Hello, World!
{"Id":1,"Name":"John","Address":"123 Main St","Orders":[{"Product":"Shoes","Price":50},{"Product":"Shirt","Price":25}],"Ignored":0,"Salary":{"Amount":200,"Currency":"USD"}}

New builder from existing object
{"Id":1,"Name":"John","Address":"123 Main St","Orders":[{"Product":"Shoes","Price":50},{"Product":"Shirt","Price":25},{"Product":"Socks","Price":5}],"Ignored":0,"Salary":{"Amount":200,"Currency":"USD"}}

Thanks a lot.
On Thu, Feb 29, 2024, 15:10 Mohamad Dbouk @.***> wrote:

@mmisu https://github.com/mmisu thank you for pointing it out, it is
now fixed. this is the new output
Hello, World!
{"Id":1,"Name":"John","Address":"123 Main St","Orders":[{"Product":"Shoes","Price":50},{"Product":"Shirt","Price":25}],"Ignored":0,"Salary":{"Amount":200,"Currency":"USD"}}
New builder from existing object
{"Id":1,"Name":"John","Address":"123 Main St","Orders":[{"Product":"Shoes","Price":50},{"Product":"Shirt","Price":25},{"Product":"Socks","Price":5}],"Ignored":0,"Salary":{"Amount":200,"Currency":"USD"}}
—
Reply to this email directly, view it on GitHub
https://github.com/mhdbouk/AutoBuilder/issues/1#issuecomment-1971108186,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD4MTUD3VSCNRC5LTWGORDYV4UFTAVCNFSM6AAAAABD624XZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZRGEYDQMJYGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


SSL resources loading broken in eclipse

There is a couple of resources in the project classpath, mainly some ssl stuff under the sslSupport package. Those resources are loaded with the ResouceExtractor helper. As long as we are in the simple app that does not uses custom classloaders this works fine. However that does not work any longer in environments like Eclipse where we've got custom classloaders and deal with the custom URLs schemas like "bundleresource://". It would be nice if we allow users to resolve those URLs in the way they need.
In a short words: ssl does not work when bmp is kept in an eclipse plugin

@akosicki -- is this still an issue? The sslSupport files should be on the classpath at /sslSupport. If eclipse can't understand the maven src/main/resources project structure, you may need to add that directory to the Eclipse classpath manually.

@jekh, that's still an issue in the latest sources, just checked it. simple fix - https://github.com/akosicki/browsermob-proxy/commit/30c905b7e , It would be nice to have it in the main branch so that I could later use
ResourceExtractor.setURLResolver(new ResourceExtractor.URLResolver() {
    @Override
    public URL resolve(URL url) {
        if ("bundleresource".equalsIgnoreCase(url.getProtocol())) {
            try {
                // FileLocator is an Eclipse-specific thingy
                return FileLocator.resolve(url);
            } catch (IOException e) {
                return url;
            }
        } else {
            return url;
        }
    }
});
// ....
server = new ProxyServer(9090);
// ....

@akosicki - I just pushed a potential fix to my fork. It's available on the classpath-resources-fix branch, and here is the updated SeleniumProxyHandler.java file.
Let me know if that fixes your problem. It will also, hopefully, eliminate the need for standalone clients to have a separate sslSupport directory.

@jekh - ok, let me try it

I believe this is fixed, so I'm going to close the issue. Please reopen if you still experience problems with it.


xorg.xorgserver: apply CVE patches

<EMAIL_ADDRESS>rebuild count 913
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Nit: we have the fpgit function in there to reduce boilerplate, but apparently people don't use it.  (I don't mind either way, really.)


Team page w/ remove team dialog

This adds the team page
No styling for mobile yet
And the leave team dialog is kinda ugly since i need the iconfont and more styling
but i'll do that in the next pr

@keybase/react-hackers this is ready


Added functionality for renaming a GitHub repo.

As a very small HackDay (13 February 2015) project.
Tested using the Lita Vagrant VM and my own Github account using an application authentication token.
@theckman

Running tests locally caused the linters to fail:
Running RuboCop...
Inspecting 17 files
.......C.........

Offenses:

lib/lita/handlers/github_repo.rb:77:121: C: Line is too long. [142/120]
          'gh repo rename PagerDuty/lita-github better-lita-github' => 'Rename the PagerDuty/lita-github repo to PagerDuty/better-lita-github'
                                                                                ^^^^^^^^^^^^^^^^^^^^^^
lib/lita/handlers/github_repo.rb:335:43: C: Redundant curly braces around a hash parameter.
          octo.edit_repository(full_name, { :name => new_repo } )
                                          ^^^^^^^^^^^^^^^^^^^^^
lib/lita/handlers/github_repo.rb:335:45: C: Use the new Ruby 1.9 hash syntax.
          octo.edit_repository(full_name, { :name => new_repo } )
                                            ^^^^^^^^
lib/lita/handlers/github_repo.rb:335:64: C: Space inside parentheses detected.
          octo.edit_repository(full_name, { :name => new_repo } )

If you need any help/suggestions resolving these let me know.

To add, for some reason Travis isn't building your PR. Not sure why.

All the tests are passing now.

Can you also work on getting tests added to this for the functionality you added?

Pinging @theckman . :)


Possible for a labelset to have two of the same label

This leads to errors such as

MultipleObjectsReturned at /image/[image id]/annotation/save_ajax/
get() returned more than one LocalLabel -- it returned 2!

As far as I know so far, this doesn't seem to cause a chain reaction of bad data; for example, I think the duplicate gets ironed out when gathering annotations for classifiers. Still, it prevents the source owners from doing some important tasks, like using the annotation tool in this case.
When it happens, I think it's safe to delete either of the LocalLabels using manage.py shell to recover from the situation.
Ideas for fix / mitigation:

Add a database-level unique constraint saying that there can only be one LocalLabel with a particular labelset + global-label combo. It would prevent this specific situation and is incidentally a reasonable constraint to define.
Disable the form-submit button after submission is done, to prevent double submission. This addresses my best guess at the cause of this situation, and if the involved Javascript code is easily re-applicable to other pages, it could make a bunch of other data-integrity bugs much less likely to happen.

Going to just add the DB-level unique constraint for a start, and then that should help narrow down where the dupe attempt is coming from. The situation will also end up being a bit easier to debug on the user side (error should happen at labelset edit time, rather than annotation tool time).
Also for the record, this error was first seen in January 2023, but that was the only occurrence that year, whereas there were about 7 separate occurrences in 2024.


Layout of individual messages and dividers between them in a Timeline

In this conversation: https://loadaverage.org/conversation/7043295 we discussed, how to improve the layout of individual messages and dividers between them in a Timeline.
Looking at the latest repository build I see these points of improvement:

Text of a message should be visually closer to a Username above it. This may mean to figure out, how to fit "Favorited" star (or maybe change its shape?!)
Divider between messages is easily visible in a Conversation view, but almost invisible in a Timeline.
Some messages produce blank space below a text. Maybe we can trim it somehow...

(A bug with avatar placement is discussed in #278  )

@yvolk may I add a fourth point related to 1?

The sender text show have the same font size as the message text (right now the former is bold but smaller than the latter!). Rationale: bold text is used is to emphasize text, while reducing font size achieves the opposite. Doing the two things at a time is contradictory.

@aroquen Actually, we don't refer to exact font size for a username and a message body.
They are defined in https://github.com/andstatus/andstatus/blob/master/app/src/main/res/values/styles.xml as:
<item name="messageUsernameTextAppearance">?android:attr/textAppearanceSmall</item>
<item name="messageUsernameColor">?android:attr/textColorSecondary</item>

<item name="messageBodyTextAppearance">?android:attr/textAppearanceMedium</item>
<item name="messageBodyColor">?android:attr/textColorPrimaryNoDisable</item>

So do you think they both should have the same "text appearance" and color?

@aroquen Actually, styles for an Author's username and a message body are defined here (using above mentioned "text appearances":
<style name="messageUsernameAppearance" parent="android:Widget.TextView">
    <item name="android:textAppearance">?attr/messageUsernameTextAppearance</item>
    <item name="android:textStyle">bold</item>
    <item name="android:textColor">?attr/messageUsernameColor</item>
</style>
<style name="messageBodyAppearance" parent="android:Widget.Holo.TextView">
    <item name="android:textAppearance">?attr/messageBodyTextAppearance</item>
    <item name="android:textStyle">normal</item>
    <item name="android:textColor">?attr/messageBodyColor</item>
    <item name="android:textColorLink">?attr/textColorLink</item>
</style>

Regarding a "Favorited star".
Today I looked at the https://mobile.twitter.com and it came to me that the star can be moved from the right top to the right bottom of the message. Thus a Username will become close to a message text and adjacent messages will get some spacing between them.
?!

I think the author's style should be bold and the font size the same as for the message text. And I would avoid italics.
The star at the bottom is a good idea!

TBH, my ideal for this kind of programs is the aesthetic of Twidere.

@aroquen I agree on Italics. Let it be in a formatted text and not for the whole text box.
@moshpirit I don't think that mimicking some application's UI is a right way. But we can always look up good design elements. What exactly may be borrowed regarding this issue/topic?
On the other hand, following a style/design of an application, which has 1000 times more users will help to get new users of our application?!

Well, since Twidere is free software and is doing it similar to Twitter, I don't see any problem about it, but the main reason about why Andstatus should use a friendly design is because it's more practical and beautiful, not because of the number of the users, they'll come later because we can use GNU social and pump.io accounts.
Here you listen to us more than the main developer of Twidere. That's something I really appreciate, so the day that Andstatus will get a really beautiful design, I'll recommend it instead of Twidere as a Twitter app.

@moshpirit You touched an interesting topic: the goal of application's developers.
I personally think that number of current users  (not total since application creation) is a proper indicator of its current "quality". Meaning not visual attractiveness only  ("esthetic"...), but features, accessibility  etc.
This is why we always have to think about the best next step. E.g. which feature should we add first? Or should we better fix some old bug/limitation first and postpone implementation of new features... ?

Good point, but I think that these things come together and you can introduce slowly this visual change :-)

Done:
"Favorited star" moved to the bottom.
Username is bold.
No italics for a bottom line with additional info on a message.

Thanks. That looks very good https://gnusocial.de/attachment/2555532

@aroquen what appearance configuration do you have? My icons are gray, not white (even with blue colour)

@moshpirit ask @vinzv ;)

@moshpirit That's the default configuration coming with current git status. Maybe it depends on your Android version and local UI theme?

@moshpirit Icons for the Application bar ("Action bar") maybe need correction.  They were from KitKat icon pack, now we need the same for "Material design", I guess.
?!

As I found today, there are other ways to set that "listDivider", see http://stackoverflow.com/questions/31222125/android-custom-theme-divider-color-for-listview
<style name="MyAppTheme" parent="Some.Base.Theme">
    <item name="android:listDivider">@color/my_divider_color</item>
    <item name="android:dividerHeight">4dp</item>
</style>

and http://stackoverflow.com/questions/4573208/how-can-i-get-the-default-divider
<View
  android:layout_width="match_parent"
  android:layout_height="wrap_content"
  android:background="?android:attr/listDivider" />


SCHEMA_VERSION in upper case_Oracle db

Which version and edition of Flyway are you using?  4.0.3
Which database are you using (type & version)?  Oracle 12C
Which operating system are you using? Windows
What did you do?
We have changed schema_version to SCHEMA_VERSION to maintain Oracle standard. all the column names also in UPPER case.
and updated Bamboo task Goal to include upper case as below:
-Dflyway.table=SCHEMA_VERSION
What did you expect to see?
Bamboo job run successfully for new scripts updated to Bitbucket. But am getting below error message.
** What did you see instead?**
[ERROR] Failed to execute goal org.flywaydb:flyway-maven-plugin:4.0.3:repair (default-cli) on project qcsample: org.flywaydb.core.api.FlywayException: Unable to check the metadata table "xyz"."SCHEMA_VERSION" for failed migrations: ORA-00904: "success": invalid identifier
am not sure if am missing something. Currently we are testing in lower environment. any help is appreciated.

I'm able to modify. here are the steps:

In BitBucket V001__ modified to 'create table table1' --  table1 is already exist.
2.. In Bamboo--> Environment-->EditTask-->Maven 3.x configuration-->Goal:
updated/added like this
-Dflyway.table=SCHEMA_VERSION
So, now when I run Bamboo job, it will look for SCHEMA_VERSION table because it is not exist, Flyway creates one.
After creating a table SCHEMA_VERSION, it will start executing scripts from V001__
But because  table1 is already present, it will fail.
Now with admin rights to my DB, I have copied all the data from "schema_version" to SCHEMA_VERSION table.
you can also manually insert into this new SCHEMA_VERSION table using INSERT statement. but make sure in the INSERT statement, specify column names in lower case and within "".
Now Re-run the Bamboo job,

with this approach now whenever we Backup/restore, now Oracle will also include this table and also Oracle 12c uses Recyclebin for deletes.
and also every user who have access to regular table, can also see SCHEMA_VERSION table.
Our application (DEV, QA, Pre-Prod, Prod) are exist from last 2 years and am able to make this conversion successfully in all environments.


Enums MVP.

Supported cases:

non-repr-C enums without non-null optimization;
repr-C enums that are dataless / have the same layout for every case
enums with non-null optimization that don't use pointers (e.g. Option).

Future work directions:

Option<&_> and such - currently emits zombies/invalid SPIR-V, likely requires adaptations in mem2reg
repr(C) enums that can be represented as (discriminant, union) - some of the groundwork is already there

Would this mean that one can use things like Option<T> or alge raic enums, e.g.?
As long as type is not a pointer?
I didn't get to play around with rust-gpu that much yet, my understanding was that so far only data-less enums work (#78).

@joeftiger yes. With pointers, it can generate incorrect SPIR-V, because operations on pointers are heavily restricted and amending that would require basically a full-program analysis that I haven't come up with.

This has been open for nearly a year. Is it still ready and just waiting for a review?

i've roughly merged this into latest version here
i compiled this code
struct Nah {
    a: u32
}

enum Foo {
    A(Nah),
    B,
}

#[spirv(compute(threads(64)))]
pub fn main(
    #[spirv(global_invocation_id)] id: UVec3,
    #[spirv(storage_buffer, descriptor_set = 0, binding = 1)] output: &mut [u32],
) {
    let aa = Foo::A(Nah { a: 0xffffffff });

    if let Foo::A(a) = aa {
        output[id.x as usize] = a.a;
    } else {
        output[id.x as usize] = 99;
    }
}

it fails to compile
however if i revert providers.layout_of changes it works
need further research

@djdisodo do you mean the deoverlay_enum_fields change etc?
@Keavon there were some unresolved issues with this code, and ultimately, not much desire from Embark to do this. No-one wanted to do a massive code review, I guess.
@eddyb there seems to still be interest in this feature - I can probably bring it up to date, write some more tests, etc. Unfortunately I never did summon the courage required to make it work with pointers.

@ElectronicRU that would be awesome if you could return to this and get it landed now that the project seems to be picking back up on Embark's end. Our project https://github.com/GraphiteEditor/Graphite needs it for our node graph compositing shaders, which are written in Rust, to work with (some degree of) generic types in our node graph system.

This is fundamental Rust, we need some form of this feature; if not, this.

What is the status on this feature? I'm running into issues with Option that I feel are related to this, specifically with Option where T is a struct.

@Lucky4Luuk sorry - life & work take up a lot of time, I don't have any to work on this and won't for the foreseeable future :( Someone else would need to push it through for now, sorry.

Noticed rust-gpu project and got so excited today, but after few hours encountered unsupported Option<T>. Gave it a try to merge this PR in main, but a lot of things have changed and I don't have the know how :/
Would really appropriate if someone picked this up again :pray:

@reinismu could be easier to re-do at this point :) btw the repository has moved.


Design Challenge: Redesign the Sponsor Page

Currently, we simply list our sponsors in cards, without tagging or prioritizing or sorting by type. Here's a design challenge: design a new Sponsor page that makes it clear what it means to be a sponsor and sorts all our sponsors by their ranking: Platinum, Gold, Silver, and Software. We don't have to stick with cards, and we could simply display logos, with no text. What's the nicest way possible to do this?

Happy to team up with anyone on this, also. I'm thinking a quick design phase with review/approval, and then build the component

I would like to team up with this!! :)

@alexandriaroberts For sure! I'm going to work on an initial design/outline later this week or earlier next week, and I'll be in touch then so we can move forward and see how to break this task up!

That sounds great, I am looking forward to it!

@mmosholder @alexandriaroberts has there been any work done on this? I've never contributed before so not really sure how I can help but I'm offering my css skills if needed!

Nothing yet, Lynne, Burt I plan on starting a design soon and then breaking
up the task as bet I can. I’ll be in touch if I have something you can help
with!!
On Sat, Mar 9, 2019 at 6:49 AM Lynne Finnigan<EMAIL_ADDRESS>wrote:

@mmosholder https://github.com/mmosholder @alexandriaroberts
https://github.com/alexandriaroberts has there been any work done on
this? I've never contributed before so not really sure how I can help but
I'm offering my css skills if needed!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/VueVixens/website/issues/46#issuecomment-471178623,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABoNy42cfqCGN-05nh9Nf8ol8FF3zQRTks5vU7vYgaJpZM4bdKew
.

--
-Malinda

No worries! I had been messing around here, but if you're doing a design and everything for it I'm happy to help with any scss/styling!  Really want to contribute to the site, but I don't have the time for a few weeks and you guys are ready to go. Don't want to hold you back!

Hey Malinda, that's totally fine! Get it, you have responsibiliies :) I would love to get on with this, I can ask help in the forum and @lynnewritescode can also help me with it. What you think @lynnewritescode ? I can start thinking about the design and get back on our channel.

All set! Thank you everyone!


Fix tooltip blinking

Fixes https://github.com/JetBrains/compose-jb/issues/1497
Now instead of reacting to Enter/Exit, we check if the cursor is within parent component bounds

Is it fix for https://github.com/JetBrains/compose-jb/issues/1497 ?

Is it fix for JetBrains/compose-jb#1497 ?

yes


1.4.2 caused a system freeze

The new version caused a system freeze and force a reboot during setup of a game using wine
Log file attached
gameimage.log

Close this. Nothing to do with gameimage just happened whilst using it


consider (possibly optional) lexical translation of cuda to HIP

For example, sometimes people have functions that use the word cuda, such as initCuda(). Or even in comments etc...

Hi,
hipify translates only CUDA API functions. Such as cudaMalloc, cudaMemcpy etc., User specific function calls are not translated.

Actually the hipify tool performs a straight text transformation for a list of CUDA APIs, types, and enumerations - you can see the source in bin/hipify.  This would tranform commented out code or strings that match the transformation list but would not transform unlisted, general uses of the word "cuda" such as "initCuda".   We have seen this works quite well for many real application - but are are looking at developing a CLANG-based translation tool to further improve the robustness of the translation.

Closing this issue. If you have more questions feel free to reopen it.


Clicking the button to generate a new code still shows the old code

After the update, clicking the button to generate a new code shows the old code indefinitely.
Steps to reproduce:

Click the button to generate a code
Wait for the code to expire
Click the button again to generate a new code

Expected results: a new code is shown. (Was the case before update)
Actual result: the old code is shown.
The issue can be worked around by changing the orientation of the screen and clicking the button again.
EDIT: reformatted to read like a proper bug report.

I only have one HOTP token.

Confirmed the issue on HOTP. Will fix the issue

Thanks!

The issue should be fixed in this https://github.com/helloworld1/FreeOTPPlus/commit/3b40b9bff910a4b8b3e5ab6cc2d9b8a0149f0443
Are you willing to beta testing it?
You can download this debug version
https://drive.google.com/file/d/1nvVGTeArC_5FPXIL86yexzJIJxee3uFU/view?usp=sharing
It can co-exist with the release with and it has an orange icon.

Thanks! Sure, I'll test it, but I can't test it with the very code I'm having the issue with (I'll need to provision a new one).

Personally I don't have any HOTP to test. Would be glad to hear any feedbacks. I will add automated testing in the future.

I have tested the debug version from GDrive with a new HOTP token, and it works as expected. Thanks a lot!


Unable to register with master node

output when running roscore seems ok (see below), however when running eiither

rosrun jetbot_ros jetbot_motors.py
OR
rosrun jetbot_ros jetbot_oled.py
I am getting this print and nothing more..
Unable to register with master node [http://localhost:11311]: master may not be running yet. Will keep trying.

Any advice would be greatly appreciated.
(
btw, motors works fine when I run a simple python script like -
from adafruit_motorkit import MotorKit
kit = MotorKit()
kit.motor1.throttle = SOME_VALUE
)
this is the output when running roscore -
... logging to /home/jetbot/.ros/log/e60c8048-80dc-11ea-a8ce-72b5f773b75d/roslaunch-jetbot-10299.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://jetbot:35987/
ros_comm version 1.14.5
SUMMARY
PARAMETERS

/rosdistro: melodic
/rosversion: 1.14.5

NODES
auto-starting new master
process[master]: started with pid [10347]
ROS_MASTER_URI=http://jetbot:11311/
setting /run_id to e60c8048-80dc-11ea-a8ce-72b5f773b75d
process[rosout-1]: started with pid [10358]
started core service [/rosout]

all OK after restart. sorry and thanks for a great repo :)


Problem running tests  	126 - unit-GPUMatrix (Failed)

Hi there! I've just compiled shogun from source with only the python interface (and default c++) and I'm executing tests in order to see is everything is fine and I have one test that isn't working appropriately and I have no idea why...
I have found that some test failed because of missing python packages and I solved it just installing these packages but with this test (126, unit-GPUMatrix) the failure looks like:
https://gist.github.com/grg121/fedc687d8f39b2daf8502d8e5ba2d066
It seems that the matrix multiplication is giving always NaN as result... but I haven't changed anything in the code so it have to be something wrong in my installation or in the code itself at the repo (I doubt it)
Any idea? I'll inform if found what's happening.

@grg121 Have a look at the file GPUMatrix.h. You will find its definition in Shogun. This has nothing to do with the R matrix ;)
/** @brief Represents a column-major matrix on the GPU
 *
 * This class handles matrices on the GPU using [ViennaCL](http://viennacl.sourceforge.net/)
 * as backend for managing GPU memory.
 *
 * It supports conversion to/from SGMatrix objects and Eigen3 matrices. Native
 * ViennaCL methods can also be used on the data of the matrix through vcl_matrix()
 *
 * Supported scalar types: char, uint8_t, int16_t, uint16_t, int32_t,
 * uint32_t, int64_t, uint64_t, float32_t, float64_t.
 */
template <class T> class CGPUMatrix

Oh... I didn't check that.. You're right. Actually.. yesterday I was doing some test and I got this failure again... but I execute the test again and then it work, I didn't changed anything. So... I'm lost ahaha, I can't imagine why that happens.


feat: payouts

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Motivation and Context

How did you test it?

Checklist

[x] I ran npm run re:build
[x] I reviewed submitted code
[ ] I added unit tests for my changes where possible

When there is no payment ops present in dashboard for payouts


S2 [Task] Identify repo owner

Task
Identify repo owner

Task Title
Identify repo owner

User Story
#102

Epic

T-shirt size default is S(mall)
S

Story Points - Fibonacci (1,2,3,5)
1

Description
Identify owner(s) of the sawtooth-next-directory github repo

Business Need (the why):
who to ask to configuration changes

Dependencies
Sawtooth governance

Assumptions

Either a maintainer should be the owner or they should have access to the owner. #127 and PR #119

amundson is a repo owner.

Chris has reached out to the LF.


Clarify some statements in the owned entity types docs

Fixes #1239
Fixes #1400
Fixes #1457
Fixes #1628
Fixes #1629
Fixes #1781
Fixes #1888

Should we explicitly call out that owned types are not a good replacement for complex types and do not closely match the semantics for DDD-style value objects?

@ajcvickers I think we need to provide a better alternative first (multi-column value converters) for the warning to be effective.

@ajcvickers  And if you make this remark, then, please,explain, why it is not a good fit for DDD ;-)
I am also eagerly watinig for the feature to setup aggregate shape, so Includes are called automatically. That's actually the main reason why I use owned types.


codeql-analysis.yml

Codecov Report

Merging #35 (3eac41d) into main (f3ef943) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #35   +/-   ##
=======================================
  Coverage   99.67%   99.67%
=======================================
  Files          19       19
  Lines         616      616
=======================================
  Hits          614      614
  Misses          2        2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f3ef943...3eac41d. Read the comment docs.


How can data around Cognito be persisted when using docker?

Moto always helps me.
However, when I stop Docker, the data is lost.
Is there a way to make it persistent?
If there is, it would be helpful if it was written in the documentation.
I especially use services related to cognito.
  mock-aws-local:
    image: motoserver/moto:latest
    environment:
      MOTO_PORT: 4000
    ports:
      - ${AWS_LOCAL_PORT:-4000}:4000

@bblommers
sorry too late.
I was do that
before create user-pool,
curl $ENDPOINT_URL/moto-api/seed?a=42

Sorry for the delay in contacting you, but it was very helpful.


Wait for document ready before calling LayoutEditor constructor

Hi @connorsmallman, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

That created a new issue on 1.9.x preventing any LayoutPart to be saved.
window.layoutEditor = new LayoutEditor.Editor(editorConfig, editorCanvasData);

from LayoutEditor.cshtml is executed after
var host = new LayoutDesignerHost($(".layout-designer"));

from LayoutDesignerHost.js.
So, window.layoutEditor is not defined when initializing LayoutDesignerHost. This throws an exception at save time in serializeCanvas function because self.editor is undefined.
PR should be reverted or fixed.

@sfmskywalker Could you revert this change?

I just pushed a fix. Please try it out and let me know if you're seeing any other issues regarding this.

@sfmskywalker  It seems to work fine now. Thanks
I saw another issue, but only with Edge and not bound to this PR because it appears before : I can only edit one element's content. After I saved an element, it throws TypeError: Permission denied when you try to edit another or same element's content.
I have to save the whole content, so it reloads the editor, in order to edit another element, and so on...
Maybe it's more an Edge's issue than a Layout editor issue. Let me know if you want me to open an issue for that.


Roy And Symmetric Logos

Aim
Want to add a solution of "Roy And Symmetric Logos"
Kindly assign me this problem. I would like to add my solution to this problem in C++ easily and efficiently using 2-D matrix.
Link to the problem: https://www.hackerearth.com/practice/data-structures/arrays/multi-dimensional/practice-problems/algorithm/roy-and-symmetric-logos-1/
Details
Roy likes Symmetric Logos.
How to check whether a logo is symmetric?
Align the center of logo with the origin of Cartesian plane. Now if the colored pixels of the logo are symmetric about both X-axis and Y-axis, then the logo is symmetric.
You are given a binary matrix of size N x N which represents the pixels of a logo.
1 indicates that the pixel is colored and 0 indicates no color.
For instance: Take a 5x5 matrix as follows:
01110
01010
10001
01010
01110
This is Symmetric
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

Please assign me this issue under LGM-SOC'21 @ravikr126


NOTE:
I've already googled (3 days) and can't find info about a few features.

I don't understand how it works? Maybe it works with some kind of extension?
If you can please provide 🎬 screencast or 🖼 screenshot.

ℹ Features for which clarification is needed:
📑 Base colors:

descriptionForeground

📑 Text Colors:

textBlockQuote.border
textCodeBlock.background
textPreformat.foreground

📑 Input control:

inputValidation.errorBackground
inputValidation.errorForeground
inputValidation.infoBackground
inputValidation.infoForeground
inputValidation.infoBorder
inputValidation.warningBackground
inputValidation.warningForeground
inputValidation.warningBorder

📑 Lists and trees:

list.inactiveFocusBackground

📑 Activity Bar:

sideBar.dropBackground

📑 MiniMap:

minimapGutter.addedBackground
minimapGutter.modifiedBackground
minimapGutter.deletedBackground

📑 Editor Groups & Tabs:

tab.activeModifiedBorder
tab.inactiveModifiedBorder
tab.unfocusedActiveModifiedBorder
tab.unfocusedInactiveModifiedBorder
editorPane.background

📑 Editor colors:

editorCursor.background
editor.findRangeHighlightBackground
editor.findRangeHighlightBorder
searchEditor.findMatchBackground
searchEditor.findMatchBorder
editor.symbolHighlightBackground
editor.symbolHighlightBorder

📑 Overview ruler:

editorOverviewRuler.rangeHighlightForeground
editorOverviewRuler.selectionHighlightForeground
editorOverviewRuler.wordHighlightForeground
editorOverviewRuler.wordHighlightStrongForeground
editorOverviewRuler.modifiedForeground
editorOverviewRuler.addedForeground
editorOverviewRuler.deletedForeground
editorOverviewRuler.errorForeground
editorOverviewRuler.warningForeground
editorOverviewRuler.infoForeground
editorOverviewRuler.bracketMatchForeground

📑 Errors and warnings:

editorWarning.foreground
editorWarning.border
editorHint.foreground
editorHint.border
problemsWarningIcon.foreground

📑 The gutter contains the glyph margins and the line numbers:
editorGutter.commentRangeForeground
📑 Editor widget colors:

editorMarkerNavigation.background
editorMarkerNavigationError.background
editorMarkerNavigationWarning.background
editorMarkerNavigationInfo.background

📑 Panel colors:

panel.dropBackground
panelInput.border

📑 Status Bar colors:

statusBar.noFolderBackground
statusBar.noFolderBorder

googled it would be something like this:

...but unfortunately, I haven't ☹
📑 Notification colors:

notificationLink.foreground

📑 Debug:

editor.stackFrameHighlightBackground
editor.focusedStackFrameHighlightBackground

I think it's about - Debug > CALL STACK
...but don't know the idea where are these features disappear? 😯
📑 Welcome page:

walkThrough.embeddedEditorBackground

📑 Settings Editor colors:

settings.dropdownListBorder

📑 Snippets:

editor.snippetFinalTabstopHighlightBackground
editor.snippetFinalTabstopHighlightBorder

ℹ System:
Microsoft Windows 10 Enterprise 2016 LTSB, 64x
Version: 10.0.14393.2273 (Win10 RS1)
«VS Code» is last updated.

Best regards❗ ✌

Sorry, what's the issue? Are you having trouble customizing a VS Code theme, or are you looking to request a dracula theme for it?
For the former, you're at the wrong place (try https://github.com/microsoft/vscode).
For the latter, https://draculatheme.com/visual-studio-code/

@benknoble
No bro, I just can figure what do these features do. For example, we have:
📑 Base colors:

descriptionForeground: Foreground color for description text providing additional information, for example for a label.

Yes, I read docs a few times but it's not a pill. I need more understandable info, 🎬 screencast or 🖼 screenshot It will be great.
P.S. ··· and yes I know it's not your job and you don't need to go on official docs site and correct something.
I asked maybe, I repeat "MAYBE" you have some Infos, cuz you work with Theme Plugin and you have experience on shoulders. Cheers!

@zenorocha I'm going to close this as it seems off-topic. I don't mind a discussion about the OP's questions happening, I just don't think it needs to clutter dracula's issue space.


Finding outliers

I would greatly appreciate your assistance in gaining a better understanding of the code. Specifically, I would like to inquire about the MatMul8bitLt function, wherein a line located under the Quantize B section searches for outliers (outliers = F.extract_outliers(state.CxB, state.SB, state.idx.int())). Based on my understanding, it appears that outliers are being looked for on the weights,  as far as I understand it should be on the input. I would be grateful for any insight you may have on this aspect of the code, as well as any clarification you can provide on the meaning and purpose of CB, CxB, SB, and other relevant variables.
Thank you for your time and assistance.

Hi @barasamit  I also have the same questions when looking at the code. Can you share the answer if you find it ?

Thanks @barasamit
My first question is also the meaning and purpose of CB, CxB and SB ?
Second question is in the state.CxB case, we rely on CxB and SB to find the outliers, instead of the outlier information from matrix A. What is the purpose here?
            if state.CxB is not None:
                outliers = F.extract_outliers(state.CxB, state.SB, state.idx.int())
            else:
                outliers = state.CB[:, state.idx.long()].clone()


Problem with delays

Hello and sorry for my bad english, i think there is an issue with delays in quest objectives:
(Required) What is your Quests version / build number (do not say "latest")?
256 (254 and 255 tried before)
(Required) Please describe the problem and how to replicate it. Any console errors?
When i create an objective with a delay, the next stage of the quest does not start fully after the defined delay, it's shows the header "--{Quests}--" with "start-message" but no objectives , and the quest stay freeze on the stage with no objectives.
(Optional) Can you provide an example quest from quests.yml using Pastebin.com?
https://pastebin.com/fmtMkB7g (sorry for the french)
in this example , (delay is in the stage 2) the objective to talk to the npc n°20 is freezing on "start-message" of stage 3 and the objective "talk to npc" don't appears. It's just launch the message: "message de debut" and If i look on quest journal , it says the name of the quest with no objectives
have I misunderstood the functioning of delays Or is it a bug ?

Once all objectives have been completed, the Delay is how long the plugin will wait until telling the player the quest is complete and dishing out rewards.
As a side note, I noticed the Delay expects milliseconds (even though it asks for seconds). I will keep this ticket open until I have time to investigate that.


Added can-utils for wily and xenial.

It is missing is precise.  Not sure if it that matters any more.

No non-EOL ROS distro supports "precise" anymore. Therefore I wouldn't spend effort on maintaining this entry but collapse them.

Sounds good, thanks.

Are packages in testing available by default in Debian? Jessie was the only one with can-utils in stable.

Yes, Stretch itself is "testing" at the moment. Jessie is the "stable" release. Eventually Stretch will transition from "testing" to "stable" and jessie will be eol'd.

Perfect, thanks!


Publish artefacts to Maven central.

Now that release 8.4.1 is finished we need to publish the artefacts to a central repository. If anyone knows how to do this, please let me know.

http://maven.apache.org/guides/mini/guide-central-repository-upload.html has some information.

Sonatype has a simple workflow for publishing artefacts to maven central: http://central.sonatype.org/pages/ossrh-guide.html.
It is really easy. Here is what I do, when I publish a new release of PojoBuilder.

Done, CalendarFX is now on jcenter and maven central.


Setup with JUnit5 RuntimeException: not found

Hi there
I have issues setting up a initial test with JUnit 5. I hope you could help me here, on Stackoverflow they told me to open up an issue here. I hope you can help me out on this one:
Having the following directory structure: src/test/java containing a karate-config.js and the package utils/ with a basic-auth.js.
karate-config.js:
`function fn() {
var env = karate.env; // get java system property 'karate.env'
karate.log('karate.env system property was:', env);
if (!env) {
env = 'local'; // a custom 'intelligent' default
}
var config = { // base config JSON
urlBase: 'http://localhost:8080/',
};
// don't waste time waiting for a connection or if servers don't respond within 5 seconds
karate.configure('connectTimeout', 5000);
karate.configure('readTimeout', 5000);
return config;

}`
basic-auth.js:
function fn(creds) {
    var temp = creds.username + ':' + creds.password;
    var Base64 = Java.type('java.util.Base64');
    var encoded = Base64.getEncoder().encodeToString(temp.getBytes());
    return 'Basic ' + encoded;
}

There is another package api.sample containing my karate-test:
sample.feature:
Feature: Sample Test

  Background:
    * url baseUrl

  Scenario: get all
    Given path "/api/sample"
    * header Authorization = call read('utils/basic-auth.js') { username: 'admin', password: 'admin' }
    When method get
    Then status 200

as well as my JUnit5-Runner:
`package api.sample;
import com.intuit.karate.junit5.Karate;
public class SampleRunner {
@Karate.Test
Karate testSample(){
    return Karate.run("sample.feature").relativeTo(getClass());
}

}`
When I try to run the SampleRunner, I'm getting a java.lang.RuntimeException: not found: api/sample/sample.feature
Somehow it can't find the sample.feature - and I really don't know why. Structure is set up according to your documentation...
The pom.xml has only this dependency:
<dependency>             <groupId>com.intuit.karate</groupId>             <artifactId>karate-junit5</artifactId>             <version>1.0.0</version>             <scope>test</scope>         </dependency>
Any input is appreciated!

Using IntelliJ with AdoptOpenJDK-15 btw.

@remo-vonarx sorry, on stack overflow the instructions were clearly to follow this process, which you haven't: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue

I commented in stackoverflow as well so folks land there from Google but seems like you did not set up the testResources in maven. By default maven only copies the *.java files to the target directory where it actually runs your tests so you explicitly must tell maven to also copy the other files. See: https://github.com/intuit/karate/tree/master#folder-structure


Search bar text not updating properly

There is an issue with the text in a SearchBar component when doing a remote search.
If you type a string too quickly, the text in the search bar won't update properly and will delete some of the characters you type. You can also see the issue when trying to delete, as sometimes the characters you have deleted will come back.
You can reproduce this issue with the search here: https://react-bootstrap-table.github.io/react-bootstrap-table2/storybook/index.html?selectedKind=Remote&selectedStory=Remote Search&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel
Type any string quickly to see the issue. It doesn't happen as often when typing a string, but it is more obvious when deleting the string.

@enderjbr I think that is because I didn't put a mask on search bar, so will cause the rendering replace your input. So far, we only support the mask or a loader on Table itself, for example: this. i will think about to implement a mechanism to mask the search when remote search enable, thanks your advice

We are also having this problem and if it doesn't get changed soon, we will have to create our own searchbox Container.
Is there a plan to implement this enhancement in the future?

Having the same issue, is it going to be fixed? Does anyone managed to fix solution for that, or should I implement my own solution for that issue?

Having the same issue, is it going to be fixed? Does anyone managed to find solution for that, or should I implement my own solution for that issue?

Can someone give me an example of adding a mask to searchbar, please? I am having the same problem now. but looks like  we did not have a solution so far

@enderjbr I think that is because I didn't put a mask on search bar, so will cause the rendering replace your input. So far, we only support the mask or a loader on Table itself, for example: this. i will think about to implement a mechanism to mask the search when remote search enable, thanks your advice

@AllenFang do you have any plans for this?

There is an issue with the text in a SearchBar component when doing a remote search. If you type a string too quickly, the text in the search bar won't update properly and will delete some of the characters you type. You can also see the issue when trying to delete, as sometimes the characters you have deleted will come back. You can reproduce this issue with the search here: https://react-bootstrap-table.github.io/react-bootstrap-table2/storybook/index.html?selectedKind=Remote&selectedStory=Remote Search&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel
Type any string quickly to see the issue. It doesn't happen as often when typing a string, but it is more obvious when deleting the string.

@enderjbr did you manage the problem?


Add card components

Describe the Feature you want to end'
I like to add some responsive card components made by using html and css

Thanks for letting me make changes to the project

I like to add some responsive card components made by using html and css

I like to add some responsive card components made by using html a


Add support for Scala 3.3

Pekko and Pekko Http latest snapshots have just been released with Scala 3.3 support. This PR updates pekko-http-cors so that it properly releases Scala 3 artifacts instead of using CrossVersion.for3Use2_13 (which actually should not be used for libraries, for applications its fine).
You may have noticed the addition of the inline settings as well as ch.megard.pekko.http.cors.OptionConverters, this is due to the fact that the latest version of Pekko has dropped java8-scala-compat for Scala 2.13+ (its still needed for 2.12) and so this technique is used to cross compile ObjectConverters for all versions of Scala that this project supports.
An alternative to this inlining solution would have been just to add java8-scala-compat as a dependency. The problem here is that it since pekko-grpc relies on this library, adding java8-scala-compat as a dependency would have made the endeavour somewhat pointless as Pekko module aside from pekko core/pekko-http would have had this dependency transitively introduced.
@lomigmegard Can you let me know when you release a new artifact. Thanks!

Perfect, thanks!