Skip to content

Fix/workflow duration validation - #8699

Open
aihubworkflow wants to merge 3 commits into
block:mainfrom
aihubworkflow:fix/workflow-duration-validation
Open

aihubworkflow wants to merge 3 commits into
block:mainfrom
aihubworkflow:fix/workflow-duration-validation

Conversation

@aihubworkflow

Copy link
Copy Markdown

Summary

Related issue

Testing

@aihubworkflow
aihubworkflow requested a review from a team as a code owner October 29, 2026 18:54
@chatgpt-codex-connector

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 🔄 Running since 2026-10-29T18:54:35.793812Z 477f9b0 PR opened
ℹ️ 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.

@github-actions

github-actions Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is ccfc1490e451b99e8bc472ab7df5d65b0f4d3837...a019f3446383c298e7cf398a7089065fd75b2521.
A new review must complete for this exact range. When manual authorization
is required, a user with write access must comment exactly
@buzz-security-review a019f3446383c298e7cf398a7089065fd75b2521 to authorize a new review.
Any previous review applies only to its recorded range.

- parse_duration_secs accepts d suffix with overflow checks; - RequestApproval dispatch propagates timeout errors instead of silent 24h fallback; - WorkflowDef::validate rejects invalid/zero approval timeouts and delay durations, plus delays over 270s.

Signed-off-by: aihubworkflow <[email protected]>
SanHsien added a commit to SanHsien/buzz that referenced this pull request Oct 29, 2026
…dvance all three watermarks

32 commits, 54 PRs and 2 issues ruled on with pinned head SHAs; no product
change adopted yet. The block#8624 trigger is rewritten now that it closed unmerged.

Executed from the roadmap's near-term table; the finished row is removed in
the same commit.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: SanHsien <[email protected]>
@aihubworkflow
aihubworkflow force-pushed the fix/workflow-duration-validation branch from 477f9b0 to a019f34 Compare October 29, 2026 20:05

@joahg joahg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🤖 Blocking on the approver check in the new decide endpoint (inline). Rest (persist gate, resume-after-gate, duration validation) read fine. This PR overlaps #8709 (older version of the same WF-08 work, plus an unrelated hermit node bump); worth closing one. PR description is still the empty template.

}
true
}

@joahg joahg Nov 5, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🤖 P1: this concerns approver_spec_satisfied just above (the final return true at L529). Any spec that is not a bare 64-hex pubkey returns true, so a gate like from: '@manager' (the form used in the tests and docs) can be granted or denied by anyone who can read the workflow's channel, including whoever triggered the run. That leaves the approval gate unenforced for the common case. Fail closed until roles resolve: reject non-pubkey specs with 403, or restrict to channel owner/admin.

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