Repository navigation
Memtrace v1.2.3
Memtrace v1.2.3
External MemDB clients attach to the running daemon
Fixed
- In external MemDB mode, memtrace mcp and memtrace status attach to a running memtrace start daemon for the same workspace right away. Daemon liveness is now judged by the daemon's own heartbeat instead of a short probe of the remote database endpoint, which previously waited 12 seconds and then reported a healthy, idle daemon as not responding.
- MemDB endpoints without an explicit port, such as an Azure Container Apps address, resolve with the standard port for their scheme instead of being treated as unreachable.
Improved
- When an external-mode daemon really has stopped responding, the startup error reports the age of its last heartbeat so the stale owner is easier to recognise.
Install
npm install -g memtrace