Fix ambiguous npx cache generation selection bug

NousResearch/hermes-agent · cluster 102576 · mcp

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 was identified where the npx cache fast-path could select an arbitrary or stale cache generation when multiple matches exist. These items address that issue by adding fallback behavior to real npx in ambiguous cases.

Open issues1

  • Issue#102576[Bug]: Cached npx fast path can execute an arbitrary stale cache generation

Open PRs2

  • PR#102578fix(mcp): stop npx cache fast-path from picking an ambiguous generation
  • PR#103698fix(tools): fall back to real npx when multiple cache generations match
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
mcp
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.