Bedrock ClientError HTTP status classification fix
NousResearch/hermes-agent · cluster 121294 · agent
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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items address a bug where Bedrock Converse client errors (such as 400 and 403 responses) were not having their HTTP status correctly extracted, causing them to be misclassified and incorrectly retried or reported as temporarily unavailable. The group includes the bug report and related fix attempts.
Open issues1
- Issue#121294Bedrock Converse: 400 ValidationException / 403 AccessDenied retried and reported as 'temporarily unavailable' (ClientError status never extracted)
Open PRs2
1 PR closed without merging
From the close comments: closed without comment 1
- #121558 fix(bedrock): classify native ClientError status and body · closed without comment
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.00means 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 LabAt a glance
- Subsystem
- agent
- Closed issues
- 0
- Attempts
- 1 PR closed without merging