Repository navigation
fix(core): avoid recompiling on Git index changes - #2080
willwashburn wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
[Low impact] The PR appears safe to merge.
|
There was a problem hiding this comment.
2 issues found across 4 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".agentworkforce/trajectories/codex-build-watch/completed/2026-11/traj_hynv0vdcl7gp/trajectory.json">
<violation number="1" location=".agentworkforce/trajectories/codex-build-watch/completed/2026-11/traj_hynv0vdcl7gp/trajectory.json:7">
P2: This completed trajectory is missing its generated `.trace.json` companion. Run the completion/finalization flow that emits the raw trace rather than committing only the summary and trajectory snapshot.</violation>
<violation number="2" location=".agentworkforce/trajectories/codex-build-watch/completed/2026-11/traj_hynv0vdcl7gp/trajectory.json:45">
P2: This completed trajectory omits the implementation commit and every changed path, so its audit record cannot identify the work it completed. Regenerate the completed trajectory metadata after recording the implementation commit instead of leaving `commits` and `filesChanged` empty.
(Based on your team's feedback about complete trajectory trace metadata.) [70713d7e-b5b6-4c02-88cf-a284a308fd60]</violation>
</file>
Reply with feedback, questions, or to request a fix.
View guided diff | Re-trigger cubic
| "task": { | ||
| "title": "Avoid rebuilding native core when Git index changes" | ||
| }, | ||
| "status": "completed", |
There was a problem hiding this comment.
P2: This completed trajectory is missing its generated .trace.json companion. Run the completion/finalization flow that emits the raw trace rather than committing only the summary and trajectory snapshot.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At .agentworkforce/trajectories/codex-build-watch/completed/2026-11/traj_hynv0vdcl7gp/trajectory.json, line 7:
<comment>This completed trajectory is missing its generated `.trace.json` companion. Run the completion/finalization flow that emits the raw trace rather than committing only the summary and trajectory snapshot.</comment>
<file context>
@@ -0,0 +1,53 @@
+ "task": {
+ "title": "Avoid rebuilding native core when Git index changes"
+ },
+ "status": "completed",
+ "startedAt": "2026-11-04T16:29:37.671Z",
+ "completedAt": "2026-11-04T16:32:57.025Z",
</file context>
| "approach": "Standard approach", | ||
| "confidence": 0.95 | ||
| }, | ||
| "commits": [], |
There was a problem hiding this comment.
P2: This completed trajectory omits the implementation commit and every changed path, so its audit record cannot identify the work it completed. Regenerate the completed trajectory metadata after recording the implementation commit instead of leaving commits and filesChanged empty.
(Based on your team's feedback about complete trajectory trace metadata.) [70713d7e-b5b6-4c02-88cf-a284a308fd60]
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At .agentworkforce/trajectories/codex-build-watch/completed/2026-11/traj_hynv0vdcl7gp/trajectory.json, line 45:
<comment>This completed trajectory omits the implementation commit and every changed path, so its audit record cannot identify the work it completed. Regenerate the completed trajectory metadata after recording the implementation commit instead of leaving `commits` and `filesChanged` empty.
(Based on your team's feedback about complete trajectory trace metadata.) [70713d7e-b5b6-4c02-88cf-a284a308fd60]</comment>
<file context>
@@ -0,0 +1,53 @@
+ "approach": "Standard approach",
+ "confidence": 0.95
+ },
+ "commits": [],
+ "filesChanged": [],
+ "projectId": "AgentWorkforce/relay",
</file context>
Touching the builder checkout’s Git index currently reruns
agent-relay-node’s build script and recompiles the core and its consumers, although the index does not affect any embedded metadata. Watch only HEAD and its active ref, preserving correct revision changes for branch and detached checkouts.The regression test compiles and executes the real build script against a temporary external Git checkout. It covers staging-only changes, commits on a branch and detached HEAD, and explicit release versions that bypass development changelog parsing. It rejects the original index watcher.
Validation:
--timingsand fingerprint logging confirm the original invalidation path:.git/index→ public node library → private desktop library → executable.Controlled local release benchmark (macOS, Rust 1.95.0,
CARGO_INCREMENTAL=0,--locked --offline --release --timings, fixed version2026.11.999):.git/indexThe before/after index measurements use the same local dependency path, target directory, desktop snapshot
17c4b47d3b507b74632a415e95d49b79aae1931a, and public source31eac487; only this build-script patch differs, with a seed build before each measurement. The desktop snapshot is an in-flight review tree, not landed main. The original Git dependency independently reproduced the index-only rebuild in 65.813s. These are single-run diagnostic measurements; host load varies. This is a local warm-build improvement, not a measured fresh-run CI release speedup. No runtime behavior or metadata contract changes.Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.