snapshot: preserve central wiki state 2026-08-15 (7 modified + 1 new file)
This commit is contained in:
@@ -0,0 +1,41 @@
|
||||
# mnemosyne-tools-none — 2026-07-29
|
||||
|
||||
## FIXED: `memory.mnemosyne.tools: None` in config.yaml
|
||||
|
||||
**Root cause:** `~/.hermes/config.yaml` had `tools: None` under the mnemosyne section (line 183). The memory manager interprets `None` as a literal tool name filter and fails schema loading with:
|
||||
```
|
||||
WARNING: Memory provider 'mnemosyne' get_tool_schemas() failed: Unknown Mnemosyne tool(s) in memory.mnemosyne.tools: None.
|
||||
```
|
||||
Fallback: the next line registers all 40 tools anyway — no data loss, just noise.
|
||||
|
||||
**Fix applied:** Removed the `tools: None` line. Config now defaults to all tools (correct behaviour).
|
||||
|
||||
**Timeline:** 86 occurrences logged between Jul 28–29, 19 unique sessions affected.
|
||||
|
||||
---
|
||||
|
||||
# relay-scope-corruption — 2026-07-29
|
||||
|
||||
## SYMPTOM
|
||||
```
|
||||
WARNING agent.relay_runtime: Hermes Relay turn finalization failed
|
||||
RuntimeError: invalid argument: scope handle is not at the top of the stack
|
||||
File relay_runtime.py:644 end_turn → run_in_session → invoke
|
||||
File nemo_relay/scope.py:144 pop()
|
||||
```
|
||||
|
||||
## DETAILS
|
||||
- Hermes Agent 0.19.0, nemo_relay 0.6.0
|
||||
- 3 occurrences across 3 sessions within 33 min (07:37–08:10 UTC 2026-07-29)
|
||||
- Sessions: `20260723_024537_95c0e6f7`, `20260728_233758_0c6b3c0d`, `20260729_070054_b8452262`
|
||||
- Exception is caught (WARNING, not ERROR). Turn finalization may be incomplete.
|
||||
- No recurrence after 08:10.
|
||||
|
||||
## LIKELY CAUSE
|
||||
Scope push/pop ordering mismatch. Something pushes a scope that isn't at the top when `end_turn` tries to pop it. Could be a recovery code path (tool failure → cleanup) pushing scopes in wrong order, or a subagent spawning pattern leaking a scope.
|
||||
|
||||
## REPORTED
|
||||
Filed (or should be filed) under NousResearch/hermes-agent issues. No token available to auto-create.
|
||||
|
||||
## MONITORING
|
||||
Watch for recurrence. If persists, check whether the affected sessions share a common tool call pattern (subagent delegation, tool failure, etc.).
|
||||
Reference in New Issue
Block a user