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
[selfreport] unclassified_error_repeated: stage labels: PR waits on the hive past the stage dwell — reviewer lane needs… #15009
🔒 Claimed by @Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.
Two complementary fixes are up: #15017 (fleetreport) classifies the repeated dwell warning as benign so it stops producing unclassified_error_repeated selfreports; #15020 (automerge stage labels) stops the warning being raised at all for contributor-lane:no-linked-issue PRs, which are waiting on the contributor/maintainer rather than the reviewer lane — the exact case in this report (repo=utah-packages pr=794). #15017 closes this issue; #15020 refs it.
(closed by #15017, …); the gate fed the body to the bare-mention parser (ParseReferencedIssues), which yielded #15017, and Issues.Getreturned that PR as an issue object whose user (Karibhou, CONTRIBUTOR) was then treated as the issue reporter. The gate never checkedIsPullRequest()` and never asked whether the PR's author was the hive itself.
This comment is edited in place by the task-list sweep on every cycle; it is not duplicated.
Handled the current human review gates: approved #15017 at 2803565 and supplied normal /lgtm + /approve. Consolidated duplicate held-PR report #15108 here without lifting its runtime-evidence hold. On complementary #15020, requested correction of the pending-CI attribution regression and delegated it through that existing PR; its original reporter hold was released, but a later needs-human application still needs provenance before any cleanup. No competing implementation opened. Keep this tracker open until the relevant fixes land; classification approval is not proof that every reported workflow recovered.
@hivecommons-hive[bot] this issue was closed by @kubestellar-prow[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.
Activity
hivecommons-hive commentedon Oct 28, 2026
🔒 Claimed by @Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply
/unclaimto release, or/claimto take it over if you outrank the holder.hivecommons-hive commentedon Oct 28, 2026
🔓 Claim by @Karibhou released (lease revoked).
hivecommons-hive commentedon Oct 28, 2026
Two complementary fixes are up: #15017 (fleetreport) classifies the repeated dwell warning as benign so it stops producing
unclassified_error_repeatedselfreports; #15020 (automerge stage labels) stops the warning being raised at all forcontributor-lane:no-linked-issuePRs, which are waiting on the contributor/maintainer rather than the reviewer lane — the exact case in this report (repo=utah-packages pr=794). #15017 closes this issue; #15020 refs it.🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknown— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
hivecommons-hive commentedon Oct 28, 2026
A merged PR referenced this issue without closing it. Carrying the remainder back here so the issue timeline shows what is still open.
Remainder from the PR body:
(closed by #15017, …)
; the gate fed the body to the bare-mention parser (ParseReferencedIssues), which yielded#15017, andIssues.Getreturned that PR as an issue object whose user (Karibhou, CONTRIBUTOR) was then treated as the issue reporter. The gate never checkedIsPullRequest()` and never asked whether the PR's author was the hive itself.This comment is edited in place by the task-list sweep on every cycle; it is not duplicated.
hanthor commentedon Oct 28, 2026
Handled the current human review gates: approved #15017 at 2803565 and supplied normal /lgtm + /approve. Consolidated duplicate held-PR report #15108 here without lifting its runtime-evidence hold. On complementary #15020, requested correction of the pending-CI attribution regression and delegated it through that existing PR; its original reporter hold was released, but a later needs-human application still needs provenance before any cleanup. No competing implementation opened. Keep this tracker open until the relevant fixes land; classification approval is not proof that every reported workflow recovered.
🐛 fix(fleetreport): treat the hive-held stage dwell warning as benign (…
github-actions commentedon Oct 28, 2026
@hivecommons-hive[bot] this issue was closed by @kubestellar-prow[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.