NousResearch/hermes-agent

batch_runner resume skipping discarded no-reasoning samples

Cluster 93527. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #93653 on 24 Aug 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 #93653. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #93653. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #93653 Pick up a Lab task

These issues and PRs concern a bug where the batch_runner's --resume flag re-runs every previously discarded no-reasoning sample because the content-based resume scan cannot detect them. The proposed fix involves writing tombstone rows so that --resume can recognize and skip those discarded prompts.

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.

#93653 fix(batch_runner): --resume stops re-running discarded no-reasoning samples (#93527, salvage #93542 + #93579)

merged to main

files: batch_runner.py, tests/test_batch_runner_checkpoint.py, tests/test_batch_runner_discard_resume.py

2 PRs closed without merging

From the close comments: merged via another change 2

#93542 fix(batch_runner): write a discard tombstone so resume skips no-reasoning prompts · merged via another change → 316d52f, a26154a, #93527, #9950, #12997
#93579 fix(batch_runner): make no-reasoning discarded samples visible to --resume (tombstone rows) · merged via another change → #93653, #93542

Closed issues · 1

Closed#93527[Bug]: batch_runner --resume re-runs every no-reasoning discarded sample; the content-based resume scan never sees them

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

Merged PRs: #93653
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 24 Aug 2026

For your agent

The same facts, typed.

cluster/93527.json
cluster/93527.md