Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/fixed-delegate-plan-github-rate-limit.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- "Let hive decide" now says why a preview failed instead of "hive unavailable". While the hive's GitHub App was out of quota, every preview failed with "Could not preview owner/repo#N (hive unavailable)": the server answered 502, and the hosted Ingress replaces every 502 with its own "hive is restarting" body. The preview now answers 429 with a `Retry-After` header and reads "GitHub API rate limit for this hive is exhausted; resets at 17:32Z" (or the secondary limit's retry time); other GitHub refusals (a 404, a permission 403), a closed item or a missing dashboard snapshot answer 424 with the real message. 502 is left for a GitHub that could not be reached at all.
2 changes: 1 addition & 1 deletion src/docs/api-reference/packs-and-acmm.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Part of the [Dashboard REST API reference](../api-reference.md); see that page f
| `POST` | `/api/repos/{owner}/{repo}/items/{number}/hold` | Owner or repo write/maintain/admin | Add or remove a dashboard hold chip for an issue or PR. Body `{"held": true}` adds the hive's exact-match canonical `hive-pause/<hive-id>` label; `{"held": false}` removes exactly the labels causing the hold (`hive-pause/<hive-id>` and/or generic hold labels) and never removes `hive/<hive-id>` provenance. Every toggle writes an audit-log entry; the #8851 upgrade migration writes `/data/hive-hold-migration-<hive-id>.json` with audit-backed, provenance-only, and ambiguous legacy `hive/<hive-id>` classifications. | `pkg/dashboard/api.go:364`, `pkg/dashboard/api_repo_hold.go` |
| `POST` | `/api/repos/{owner}/{repo}/items/{number}/decision` | Owner or repo write/maintain/admin, signed-in GitHub user | Record an operator decision from the activity monitor's row menu / selection bar. Body `{"decision": "approve"|"direction"|"close-superseded"|"close-wontfix"|"adopt"|"reroute"|"re-author"|"merge-now"|"queue-merge", "comment": "…", "type": "issue"|"pr", "superseded_by": "#458", "force": true, "to": "<login>"|"any"}` (`force` only with `adopt`, `to` only with `reroute`; an unknown `decision` is a 400). On an issue parked at 045, `approve`/`direction` act exactly as a maintainer's `/hive approve` / `/hive decision <text>` comment would (labels, `approved-direction`, stage-engine Unparked fact, reply comment naming the operator). On a PR parked at 085 (`type: "pr"`), `approve` posts the `/lgtm` and `/approve` commands as two comments attributed to the operator, records the approval against the head as the human answer to a `requires_human` / decision-requested verdict (the lanes and the stage engine honour it like a trusted merger's Approve review), lifts `needs-human`, clears the sentinel label and acknowledges the bundle's sentinel findings for that head, re-derives the stage and drops the tracker cache — the response adds `released` (`approval-recorded`, `needs-human`, `sentinel-label`, `sentinel-acknowledged`) and `stage`; the merge gate decides from there (no review as the operator, no merge) — and `direction` records the text as a human change request against the head — the `/hive decision` fix lane — on a hive-authored PR, and on a contributor's clanker PR (`author/clanker` / hive attribution markers) where the text is posted to the contributor's hive and the PR moves to `stage/072-returned-to-contributor` (`status: "direction-returned-to-contributor"`); a person's PR, which no hive can carry direction to, answers 409. The close variants post a comment naming the operator (and the superseding PR when `superseded_by` is given) and close the item as not planned. `adopt` and `re-author` require `type: "pr"` and queue adoption via the `adoption/supersede` label (409 unless `governor.labels.stage.adoption` is enabled). `adopt` with `"force": true` is *Adopt now* ([#15038](https://github.com/hivecommons/hive/issues/15038)): it bypasses the author's presence, the grace window and `maintainer_policy`, marks the stage record and nudges the automerge sweep so the adoption engine supersedes the head at once (responds `status: "already-adopted"` when nothing is left to do; 400 on the hive's own PR). `reroute` (`type: "pr"`, `"to": "<clanker login>"|"any"`) hands the PR's follow-up work to another online clanker through the contributor fix queue, posts a `<!-- hive:rerouted … -->` note and arms a pickup timer that falls back to Adopt now after `governor.reroute.pickup_timeout`; answers `status: "rerouted"`, 409 when no clanker is online or adoption is disabled. On a PR at 090, `queue-merge` (*Approve and let hive merge*, the lead action) records an approval attributed to the operator and applies the automerge label, returning `status: "queued-for-merge"` (on the hive's own PR, which the App cannot review, the queue note is a comment and the operator's approval is recorded as `approve` records it — `released` lists `approval-recorded`, `admitted`); hive's merge sweep merges on its next tick once CI is green and the head has soaked, and that recorded operator approval is the one thing that lets the sweep merge an untrusted-author PR (the merge comment names the operator). `merge-now` (*Merge now as maintainer*, secondary) posts an attributed comment and merges immediately through the hive's GitHub App, returning `status: "merged"`. Both require `type: "pr"` and a verified owner or `merger` role in addition to the route's repo permission check; both refuse closed/merged PRs and the operator's own PR. `merge-now` on a PR whose `mergeable_state` is `dirty`/`behind` instead answers `202` with `status: "rebase-queued"` (approval recorded, rebase kicked, merge follows via the follow-through once the hive's own rebase is green; a head pushed by anyone else fails the follow-through closed; `head-not-pushable` refusal on a fork without maintainer edits). `approve` on such a PR adds `rebase: {attempt, max, exhausted, head, text}` for the rebase episode it opened. Every decision writes an audit-log entry (`repo_item_decision_*`, e.g. `repo_item_decision_adopt_now`, `repo_item_decision_reroute`). | `pkg/dashboard/api.go:365`, `pkg/dashboard/api_repo_item_decision.go` |
| `POST` / `GET` | `/api/repos/{owner}/{repo}/items/{number}/decide-delegated` | Same as `…/hold` (owner or repo write), signed-in GitHub user; `decisions.delegate.enabled` (403 when off) | *Let hive decide*: enqueue a delegated-decision job in which the hive decides the parked item itself as the owner's delegate under `pkg/delegatedecision.PolicyText` and records it as a human decision (`/hive decision` comment with the `<!-- hive:delegated-decision … -->` marker, park labels off, `triage/accepted`, queue approval on a PR head). Body `{"type": "issue"|"pr", "reason", "caption", "sentinel_reason"}`. `POST` answers 202 with the job (`{id, status: "running"|"done"|"failed", decision: {verdict, rule, text, rationale, actions, keeps_park, ladder?: {decision, reason, ruled_out[]}}, notes, error}`; `ladder` is set on contributor-PR decisions and names the rung that decided — `already-fixed` → `mergeable-as-is` → `rebase-then-merge` → `return-to-contributor` → `contributor-offline` — and why each rung above it did not apply); 409 with the running job while one is in flight; `GET` reads it. Rails: never merges, refuses items wearing `hold`, never grants secrets/permissions (`needs-owner` + `hold` instead), recommends only on hive policy/governance questions (keeps 085). Audited as `repo_item_decision_delegated[_failed]`. See [dashboard-sections.md](../dashboard-sections/activity-monitor.md#let-hive-decide). | `pkg/dashboard/api.go:329`, `pkg/dashboard/api_repo_item_decide_delegated.go` |
| `POST` | `/api/repos/{owner}/{repo}/items/{number}/decide-delegated/plan` | Same as `…/decide-delegated` | Preview for *Let hive decide*: runs the same owner-delegate policy with **no side effects** (nothing written, no job) and answers `{would, rule, acting, title, summary, why, consequences[], ladder, mergeable_as_is, alternatives[], writes: false, prior, notes, saw[], rule_plain, rationale, why_not[]}` — `summary` is one verb-first sentence with no "Hive would:" prefix (*Send #15332 back to its author with one instruction: make CI green, nothing else.*), `why` one short line (*CI is red.*), `consequences` at most two items, `ladder` the rung that decided with its `ruled_out` list, `saw` every fact the rules read as `{label, value, state}` (`state` is `ok`, `blocks` or `info`), `rule_plain` and `rationale` the deciding rule in plain words and its whole reason (`rationale` omitted when it only repeats `why`), `why_not` the ruled-out rungs as `{option, because}`, and `mergeable_as_is` whether an as-is merge is honest (the queue-merge and merge-now alternatives are dropped when it is not). The dialog shows **Cancel** / **Let hive do that**, plus **Approve and let hive merge** (or **Merge now as maintainer** when the hive would approve anyway) only when `mergeable_as_is`; only then does the SPA post `…/decide-delegated` with `chosen` naming the button. See [dashboard-sections.md](../dashboard-sections/activity-monitor.md#let-hive-decide). | `pkg/dashboard/api.go:369`, `pkg/dashboard/api_repo_item_decide_delegated_plan.go` |
| `POST` | `/api/repos/{owner}/{repo}/items/{number}/decide-delegated/plan` | Same as `…/decide-delegated` | Preview for *Let hive decide*: runs the same owner-delegate policy with **no side effects** (nothing written, no job) and answers `{would, rule, acting, title, summary, why, consequences[], ladder, mergeable_as_is, alternatives[], writes: false, prior, notes, saw[], rule_plain, rationale, why_not[]}` — `summary` is one verb-first sentence with no "Hive would:" prefix (*Send #15332 back to its author with one instruction: make CI green, nothing else.*), `why` one short line (*CI is red.*), `consequences` at most two items, `ladder` the rung that decided with its `ruled_out` list, `saw` every fact the rules read as `{label, value, state}` (`state` is `ok`, `blocks` or `info`), `rule_plain` and `rationale` the deciding rule in plain words and its whole reason (`rationale` omitted when it only repeats `why`), `why_not` the ruled-out rungs as `{option, because}`, and `mergeable_as_is` whether an as-is merge is honest (the queue-merge and merge-now alternatives are dropped when it is not). The dialog shows **Cancel** / **Let hive do that**, plus **Approve and let hive merge** (or **Merge now as maintainer** when the hive would approve anyway) only when `mergeable_as_is`; only then does the SPA post `…/decide-delegated` with `chosen` naming the button. A plan that cannot read the item says why, never with 502 or 503 (the hosted Ingress replaces those with its own *hive unavailable* page): 429 with `Retry-After` while GitHub rate-limits the hive (*GitHub API rate limit for this hive is exhausted; resets at 17:32Z*, or the secondary limit's *retry after* time); 424 with the real message for any other GitHub refusal (a 404, a permission 403), a closed item, or no dashboard snapshot yet; 502 only when GitHub could not be reached at all. See [dashboard-sections.md](../dashboard-sections/activity-monitor.md#let-hive-decide). | `pkg/dashboard/api.go:369`, `pkg/dashboard/api_repo_item_decide_delegated_plan.go`, `pkg/dashboard/delegated_gather_error.go` |
| `POST` | `/api/repos/{owner}/{repo}/items/{number}/blocker/recheck` | Same as `…/hold` (owner or repo write), signed-in GitHub user | *Re-check permissions* on an issue parked on a capability blocker (#15099): probes the GitHub App installation's permissions; when a non-workflows permission is granted, clears its ledger entries and un-parks the item; workflows blockers require a separate hand-off (`{result: {outcome: "released", …}}`), otherwise `{result: {outcome: "no-effect", reason: "blocker", options: [...]}}`; 404 when the item has no blocker, 409 when the blocker is not a capability gap | `pkg/dashboard/api.go:370` |
| `POST` | `/api/repos/{owner}/{repo}/items/{number}/blocker/handoff` | Same as `…/hold`, signed-in GitHub user | With a workflows blocker, verified App permission and capable lane, records the decision, clears the park and routes the issue to that lane; rejects held or ineligible issues | `pkg/dashboard/api.go:371` |
| `POST` | `/api/repos/{owner}/{repo}/items/{number}/blocker/close-partial` | Same as `…/hold` (owner or repo write), signed-in GitHub user | Option (c) on a capability blocker (#15099): labels the issue `hive/partially-addressed`, posts the operator's `{"comment"}` naming what remains and closes it; the ledger entry is cleared | `pkg/dashboard/api.go:372` |
Expand Down
2 changes: 1 addition & 1 deletion src/docs/dashboard-sections/activity-monitor.md
Original file line number Diff line number Diff line change
Expand Up @@ -677,7 +677,7 @@ The item leaves 085/045 and proceeds without the owner. The action is audited as

#### How it runs

1. The preview opens at once as a skeleton: the title, the item, **Asking the hive…** and placeholder lines (still under *prefers-reduced-motion*). **Cancel** works straight away; **Let hive do that** stays disabled until the plan lands and fills the dialog. Until then the row's *Let hive decide* button and its caption read **Asking the hive…** too, and a second click (button, ⋯ entry or popover) opens nothing. If the plan fails, the dialog says so inline with **Retry** — no toast, no browser alert.
1. The preview opens at once as a skeleton: the title, the item, **Asking the hive…** and placeholder lines (still under *prefers-reduced-motion*). **Cancel** works straight away; **Let hive do that** stays disabled until the plan lands and fills the dialog. Until then the row's *Let hive decide* button and its caption read **Asking the hive…** too, and a second click (button, ⋯ entry or popover) opens nothing. If the plan fails, the dialog says so inline with **Retry** — no toast, no browser alert — and gives the hive's reason: while GitHub rate-limits the hive it reads *Could not preview owner/repo#N (GitHub API rate limit for this hive is exhausted; resets at 17:32Z)*, so wait until then before retrying. *hive unavailable* means the hive itself did not answer (it is restarting or unreachable).
2. Read the one-time explanation and confirmation. **Don't ask again for this action** is optional; reset it in ⚙ → **Confirmations**.
3. The row reads **Hive deciding…** while the job runs.
4. Read the persistent result toast. It says what was decided and what happens next; it stays until the target row changes state.
Expand Down
2 changes: 1 addition & 1 deletion src/pkg/dashboard/api_repo_item_decide_delegated_plan.go
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ func (s *Server) handleRepoItemDecideDelegatedPlan(w http.ResponseWriter, r *htt
var err error
plan, err = s.planDelegatedDecision(ctx, repoFull, number, itemType, mergerRole, body)
if err != nil {
jsonError(w, err.Error(), http.StatusBadGateway)
delegatedGatherError(w, err, time.Now())
return
}
s.delegatedJobs.plans.put(key, plan, time.Now())
Expand Down
66 changes: 66 additions & 0 deletions src/pkg/dashboard/delegated_gather_error.go
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
package dashboard

import (
"context"
"errors"
"math"
"net"
"net/http"
"strconv"
"time"

gh "github.com/google/go-github/v72/github"
ghpkg "github.com/hivecommons/hive/pkg/github"
)

// delegatedGatherRetryFallback is the wait named when GitHub refused for
// quota without saying until when: GitHub's own rule for that case is to
// wait at least a minute.
const delegatedGatherRetryFallback = time.Minute

// delegatedGatherError answers a "Let hive decide" request whose live read
// of the item failed. On a hosted hive the Ingress swaps every 502 and 503
// for its canned "hive unavailable" body (custom-http-errors, see
// pkg/hub/saas_provision.go), so an error GitHub explained must not use
// them: projectbluefin's previews all read "(hive unavailable)" for half an
// hour while the hive was up and its App was out of quota.
func delegatedGatherError(w http.ResponseWriter, err error, now time.Time) {
status, msg, retry := delegatedGatherErrorStatus(err, now)
if retry > 0 {
w.Header().Set("Retry-After", strconv.Itoa(int(math.Ceil(retry.Seconds()))))
}
jsonError(w, msg, status)
}

// delegatedGatherErrorStatus maps a gather error to its answer: a GitHub
// rate limit (primary, secondary, or a request the pacer shed while one is
// in force) is 429 with the wait and the time it lifts; any other answer
// from GitHub (404, a permission 403, …) or a hive-side refusal (the item
// is closed, no snapshot yet) is 424 with the real message; only a request
// that never got an answer (network error, timeout) stays 502.
func delegatedGatherErrorStatus(err error, now time.Time) (int, string, time.Duration) {
if delay, limited := ghpkg.RateLimitRetryDelay(err, now); limited || errors.Is(err, ghpkg.ErrPacingShed) {
if delay <= 0 {
delay = delegatedGatherRetryFallback
}
var primary *gh.RateLimitError
if errors.As(err, &primary) {
return http.StatusTooManyRequests, "GitHub API rate limit for this hive is exhausted; resets at " + now.Add(delay).UTC().Format("15:04Z"), delay
}
// Round up so "retry after" is never early.
at := now.Add(delay + time.Minute - time.Nanosecond).UTC().Truncate(time.Minute).Format("15:04Z")
if !limited {
return http.StatusTooManyRequests, "This hive is pacing its GitHub requests after a rate limit; retry after " + at, delay
}
return http.StatusTooManyRequests, "GitHub secondary rate limit reached for this hive; retry after " + at, delay
}
var ghErr *gh.ErrorResponse
if errors.As(err, &ghErr) {
return http.StatusFailedDependency, err.Error(), 0
}
var netErr net.Error
if errors.As(err, &netErr) || errors.Is(err, context.DeadlineExceeded) {
return http.StatusBadGateway, err.Error(), 0
}
return http.StatusFailedDependency, err.Error(), 0
}
Loading
Loading