feat(lastcode): add resumable Intel builds - #106
Conversation
|
@codex review |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
a61c360 to
caadaf1
Compare
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: caadaf1b78
ℹ️ 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".
| if (!run && request.dispatchAttemptedAt === null) { | ||
| request = { ...request, dispatchAttemptedAt: dependencies.nowIso() }; | ||
| dependencies.writeRequest(request); | ||
| try { | ||
| dependencies.dispatchWorkflow(request); |
There was a problem hiding this comment.
Serialize the request claim before dispatching
When two Project Actions for the same worktree are launched from different threads, their separate Node processes can both read dispatchAttemptedAt === null, observe no registered run, and reach this write before either dispatch becomes visible. The atomic file rename does not make this read/check/write sequence exclusive, so both processes can call dispatchWorkflow with the same token; GitHub then creates duplicate runs and findCorrelatedRun rejects them once both appear. Claim the shared request with a cross-process lock or compare-and-swap before dispatching.
Useful? React with 👍 / 👎.
Build Intel artifacts currently requires manual workflow dispatch and external polling. This adds a resumable Project Action and script that select an exact remote checkpoint/revision tag and commit, dispatch the existing Intel workflow once with a unique request token, waits internally for the uniquely correlated run, and resumes with a verified terminal result.
The action only builds and verifies the immutable Intel release. It does not stage, install, promote, restart, or update htulo; the agent retains the decision to build.
Focused coverage exercises exact tag resolution, at-most-once dispatch, unique run correlation, restart reattachment, terminal outcomes, timeouts, and release verification. The normal guarded push also passed the complete quick-CI suite.
Tracks #103.
Implemented with GPT-5.6 Codex in the T3 Code harness.