NousResearch/hermes-agent
Fix duplicated Discord mock splitting module identity
Cluster 117996 · gateway. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab task
A bug where calling _ensure_discord_mock() multiple times installs a fresh MagicMock each time, causing the discord module identity to differ across test modules. The members address preserving a shared mock identity in tests to prevent this split.
Open issues1
- Issue#117996[Bug]: duplicated _ensure_discord_mock() installs a fresh MagicMock per call, splitting `discord` module identity across test modules
Open PRs1
- PR#124305test(discord): preserve shared mock identity
1 PR closed without merging
From the close comments: done elsewhere 1
-
#118201 fix(tests): preserve Discord mock identity · done elsewhere →
#124305,#117996
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.00means 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 LabAt a glance
- Subsystem
- gateway
- Closed issues
- 0
- Attempts
- 1 PR closed without merging