Repository navigation
fix(antigravity): install from the release manifest instead of upstream's install.sh - #28
Merged
Merged
Conversation
…am's install.sh arm64 image builds under QEMU fail at this feature: bash rejects the downloaded install.sh with "cannot execute binary file" (exit 126), while the amd64 leg of the same build installs fine. Any change that busts the layer cache, such as the playwright-cli bump in orianna-ai/devcontainer#101, hits it. Read manifests/linux_<arch>.json directly, download the archive it names, verify its sha512, and extract the binary into the shared prefix. This skips the step that fails, and it also removes the HOME staging and the `agy install` profile edits that the feature previously had to contain. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mf8JGK7iWHT9PnV8oXoiEY
|
Automatic reviews are disabled for this repository. |
ashwin153
enabled auto-merge (squash)
October 8, 2026 14:16
ashwin153
disabled auto-merge
October 8, 2026 14:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The arm64 leg of the devcontainer image build fails at this feature. Bash refuses the
install.shit just downloaded withcannot execute binary file(exit 126). The amd64 leg of the same build installs 1.3.1 without trouble. The failure happened in both attempts of orianna-ai/devcontainer#101, the playwright-cli 0.1.22 bump. That PR invalidates the layer cache, so this feature has to run again. Onmainthe layer is still cached from the Oct 4 build, which is whymainis green.I couldn't reproduce the bad download outside CI. Under both qemu 8.2 and CI's qemu 10.2.3, the arm64 image's own curl and bash fetched and ran the script correctly. So this PR goes around the step that fails instead of trying to patch it.
What
install.shnow does the work upstream's script did, minus the parts this feature had to undo:uname -mtoamd64orarm64.manifests/linux_<arch>.jsonfrom the same release server upstream's script uses.antigravityto/usr/local/share/antigravity/bin/agyand symlink it from/usr/local/bin/agy. The file is root-owned and not writable by other users, same as before.No HOME staging and no
agy installprofile edits. The install location, the permissions and every test check are unchanged. Comments in the docs and tests are updated, and the feature version goes to1.0.1so:1picks it up.Testing
pre-commit(shellcheck, shfmt, json) passes.agy --versionreports1.3.1.uname -mshimmed toaarch64: selectslinux_arm64, the checksum verifies, and it installs an aarch64 binary owned by root with mode 755. That binary runs under qemu-aarch64 and reports1.3.1.devcontainer features testruns the existing scenario on amd64.Once this is published, re-running CI on orianna-ai/devcontainer#101 should get it past this step.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Mf8JGK7iWHT9PnV8oXoiEY
Generated by Claude Code