NousResearch/hermes-agent

Distinguishing clean EOF from network drop in streams

Cluster 102766. 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. 3 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

These items address a conflation bug where a clean EOF with no finish_reason is incorrectly labeled the same as a transport/network drop. The work involves separating diagnostics, labels, and handling for these two distinct stream-ending conditions.

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

1 PR closed without merging

From the close comments: done elsewhere 1

#102772 fix(stream): distinguish clean-EOF no-finish_reason from a transport drop · done elsewhere → 1f04155, #121639, #102766

Closed issues · 1

Closed#102766[Bug]: "Response truncated — stream ended before completion" conflates two distinct failure modes; type-2 (clean EOF, no finish_reason) needs its own diagnostics and is mislabeled as a network drop

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.67: 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

Merged PRs: #121639
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 26 Sep 2026

For your agent

The same facts, typed.

cluster/102766.json
cluster/102766.md