mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-19 23:05:21 +00:00
* fix(server): abort timed-out watcher setups and back off their retries A watcher subscription that missed WORKSPACE_GIT_WATCHER_SUBSCRIBE_TIMEOUT_MS was abandoned but its startup scan kept walking the tree to completion, and recovery retried every five minutes forever, repeating the full scan each time. On a CPU-starved host that kept dozens of directories rescanning. - FileObserver.subscribe accepts an abort signal that stops the startup scan and rejects; WorkspaceGit aborts setups at the deadline and on dispose. - Consecutive setup timeouts extend the recovery delay past the 5-minute ladder cap, doubling up to one hour; an accepted subscription resets it. Degraded polling keeps its 5-60 s cadence meanwhile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(file-observer): keep an aborted observation's backend from starting Aborting a subscription closes its observation, which can happen while start() is still reading the root. The backend then started after its close had finished, and the native backend opened a root watcher that nothing would close. Co-authored-by: Spencer Shulem <1703265+Spshulem@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(file-observer): abort a subscription mid-scan in the abort test The test aborted before the backend started, so it passed with the abort listener removed. A tree past the Linux directory limit makes a scan that keeps walking fail on the limit instead of rejecting with the reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Spencer Shulem <spshulem@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com> Co-authored-by: Spencer Shulem <1703265+Spshulem@users.noreply.github.com>