Azure detection reads response bodies without size limit
NousResearch/hermes-agent · cluster 54759 · hermes cli
Data as of
Nothing open on GitHub. Fix merged in #115727. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #115727. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115727. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests concern Azure auto-detection logic that reads HTTP probe response bodies without an upper bound on size. The fixes introduce a cap on how much response body data is read during detection.
Open issues0
Open PRs0
Fixes on record
-
#115727 fix(cli): Azure endpoint auto-detection stops buffering oversized probe bodies (#54759, salvage #54760)
files:
hermes_cli/azure_detect.py,tests/hermes_cli/test_azure_detect.py
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 2
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.44: 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
- hermes cli
- Merged PRs
- #115727
- Closed issues
- 2
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 19 Sep 2026