airkjw/claude-mem
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: log warning when readiness times out on reused-worker path (#1491)

Browse Source 
Mirror the fresh-spawn path's timeout logging for debugging parity.
CodeRabbit nitpick on PR #1491.

Co-Authored-By: CC <noreply@anthropic.com>
This commit is contained in:
Ryan Malia
2026-03-25 16:07:44 -07:00
parent 83f61177c7
commit b0f1a458cf
3 changed files with 142 additions and 137 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugin/scripts/mcp-server.cjs
+1 -1
View File
File diff suppressed because one or more lines are too long
plugin/scripts/worker-service.cjs
+137 -135
View File
File diff suppressed because one or more lines are too long
src/services/worker-service.ts
+4 -1
View File
@@ -989,7 +989,10 @@ async function ensureWorkerStarted(port: number): Promise<boolean> {
// another hook just spawned it and background init is still running. // another hook just spawned it and background init is still running.
// This mirrors the fresh-spawn path (line ~1025) so concurrent hooks // This mirrors the fresh-spawn path (line ~1025) so concurrent hooks
// don't race past a cold-starting worker's initialization guard. // don't race past a cold-starting worker's initialization guard.
await waitForReadiness(port, getPlatformTimeout(HOOK_TIMEOUTS.READINESS_WAIT)); const ready = await waitForReadiness(port, getPlatformTimeout(HOOK_TIMEOUTS.READINESS_WAIT));
if (!ready) {
logger.warn('SYSTEM', 'Worker is alive but readiness timed out — proceeding anyway');
}
logger.info('SYSTEM', 'Worker already running and healthy'); logger.info('SYSTEM', 'Worker already running and healthy');
return true; return true;
} }