ROOH/MATTERMOST_OPENCLAW_LIVESTATUS
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Revert "fix: ghost watch false-positive reactivation on trailing writes"

Browse Source 
This reverts commit 5c4a665fb9.
This commit is contained in:
Xen
2026-03-10 08:38:41 +00:00
parent 5c4a665fb9
commit 07c6fd701b
1 changed files with 1 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/status-watcher.js
View File

@@ -341,21 +341,9 @@ class StatusWatcher extends EventEmitter {
// Ghost watch: file changed for a completed session — signal immediate re-detection
if (sessionKey.startsWith('\x00ghost:')) {
const originalKey = sessionKey.slice(7);
// Only trigger reactivation if the lock file currently exists.
// A JSONL write without a lock file is a trailing write from the just-completed
// turn — not a new user message. Emitting reactivation here causes a false
// complete→reactivate→complete loop within the same turn.
const lockFile = fullPath + '.lock';
const lockExists = (() => { try { fs.statSync(lockFile); return true; } catch (_) { return false; } })();
if (!lockExists) {
if (this.logger) {
this.logger.debug({ sessionKey: originalKey }, 'fs.watch: ghost file change but no lock file — skipping reactivation (trailing write)');
}
return;
}
// Do NOT delete ghost entry here — let caller clean up after pollNow confirms the session
if (this.logger) {
this.logger.info({ sessionKey: originalKey }, 'fs.watch: file change on completed session (lock file present) — triggering reactivation');
this.logger.info({ sessionKey: originalKey }, 'fs.watch: file change on completed session — triggering reactivation');
}
this.emit('session-reactivate', originalKey, fullPath);
return;