Skip to content

[selfreport] unclassified_error_repeated: stage labels: PR waits on the hive past the stage dwell — reviewer lane needs… #15009

Closed

Description

@hivecommons-hive

A hive hit an unusual runtime error (class unclassified_error_repeated) and is reporting it so the same defect across the fleet lands in one issue.

Evidence

Field Value
hive hosted-projectbluefin-knuckle-gjvq
hive name bluefin
spoke bluefin
anonymous instance 0f7701746ac14f88
owner(s) @castrojo, @clubanderson, @Danathar, @hanthor, @joshyorko
hive version 5.186.4-1516-g917078855
hive commit 9170788
cluster —
mode busy
component agent-runtime
scope stage labels: pr waits on the hive past the stage dwell — reviewer lane needs attention
message stage labels: PR waits on the hive past the stage dwell — reviewer lane needs attention
count + window 15 in 10m0s
first seen 2026-10-28T15:40:55Z
reported at 2026-10-28T16:41:21Z
repos —
owners —
repo —
ref —
self-recovered no

Affected hives (1):

Diagnostics (scrubbed)
WARN start=c4e2d97b repo=utah-packages pr=794 stage=050-review-pending quiet_for=1h1m0s reason=contributor-lane:no-linked-issue lane=contributor-lane

Activity

  1. hivecommons-hive commented on Oct 28, 2026

    @hivecommons-hive
    ContributorAuthor

    🔒 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.

  2. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 28, 2026
  3. hivecommons-hive commented on Oct 28, 2026

    @hivecommons-hive
    ContributorAuthor

    🔓 Claim by @Karibhou released (lease revoked).

  4. hivecommons-hive commented on Oct 28, 2026

    @hivecommons-hive
    ContributorAuthor

    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.


    🐝 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

  5. hivecommons-hive commented on Oct 28, 2026

    @hivecommons-hive
    ContributorAuthor

    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, 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.

  6. hanthor commented on Oct 28, 2026

    @hanthor
    Contributor

    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.

  7. github-actions commented on Oct 28, 2026

    @github-actions
    Contributor

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    has-open-prhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions