Run details

NxWorkspace

CI Pipeline Executions
- Current executionCanceled
  sj/daemon-outdated-check-events
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Sign in

fix(core): check the lockfiles on watch events instead of every 20 ms The daemon's outdated check ran on a 20 ms interval. Every tick read the process file, resolved the installed nx version and hashed every lockfile at the workspace root. With a 1.7 MB yarn.lock an idle daemon read the file 34 to 50 times a second: 8 to 12% of a core and 57 MB/s on a Windows laptop, 5 to 6% of a core on an M4 Mac, for a daemon doing nothing. The watch already names every changed path. The lockfile hash is now recorded once, before the watch starts, and compared only when a batch names a lockfile at the root; a change the kernel dropped arrives as an ordinary batch after the re-walk. The process-file check already ran on the watch event for that file, and now also runs when the watch reports dropped events, since that event may have been among them. A client connection runs all three checks once before the daemon serves it, so a change the watch never reported is still caught at the next request. The interval is gone.

nx affected --targets=lint,oxlint,test,build,e2e,e2e-ci,format-native,lint-native,check-native-wasm,gradle:build-ci,vale,run,validate-example

Canceled

read access token used

d8157d7737113

99%

Completed tasks

726 of 728 completed.

<1%

Not executed tasks

2 of 728 tasks were not executed.

1%

Potential flaky tasks

5 of 728 tasks retried.

17%

Cache hits

127 of 728 tasks used cache.

94%

Distribution saved time

1h 38m 51s instead of 29h 00m 50s.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

NxWorkspace