Repository navigation
fix(ci): recover signed Ubuntu dependencies during DNS outages - #935
Merged
Merged
Conversation
This was referenced Nov 11, 2026
Mjones13
added a commit
that referenced
this pull request
Nov 12, 2026
Brings in #913 (orphaned run records), #917 (held queue expiry and the sparse Jones jones_queue_holds table at migration 147), #930 (install status reconcile), #931 (question line breaks) and #935 (signed Ubuntu APT retrieval during transport failures). #917 landed first and keeps Jones migration 147 (QueueHolds). The sync's unreleased Jones migrations move up by one, above the highest main ID: NativeExecutionProcessCustody 148, OrdinaryCheckoutProcessCustody 149, AuthSessionClientMetadata 150, WorkspaceRuntimeUses 151 and PeerLinksAdoption 152. These IDs were only ever on the unmerged sync branches (#850 and this successor), never on main. Their module files, ledger tests and the WorkspaceRuntimeUses basis literal in RuntimeUseInstallation follow the new IDs; no shipped schema or row changes. server.ts keeps the sync's managed-policy imports and adds main's HeldQueueExpiry (WorkMode and Scheduler were already imported). The boundary JSON is a structural three-way merge; the install-status lint and fmt commands keep the sync's sidebar path and gain main's finishPlan files. The server compile-cache anchor is re-pinned for server.ts. 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.
Ubuntu DNS failures make the three native dependency steps spend minutes retrying the built-in Ubuntu mirrors, then fail before tests run. This gives those steps one strict, bounded refresh/download owner and an isolated independent mirror fallback for recognized transport failures. Package sets, recommends behavior, Ubuntu suites/components/keyring, job deadlines, test commands, selection and Check stay intact.
The candidate uses fresh lists and archives, validates the supported runner source layout and index targets, requires signed retrieval and current updates/security metadata, then installs offline. Owned process groups must be quiescent before fallback or workspace removal. A dispatch input can force the candidate on the final head for runner qualification.
Validation: final PR head a1c5ad9 passed CI run 43061095779, including Lint/strict boundary, Build, Test, Test Desktop, and Check. All three dependency steps exercised the fallback after a safely terminated normal-route deadline, retrieved all four signed suites and packages from the isolated candidate, accepted current updates/security dates, and installed offline. The real Linux TERM/leader-exit/KILL regression passed. CI tested merge commit 6f07528 against main ad37e66; its tree matches the final PR head. Focused local union:39 passed/1 explicit Linux-only skip; independent correctness review found no issues. The healthy normal route remains covered by injected tests, with no live provider-recovery claim.
Refs #932. Failed PR reruns retain their old workflow; those PRs need fresh heads including this repair after it lands.
Contributor: Jones Code thread c961c662-3164-44fa-83d8-963dbcaed3a1 (Codex root, coordination/Git owner); delegated builder and read-only investigation/review tasks are recorded in that thread.