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
perf: batch of low-risk fixes for hangs and unnecessary FS work (#187)
* fix(staleness): bound npm registry fetch with a timeout
fetchNpmVersion had no timeout/AbortSignal, so an unreachable or slow
npm registry could block `intent stale` indefinitely. Bound it to 5s;
timeout/error still falls through to the existing null fallback.
* fix(shared): bound global package-manager detection with a timeout
* perf(setup): early-exit skill-file check in getWorkspaceInfo
* perf(bench): add process-level cold-start benchmark
* perf: fix potential hangs on slow or large environments
* add timeout to node process execution in cold start benchmark
Fix potential hangs on slow or large environments:
6
+
7
+
- Bound the npm registry staleness check with a request timeout so `intent list` and other staleness checks can't hang indefinitely on a slow or unreachable registry.
8
+
- Bound global package-manager detection with a command timeout so it can't hang indefinitely when the environment's global `node_modules` is slow to resolve.
9
+
- Avoid enumerating a workspace package's entire skill tree just to check whether it has any skills, reducing filesystem work in large monorepos.
0 commit comments