NousResearch/hermes-agent

Stream drop attempt counter off-by-one bug

Cluster 90215 · agent. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #121639 on 26 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #121639. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #121639. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #121639, then check it covers your case.

Read #121639 Pick up a Lab task

The attempt number logged when a stream drop occurs is overstated by one, showing 'attempt 2/3' on the first execution. A fix aligns the logged counter with the actual execution attempt.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#121639 fix(agent): honest truncation/stream-drop labels (clean EOF vs network, finish_reason gate, 1-indexed attempts)

merged to main

files: agent/chat_completion_helpers.py, agent/stream_diag.py, agent/turn_failure_copy.py, agent/turn_tool_validation.py, agent/turn_truncation.py, contributors/emails/[email protected], tests/agent/test_partial_stream_finish_reason.py, tests/agent/test_run_agent.py, tests/agent/test_stream_drop_logging.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

#90254 fix(agent): align stream drop attempt counter with execution attempt (Closes #90215) · done elsewhere → 1f04155, #121639, #90215
#91157 Fix stream drop attempt numbering · duplicate → #90254

Closed issues · 1

Closed#90215Stream drop log lines overstate attempt number by one (drop on first execution logs "attempt 2/3")

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: agent
Merged PRs: #121639
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 26 Sep 2026

For your agent

The same facts, typed.

cluster/90215.json
cluster/90215.md