You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was found in the logs, with a whole bunch of failures later:
No locally built Ark found in /home/runner/work/positron/ark; checking downloaded version.
package.json version: 0.1.170
Downloaded ark version: Not found
Using Github PAT from environment variable POSITRON_GITHUB_PAT.
Downloading Ark 0.1.170 from https://api.github.com/repos/posit-dev/ark/releases/assets/233347570...
Successfully downloaded Ark 0.1.170 (0 bytes).
Successfully unzipped Ark 0.1.170.
If no data is received, we should not treat the binary download as successful, even if the download reports a successful HTTP status and unzip doesn't complain.
The text was updated successfully, but these errors were encountered:
This change addresses an issue observed in builds in which problems
downloading our binary dependencies do not necessarily cause the build
to fail. Instead, the build "succeeds" but the product is broken because
the dependencies are missing.
The fix is to add more error handling to the download scripts:
- make sure we got a 200 status code on our final request for the binary
data (after following 302 redirects)
- make sure we got a reasonable-looking amount of data for the asset
Addresses #6672
This was found in the logs, with a whole bunch of failures later:
If no data is received, we should not treat the binary download as successful, even if the download reports a successful HTTP status and unzip doesn't complain.
The text was updated successfully, but these errors were encountered: