3 people 8dcf92f285 fix(watch): schedule a sync when a directory is deleted (#1313) ...

A directory deletion arrives as ONE event on the directory's own path.
That path has no source extension, so handleChange dropped it at the
isSourceFile gate before ever scheduling a sync — and the files inside
may never get events of their own (Windows's recursive watcher reports
only the top-most removed entry; FSEvents can coalesce a tree deletion
the same way). Every child record then sat stale in the index until an
unrelated edit happened to trigger a sync (#1285).

A non-source path that no longer EXISTS on disk now schedules the
debounced sync; the sync's scan-diff removes whatever vanished (already
correct — verified: manual `codegraph sync` cascades fine). Events for
live non-source files stay fully ignored, so build churn schedules
nothing.

Fixes #1285

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-07-16 15:27:10 -05:00

..

git-hooks.ts

fix(sync,installer): time-bound the git/npm subprocess calls that had no timeout (#1139) (#1148)

2026-07-02 17:11:19 -05:00

index.ts

fix(watcher): retain pending files on zero-result sync (#450)

2026-05-26 13:47:04 -05:00

watch-policy.ts

fix(mcp): skip fs.watch on WSL2 /mnt drives that hang MCP startup (#199) (#210)

2026-05-20 10:32:08 -05:00

watcher.ts

fix(watch): schedule a sync when a directory is deleted (#1313)

2026-07-16 15:27:10 -05:00

worktree.ts

fix(sync,installer): time-bound the git/npm subprocess calls that had no timeout (#1139) (#1148)

2026-07-02 17:11:19 -05:00