Verified
Status Update
No update yet.
Comments
fr...@google.com
Hello,
Thanks for bringing this to our notice! A feature request for the same has been forwarded to the App Engine Product Engineering Team so that they may evaluate it. However, please note that there is no ETA or guarantee of implementation for this. Rest assured, we’ll keep you updated on every update we receive from the team. All communication regarding this feature request is to be done here.
fr...@google.com
Hey there, I noticed that Go 1.20 runtime is suffering the same fate here. I'd be happy to submit a patch to remove ffmpeg from the documented system packages if this is not a priority to fix :)
wi...@federated.directory
I can confirm, it works again 🎉🎉
fr...@google.com
Awesome!!! Thank you for the confirmation and for reaching out to Google Cloud Platform Support, hope you guys have a great week!
kind regards,
Froián.
kind regards,
Froián.
Description
We are using zero-install approach of yarn 2 (https://yarnpkg.com/features/zero-installs ).
In our setup, yarn executable is also bundled into the repository and https://classic.yarnpkg.com/en/docs/yarnrc#yarn-path- ). This helps us to achieve that everyone is running the correct version of yarn 2 even when they have yarn 1 globally installed.
.yarnrccontains the path to the executable of yarn 2, like thisyarn-path ".yarn/releases/yarn-2.4.0.cjs"(seeDue, to the runtime magic, which is described herehttps://cloud.google.com/appengine/docs/standard/nodejs/runtime , whereby nodejs runtime first runs
yarn install ...we are having issues now when moving to a new version of nodejs runtime.Looks like, nodejs runtime v16 is running
yarn install --production=false, but this flag--productionis not implemented anymore inside yarn 2.This is a regression, since on nodejs12 everything was working fine, but now we get an error: