You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Workspace sync: a bare sync lists every file it can't check, one entry each, with no bound #289
From slimepriestess's review of #282 (its non-blocking note), filed as it suggested.
What. A bare sync (one naming no path) lists under skipped every tracked file it couldn't check, one entry per file. In the sync handler in src/modules/workspace/index.ts, the reports loop pushes { mount, path, reason } onto allSkipped for each unverified or disk-only report, with no bound.
Before #282, a watched mount's watcher took in files from under ignored paths, node_modules included, because chokidar was handed the ignore patterns as plain strings. #282 stops that. As its changelog says, the files already taken in stay tracked, and every bare sync lists each one as skipped ("disk could not be checked: ignored by the mount") for as long as disk can't show it gone. So on a deployment whose watcher fed it a project's node_modules, every bare sync a resident runs carries thousands of entries until that directory is removed.
A possible shape.#278 answered the same shape for regions the walk passes over with a count per mount and reason (passedOver). Past some threshold, the skipped listing could do the same: a count per region and reason, with the paths kept in the audit or returned when a sync names the region. It would keep a bare sync readable without hiding anything.
Not measured. This comes from the code and #282's changelog. We haven't seen it on a deployment.
Activity