Cairn

Device-code slow_down backoff RFC 8628 compliance

NousResearch/hermes-agent · cluster 121254 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These items address a bug where the device-code authentication flow increments the polling interval by only 1 second on a slow_down response, rather than the 5 seconds required by RFC 8628. The cluster covers the bug report and related fixes targeting this specific backoff behavior.

Open issues1

  • Issue#121254[Bug]: device-code login backs off only +1s on slow_down (RFC 8628 requires +5s)

Open PRs2

  • PR#121262fix(auth): back off device-code slow_down by RFC 8628's mandated 5s
  • PR#122068fix(cli): grow the device-code poll interval by 5s on slow_down (#121254)

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #121260 fix(auth): apply RFC device-code slow-down backoff · stale or abandoned → 0ff4c74
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/121254.json
cluster/121254.md