I've set up my project and have been running with run-bundled-codegen.sh for a month or so now with no problem. Today I started getting failures in CI and locally when I re-clone my repo using the 0.24.0 version of the client up to the next major version:
Checking if CLI needs to be downloaded...
Downloading zip file with the CLI...
Incorrect version of the CLI tarball is downloaded locally, redownloading the zip from the server.
Downloading zip file with the CLI...
Error: The SHASUM of this zip file does not match the official released version from Apollo! This may present security issues. Terminating code generation.
Command PhaseScriptExecution failed with a nonzero exit code
I was wondering if the checksum is out of date or something on your end?
Same error
I believe the recent change of migrating the build images broke the command line tools.
Here is the content of the apollo.tar.gz file the commandline tool downloads during the 'run-bundled-codegen.sh' script :
Redirecting to <https://circle-production-customer-artifacts.s3.amazonaws.com/picard/5aefb6e902a29900129bef67/5dadba7f55793353d367a38f-0-build/artifacts/oclif-pack/apollo-v2.21.0/apollo-v2.21.0-darwin-x64.tar.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20200430T180940Z&X-Amz-SignedHeaders=host&X-Amz-Expires=60&X-Amz-Credential=AKIAJR3Q6CR467H7Z55A%2F20200430%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=d2f3b0b0b717f73761252232023d0854f0ffea06fb328b64b2f385f5e5278dcb>
If you want to fix the issue, you can update manually the file run-bundled-codegen.sh
and change this :
curl --silent "${ZIP_FILE_DOWNLOAD_URL}" -o "${ZIP_FILE}"
by
curl --silent -L "${ZIP_FILE_DOWNLOAD_URL}" -o "${ZIP_FILE}"
@Valpertui i am also facing similar issue. How can i update file
run-bundled-codegen.sh
manually ?
We just discovered that we were not updating to the latest version 0.27 and were stuck at 0.23. Seems to be updating correctly now.
Having the same issue. Is updating to the latest version the suggested solution, or is this going to be fixed in a different way?
For versions older than 0.26.0, the download URLs may stop working soon because of changes to Circle's retention policy (or more honestly, enforcement of existing policy) that mean build artifacts will be deleted after 30 days. It sounds like this has already started for some older versions.
Versions newer than 0.26.0 use our new CDN and will not be affected by this, so upgrading will definitely fix this. Versions older than 0.18.0 do not use this download mechanism and will also not be affected by this.
For versions between 0.18.0 and 0.26.0, you can manually change the download link by taking the old download link, which should look like this:
https://46555-65563448-gh.circle-artifacts.com/0/oclif-pack/apollo-v2.26.0/apollo-v2.26.0-darwin-x64.tar.gz
grabbing the version out of that, and updating the download link to:
https://install.apollographql.com/legacy-cli/darwin/2.26.0
For those on versions between 0.18.0 and 0.26.0, quick poll on how to handle this. Vote by Reaction Emoji! Should I:
OK, that's all of 'em - gonna go back and slap past me for not twisting more arms to move off of Circle earlier. 馃槅
Most helpful comment
For versions older than
0.26.0, the download URLs may stop working soon because of changes to Circle's retention policy (or more honestly, enforcement of existing policy) that mean build artifacts will be deleted after 30 days. It sounds like this has already started for some older versions.Versions newer than
0.26.0use our new CDN and will not be affected by this, so upgrading will definitely fix this. Versions older than0.18.0do not use this download mechanism and will also not be affected by this.For versions between
0.18.0and0.26.0, you can manually change the download link by taking the old download link, which should look like this:grabbing the version out of that, and updating the download link to:
For those on versions between
0.18.0and0.26.0, quick poll on how to handle this. Vote by Reaction Emoji! Should I: