You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PR Verifier leaves the required PR Type and PR Issue checks stuck in progress when it cannot update its own check runs (404), blocking an approved PR #18764
On #18667 (head ac459c3c3, base v6, opened from a fork) the PR Verifier workflow run finishes green, but the two check runs it creates, PR Type and PR Issue, stay in_progress for ever. Tide requires both, so the pull request cannot merge although it is approved and every other check is green. Tide's status reads: "Not mergeable. Jobs PR Issue, PR Type have not succeeded."
Evidence
Workflow run 44069761061 (.github/workflows/pr-verifier.yml, event pull_request_target). First attempt 2026-11-17 10:58 UTC, re-run 16:23 UTC. Both attempts behave the same.
Log of the verify PR contents job on the re-run:
unable to update check run with results: PATCH .../check-runs/134186742530: 404 Not Found
unable to update check run with results: PATCH .../check-runs/134186742652: 404 Not Found
2 plugins had errors, exit code 2, then the wrapper's advisory warning, and the job is reported as success.
The verifier can create its check runs but gets 404 when it completes them. Find why (which token creates and which updates, and whether a re-run or this pull request's base changes that).
When the update fails, the checks are left in_progress and the wrapper job goes green. A required check must end in a definite state: if the verifier cannot report its result, the check must fail visibly with the reason, never hang.
Done when
PR Type and PR Issue always reach a conclusion, and a verifier that cannot write its result fails the job with a message saying so.
The PR body says this is partial/non-closing work (Refs/Part of or leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.
Verified: both fixes merged (v6 copy #18796, v5 copy #18795), so new events record PR Type / PR Issue in one completed create and a failed write fails the job. Remaining: #18667's two checks are still IN_PROGRESS on its head, because the fix only applies to new events. A person or App needs to flip a label on #18667 to record a fresh pair, then confirm Tide counts the newest run. Leaving this open for that confirmation.
Activity
hivecommons-hive commentedon Nov 17, 2026
🔓 Claim by agent
scannerreleased (holding agent relaunched).Claim history
scanner(agent on hive hosted-available-oke-11-placeholder-r05x)scanner(agent; holding agent relaunched)📖 PR Verifier: say which copy pull_request_target runs
📖 PR Verifier: say which copy pull_request_target runs
🐛 PR Verifier: record PR Type and PR Issue with one completed create,…
hivecommons-hive commentedon Nov 17, 2026
Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.
PR #18792 covers this issue: #18792
The PR body says this is partial/non-closing work (
Refs/Part ofor leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.🐛 PR Verifier (v5): record PR Type and PR Issue with one completed cr…
hivecommons-hive commentedon Nov 17, 2026
Verified: both fixes merged (v6 copy #18796, v5 copy #18795), so new events record
PR Type/PR Issuein one completed create and a failed write fails the job. Remaining: #18667's two checks are stillIN_PROGRESSon its head, because the fix only applies to new events. A person or App needs to flip a label on #18667 to record a fresh pair, then confirm Tide counts the newest run. Leaving this open for that confirmation.🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknown— hive: agent=scanner backend=claude model=claude-sonnet-5-5 claude=2.1.326
clubanderson commentedon Nov 18, 2026
Closing by hand: delivered by #18795 (merged to v5). v5 merges with Refs do not auto-close, so a maintainer closes it after the merge.