Cairn

sys.exit() nonzero exit not reported as failure

NousResearch/hermes-agent · cluster 123561 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 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.

A bug where execute_code session kernels incorrectly report nonzero sys.exit() calls as success, also dropping any exit message text. The members include a bug report and related fix attempts addressing this behavior.

Open issues1

  • Issue#123561[Bug]: execute_code session kernel reports sys.exit(1) as success and drops the sys.exit("message") text

Open PRs2

  • PR#123562fix(execute_code): report a nonzero sys.exit() from a kernel cell as a failure
  • PR#123580fix(execute_code): report nonzero sys.exit() as an error in session kernels
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

Subsystem
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/123561.json
cluster/123561.md