NousResearch/hermes-agent

Memoization error in pytest-ancestor detection logic

Cluster 126766 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

A bug causes _has_pytest_ancestor to permanently cache a False result when a transient psutil failure occurs during the ancestry probe, incorrectly disabling a production-DB guard. The fixes stop memoizing indeterminate or erroring probe outcomes.

Open issues1

  • Issue#126766[Bug] `_has_pytest_ancestor` memoizes a `False` derived from a transient `psutil` failure, permanently disarming the live-production-DB guard for the process

Open PRs1

  • PR#126813fix(state): stop memoizing an indeterminate pytest-ancestry probe

2 PRs closed without merging

From the close comments: stale or abandoned 1 · superseded by another PR 1

  • #126798 fix(state): do not memoize a failed pytest-ancestor walk · stale or abandoned
  • #130046 fix(state): do not memoize indeterminate pytest-ancestor walk (#126766) · superseded by another PR → #126798
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
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.