Repository navigation
fix(agents): retry transient executable conflicts - #29
Conversation
411e778 to
88f01fe
Compare
|
@coderabbitai full review |
✅ Action performedFull review finished. |
|
Agent review of Minimalism: 9/10. Elegance: 9/10. Correctness: 9/10. No blocking findings in the current diff. Only executable-busy spawn failures retry, for ten 10-millisecond waits. No provider request is written before successful spawn; protocol negotiation and deployment retain the same staged bytes. Persistent write conflicts and unrelated launch errors still fail. Validation: the transient-writer regression failed against the original spawn path; all three added cases pass. The integrated desktop native suite passed 3,445 tests. Thirty parallel runs of the 13 provider tests passed (390 executions), including protocol mismatch and staged-source replacement checks. Native Clippy with warnings denied passed. The complete local CI command has not passed in one run; unrelated mobile timeout cases passed in isolation and the terminal unit suite passed in an isolated Linux container with standard tools. Human workflow confirmation remains pending under AGENTS.md. |
88f01fe to
aebb2ee
Compare
|
@coderabbitai full review |
✅ Action performedFull review finished. |
|
@thebrandonlucas please review this PR, layer 1 of 23 in the remote-agent stack. Assigned to @tee8z. CodeRabbit's review has no outstanding actionable findings at |
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
CI note: this stack still hits flaky tests in code it does not change. When one of these fails here, the failure is unrelated to this PR, and a re-run usually passes.
Summary jobs from cancelled runs also stay red until the replacement run finishes. A failure in this PR's own code gets a fix in this PR. @thebrandonlucas it's fine to approve without CI fully passing. |
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
@coderabbitai review |
|
Provider launches and adapter version probes could fail when a concurrent fork briefly kept the executable open for writing. Share a bounded retry for
ExecutableFileBusy: ten retries at 10 ms intervals. Other launch errors propagate immediately, and version probes include retries within their existing five-second deadline.Validation: the new regression test reproduced the missing-version result before the fix. After the fix, eight version-probe tests, three provider-launch tests, and 40 repeated writer-conflict cases passed. The full native suite passed 3,453 tests with 19 ignored. Native Clippy, Rust formatting, and the file-size checks passed.
Stack: layer 1 of 24. Base:
main. Next: #24. One signed commit per layer. Fresh GitHub CI is running across the stack. No human runtime acceptance is claimed.Summary by CodeRabbit
Bug Fixes
Tests