Skip to content

feat(lastcode): add resumable Intel builds - #106

Open
lastobelus wants to merge 1 commit into
lastcode/mainfrom
lastcode/build-intel-package-action
Open

feat(lastcode): add resumable Intel builds#106
lastobelus wants to merge 1 commit into
lastcode/mainfrom
lastcode/build-intel-package-action

Conversation

@lastobelus

Copy link
Copy Markdown
Owner

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.

@lastobelus

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Chef's kiss.

Reviewed commit: a61c3601e8

ℹ️ 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".

@lastobelus
lastobelus force-pushed the lastcode/build-intel-package-action branch from a61c360 to caadaf1 Compare August 27, 2026 03:08
@lastobelus

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment on lines +380 to +384
if (!run && request.dispatchAttemptedAt === null) {
request = { ...request, dispatchAttemptedAt: dependencies.nowIso() };
dependencies.writeRequest(request);
try {
dependencies.dispatchWorkflow(request);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

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.

1 participant