Conversation
The v2 manifest pinned b0ad1457, which no longer exists on saphid/t3code after its PR branch was rewritten, so every v2 run failed in resolve with a 422. The fix merged upstream as pingdotgg#13201 (6134998) and is already in t3code/codex-turn-mapping, so the pin is redundant. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
This was referenced Sep 29, 2026
Owner
Author
|
Superseded by #100, which refreshes the whole v2 stack and no longer includes the dead pin. |
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
1 participant
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.
Every Fork Nightly Orchestrator v2 run since 23 Sep has failed in
resolvewith422 No commit found for SHA: b0ad1457…. That manifest entry pinned a commit from the PR branch for pingdotgg#13201, and the branch was rewritten after the pin, so the commit no longer exists on GitHub.The fix merged upstream as
6134998b("test(server): stop ACP soft-steer tests racing the prompt settle (pingdotgg#13201)"), which is already an ancestor oft3code/codex-turn-mapping(currentlycb64162d). This PR drops the dead entry instead of re-pinning it.After this merges, v2 gets past
resolve, but its stack still conflicts with the current upstream branch.75be8c11(custom updater on V2 profiles) conflicts inapps/desktop/src/updates/updatesTestHarness.ts, and several later pins need refreshing too. The companion PR that skips identical failed inputs keeps that from re-emailing every five minutes.Verification:
parseManifestaccepts the file. A localresolveagainst GitHub succeeds (Will build v0.0.42-nightly-v2.20260929…fromcb64162dee). A localapplythen stops at the75be8c11conflict described above. Independent review on Codexgpt-6-sol(high), via T3 delegated task, found no actionable findings and independently confirmed the 422 and the ancestry.Work by Claude Opus 5.5 (1M context) in Claude Code, running in T3 Code.
🤖 Generated with Claude Code
Update: to stop the failure emails immediately, both
Fork NightlyandFork Nightly Orchestrator v2are now disabled on saphid/t3code (gh workflow disable). After merging #93 (and #94), re-enable them with: