Repository navigation
fix: create Codex cache parent for fresh homes - #274
Merged
Merged
Conversation
tangletools
approved these changes
Oct 24, 2026
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved PR — fe9b4df1
Blanket team auto-approval is intentional. This is not a code review.
No automated review runs on this PR. This approval rests on the rule above alone.
tangletools · auto-approval · reason: blanket_auto_approve · 2026-10-24T19:19:49Z
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.
Codex MCP materialization fails in a fresh runner home because its stable temporary root assumes
HOME/.cachealready exists. Create that parent with private permissions before allocating the one-shot Codex home.The actual exported materializer reproduced ENOENT on Beelink1 with a fresh HOME before the change. The same real filesystem path succeeds after the change, creates mode0700, writes the expected native-command configuration, and cleans up its owned home. No tests were added or modified. Beelink2 frozen install, typecheck, diff checks and required commit/push hooks passed through the native gate (19s command; gate receipt retained with item10485).
This repairs nine cache-parent failures from the restored Tests workflow run40123886007. Two separate five-second timeout failures remain outside this fix and will be assessed from the shipped check. Preconditions: exact one-line source diff reviewed; completed native Beelink gate. Both are recorded before merge.
Run ID: run_96c1955f8080e72580cf1d36f2168e09