Skip to content

[anneal][v1] Relocate Darwin translation tools in private archive staging - #3816

Open
joshlf wants to merge 1 commit into
Gqmwj6652y5h2ib2rvxvgckxsiwmzlcszfrom
G246gdcbsz2wjddnwbpl2g567g3kxnlx2
Open

joshlf wants to merge 1 commit into
Gqmwj6652y5h2ib2rvxvgckxsiwmzlcszfrom
G246gdcbsz2wjddnwbpl2g567g3kxnlx2

Conversation

@joshlf

@joshlf joshlf commented Oct 8, 2026 •

Copy link
Copy Markdown
Member

Darwin translation tools need their native dependencies to remain
loadable when the omnibus archive moves out of the Nix store. Automatic
fixups can alter producer load commands and signatures before the
complete archive payload is staged. Omitted release libraries or
host-dependent loader paths also prevent the tools from moving together.

Preserve downloaded and compiled Darwin producer bytes, and defer
explicit relocation and re-signing to fresh archive staging. Retain
Aeneas's release libraries beside its executable and resolve Charon's
Rust driver relative to the staged Rust payload so removal of
DYLD_LIBRARY_PATH by macOS shells cannot break that dependency. Allow
reviewed system-library substitutions only when symbol inspection finds
no imports from those libraries.

Statically walk the relocated dependency closure against the owned
Aeneas/Rust payload. Reject missing or ambiguous providers, escaping
loader paths and wrong architectures. Verify present signatures and
require signature verification on arm64. System-library compatibility
remains an explicit platform assumption.

Authored by an AI agent acting on joshlf's behalf.


Latest Update: v13 — Compare vs v12

📚 Full Patch History

Links show the diff between the row version and the column version.

Version v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v8 v7 v6 v5 v4 v3 v2 v1 Base
v7 v6 v5 v4 v3 v2 v1 Base
v6 v5 v4 v3 v2 v1 Base
v5 v4 v3 v2 v1 Base
v4 v3 v2 v1 Base
v3 v2 v1 Base
v2 v1 Base
v1 Base
⬇️ Download this PR

Branch

git fetch origin refs/heads/G246gdcbsz2wjddnwbpl2g567g3kxnlx2 && git checkout -b pr-G246gdcbsz2wjddnwbpl2g567g3kxnlx2 FETCH_HEAD

Checkout

git fetch origin refs/heads/G246gdcbsz2wjddnwbpl2g567g3kxnlx2 && git checkout FETCH_HEAD

Cherry Pick

git fetch origin refs/heads/G246gdcbsz2wjddnwbpl2g567g3kxnlx2 && git cherry-pick FETCH_HEAD

Pull

git pull origin refs/heads/G246gdcbsz2wjddnwbpl2g567g3kxnlx2

Stacked PRs enabled by GHerrit.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-08T17:24:42.672089Z dc8bfdf Manual request
🔒 Security Review ✅ Completed 2026-10-08T17:24:53.540019Z dc8bfdf Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@codecov-commenter

codecov-commenter commented Oct 8, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.94%. Comparing base (4fa5839) to head (0b41f12).

Additional details and impacted files
@@                        Coverage Diff                         @@
##           Gqmwj6652y5h2ib2rvxvgckxsiwmzlcsz    #3816   +/-   ##
==================================================================
  Coverage                              92.94%   92.94%           
==================================================================
  Files                                     16       16           
  Lines                                   2466     2466           
==================================================================
  Hits                                    2292     2292           
  Misses                                   174      174           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@joshlf
joshlf force-pushed the Gqmwj6652y5h2ib2rvxvgckxsiwmzlcsz branch from 19d62d5 to c844958 Compare October 8, 2026 11:23
@joshlf
joshlf force-pushed the G246gdcbsz2wjddnwbpl2g567g3kxnlx2 branch from 2011cd2 to 53df826 Compare October 8, 2026 11:23
@joshlf

joshlf commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

@codex review

The stack has been rebased onto current main after the SHA optimization merged. Please review this PR’s current diff. Current head: 53df8269fb6163720dcc7bc327612b1f781bcd6b.

Authored by an AI agent acting on joshlf's behalf.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Nice work!

Reviewed commit: 53df8269fb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 53df8269fb

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@joshlf
joshlf force-pushed the Gqmwj6652y5h2ib2rvxvgckxsiwmzlcsz branch from c844958 to 5b12697 Compare October 8, 2026 13:30
@joshlf
joshlf force-pushed the G246gdcbsz2wjddnwbpl2g567g3kxnlx2 branch from 53df826 to 302e843 Compare October 8, 2026 13:30
@joshlf

joshlf commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

@codex review

Please review the updated exact head 302e84308a5ce20fbd89e46aa80e51597c885cac. The Darwin closure cleanup is rebased onto current main.

Authored by an AI agent acting on joshlf's behalf.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Nice work!

Reviewed commit: 302e84308a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 302e84308a

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@joshlf
joshlf force-pushed the Gqmwj6652y5h2ib2rvxvgckxsiwmzlcsz branch from 5b12697 to a021df0 Compare October 8, 2026 14:21
@joshlf
joshlf force-pushed the G246gdcbsz2wjddnwbpl2g567g3kxnlx2 branch from 302e843 to 5996278 Compare October 8, 2026 14:21
@joshlf

joshlf commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

@codex review

Please review the updated exact head 599627841c3f8e0a670a22ee4a570810b728046d. The review unit is unchanged; this exact head incorporates the repaired lower CI boundary.

Authored by an AI agent acting on joshlf's behalf.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Nice work!

Reviewed commit: 599627841c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 599627841c

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@joshlf
joshlf force-pushed the G246gdcbsz2wjddnwbpl2g567g3kxnlx2 branch from 5996278 to dc8bfdf Compare October 8, 2026 17:21
@joshlf
joshlf force-pushed the Gqmwj6652y5h2ib2rvxvgckxsiwmzlcsz branch from a021df0 to 1c94fc8 Compare October 8, 2026 17:21
@joshlf

joshlf commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

@codex review

Please review the updated exact head dc8bfdfb50d628083805a7342b86b392fbcff4fa. Removed PR3814 from the ancestry and restored main's original separate early unit-test command and comments exactly. All other files in this prefix are byte-identical to the previously CI-passing and Codex-reviewed prefix; the conceptual review order is unchanged.

Authored by an AI agent acting on joshlf's behalf.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: dc8bfdfb50

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: dc8bfdfb50

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@joshlf
joshlf force-pushed the G246gdcbsz2wjddnwbpl2g567g3kxnlx2 branch from dc8bfdf to fa64d85 Compare October 10, 2026 00:00
@joshlf joshlf changed the title [anneal][v1] Preserve the Darwin native translation tool closure [anneal][v1] Relocate Darwin translation tools in private archive staging Oct 10, 2026
@joshlf
joshlf force-pushed the Gqmwj6652y5h2ib2rvxvgckxsiwmzlcsz branch from 1c94fc8 to 5bfbd8a Compare October 10, 2026 00:00
…ging

Darwin translation tools need their native dependencies to remain
loadable when the omnibus archive moves out of the Nix store. Automatic
fixups can alter producer load commands and signatures before the
complete archive payload is staged. Omitted release libraries or
host-dependent loader paths also prevent the tools from moving together.

Preserve downloaded and compiled Darwin producer bytes, and defer
explicit relocation and re-signing to fresh archive staging. Retain
Aeneas's release libraries beside its executable and resolve Charon's
Rust driver relative to the staged Rust payload so removal of
DYLD_LIBRARY_PATH by macOS shells cannot break that dependency. Allow
reviewed system-library substitutions only when symbol inspection finds
no imports from those libraries.

Statically walk the relocated dependency closure against the owned
Aeneas/Rust payload. Reject missing or ambiguous providers, escaping
loader paths and wrong architectures. Verify present signatures and
require signature verification on arm64. System-library compatibility
remains an explicit platform assumption.

gherrit-pr-id: G246gdcbsz2wjddnwbpl2g567g3kxnlx2
Agent-authored-by: AI agent acting on joshlf's behalf
@joshlf
joshlf force-pushed the Gqmwj6652y5h2ib2rvxvgckxsiwmzlcsz branch from 5bfbd8a to 4fa5839 Compare October 10, 2026 13:18
@joshlf
joshlf force-pushed the G246gdcbsz2wjddnwbpl2g567g3kxnlx2 branch from fa64d85 to 0b41f12 Compare October 10, 2026 13:18

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants