wehub-resource-sync
6c9c7fe7f3
CI / integration tests (3.13) (push) Failing after 1s
Commit lint / pull request title (push) Has been skipped
Docs / links (push) Failing after 1s
CI / unit tests (3.13) (push) Failing after 1s
CI / lint (push) Failing after 1s
CI / integration tests (push) Failing after 1s
CI / package build (push) Failing after 1s
Commit lint / commit messages (push) Failing after 1s
CI / unit tests (push) Failing after 1s
1.5 KiB
1.5 KiB
description
| description |
|---|
| View EverMem debug logs to troubleshoot memory saving and retrieval issues |
EverMem Debug Log Viewer
View the EverMem debug log to troubleshoot issues.
Instructions
Show the user the recent debug log entries from /tmp/evermem-debug.log.
- First check if debug mode is enabled by looking for
EVERMEM_DEBUG=1in the plugin's.envfile - Read the last 50 lines of the debug log file
- If the file doesn't exist or is empty, inform the user how to enable debug mode
Actions
-
Check debug mode status:
grep "EVERMEM_DEBUG" /path/to/plugin/.env 2>/dev/null || echo "Not configured" -
Show recent logs:
tail -50 /tmp/evermem-debug.log 2>/dev/null || echo "No debug log found" -
Format the output for the user, highlighting:
[inject]entries for memory retrieval[store]entries for memory saving- Any errors or warnings
Output Format
📋 EverMem Debug Log
Status: Debug mode [ENABLED/DISABLED]
Log file: /tmp/evermem-debug.log
--- Recent Entries ---
[timestamp] [inject] ...
[timestamp] [store] ...
--- Tips ---
• Enable debug: Add EVERMEM_DEBUG=1 to .env
• Clear log: > /tmp/evermem-debug.log
• Live view: tail -f /tmp/evermem-debug.log
Additional Options
If the user specifies arguments:
clear- Clear the debug loglive- Show command for live monitoringfull- Show more lines (100+)inject- Filter to show only [inject] entriesstore- Filter to show only [store] entries