Repository navigation
fix(ci): make the first ARC voice+inbox run reach its checks - #61
Merged
nullStack65 merged 2 commits intoNov 17, 2026
Merged
Conversation
The first real ARC run of the voice + founder inbox workflow (fork run 44168925335, job 134342439700) checked out 623dea7 successfully, then failed in actions/checkout's credential removal: with persist-credentials false it runs `git submodule foreach --recursive`, which exits 128 on the two vendored gitlinks under .repos/alchemy-effect/submodules that have no .gitmodules entry ("No url found for submodule path ... distilled"). Add a root .gitmodules naming their real upstream sources with update=none and ignore=all. Nothing is fetched or initialized, .repos/ stays untouched (it is a vendored read-only reference), and persist-credentials stays false so no job token is left for dependency install scripts on the ARC LAN. Upstream CI avoids the failure only because it keeps the default persisted credentials. Source, voice and inbox code are unchanged. Task: CLO-866 Model: claude-opus-5-5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With checkout fixed, PR61's ARC run 44171253656 (job 134350632468, runner t3code-ci-arc-w7cd8-runner-z27ph) failed in setup-vp: Vite+ 1.4.0 self-setup prepared Node 26.12.1, then "Failed to install production dependencies (exit code: 127)" on all four attempts. Official Node 26 linux-x64 binaries link libatomic.so.1 (verified with readelf/ldd), and the pinned actions-runner 2.338.2 image (dotnet runtime-deps:8.0-noble plus sudo, lsb-release, gpg-agent, software-properties-common, curl, jq, unzip, git) does not ship it, so the loader exits 127. The ARC pod blocks privilege escalation, so sudo/apt is not available and must not be. Before setup-vp, fetch Ubuntu noble's release-pocket libatomic1 14-20240412-0ubuntu1 (immutable pool path; Release signature, Packages.gz hash and this SHA-256 verified on 2026-11-17), check the pinned SHA-256, extract only the shared library into RUNNER_TEMP and add it to LD_LIBRARY_PATH. The step is a no-op when the image already provides it, so it stays correct if the runner image later adds libatomic1. T3's own release archives bundle libatomic for the same reason. Task: CLO-866 Model: claude-opus-5-5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 first real ARC run of T3 fork ARC CI (run 44168925335, job 134342439700 on
t3code-ci-arc-w7cd8-runner-ckf4w) checked out623dea7(8,044 files), then failed in actions/checkout's credential removal:With
persist-credentials: false, checkout runs that cleanup inside the main step, and git exits 128 on the two vendored gitlinks under.repos/alchemy-effect/submodules/(distilled,floci), which have no.gitmodulesentry. Upstream has the same gitlinks but keeps the default persisted credentials, so its cleanup only runs in the non-fatal post step. actions/checkout v6.1.0 runs the samesubmoduleForeach, so upgrading it would not help.Change
.gitmodulesnaming the two gitlinks' real upstream sources (taken from alchemy-effect's own.gitmodules), withupdate = noneandignore = all..repos/(vendored, read-only per AGENTS.md) is untouched, andpersist-credentials: falsestays, so no job token is exposed to dependency install scripts on the ARC network.Verification
git submodule foreach --recursive true→ rc 128.git submodule statusshows both uninitialized, and the worktree is clean.Second fix: provide libatomic for Node on the stock runner image (commit
d6e5e601)Once checkout passed, the PR's ARC run (44171253656, job 134350632468 on
t3code-ci-arc-w7cd8-runner-z27ph) failed in Set up pinned Node, pnpm and Vite+. Vite+ 1.4.0 prepared Node 26.12.1, then hitFailed to install production dependencies (exit code: 127)on all four attempts.libatomic.so.1(checked withreadelf/ldd). The pinnedactions-runner2.338.2 image isdotnet/runtime-deps:8.0-nobleplussudo lsb-release gpg-agent software-properties-common curl jq unzip git, and none of those provideslibatomic1, so the dynamic loader exits 127.sudo aptisn't available, and that safeguard stays.libatomic114-20240412-0ubuntu1(an immutable pool path).f496d806….RUNNER_TEMPand add it toLD_LIBRARY_PATH.Releasesignature good (archive key 2018) →Packages.gzhash listed in it →.debSHA-256 matches. Running the step's own script withRUNNER_TEMP/GITHUB_ENVset, Node 26.12.1 resolveslibatomic.so.1from the extracted directory and runs.Not addressed here: checkout took about 9.5 minutes because sparse checkout with
filter=blob:nonefetches each file's contents lazily. That's slow but not failing; the job timeout is 90 minutes.Task: CLO-866
🤖 Generated with Claude Code