Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35204
0ae0a848 fix(core): clear stale NX_ env vars on daemon env reflection The daemon mirrors each client's env on the first message of every CLI process so the project graph computation sees the right env. The reflection was additive only - it set keys present in payload.env but never deleted keys the daemon already had that the new client didn't. A var set by one CLI invocation (e.g. NX_PREFER_NODE_STRIP_TYPES=true for a single 'nx report' call) therefore persisted in the daemon forever, leaking into every subsequent client's plugin loading. The plugin worker's setWorkerEnv handler had the same bug. Extract applyDaemonEnvFromClient in daemon-environment.ts and use it from both call sites. Deletion is scoped to NX_-prefixed keys (skipping the daemon-side exclusions and required-settings sets) so unrelated process env (PATH, HOME, etc.) is left alone.
by Jason Jean
Succeeded
34946
c6ab9abf chore(repo): tighten dist-build-migration skill after self-review Deduplicates internal.ts guidance between Steps 2 and 16, splits the patched-jest-resolver step into workspace-wide and per-package changes, adds a blast-radius grep up front, notes the typesVersions/dist-path matching requirement, calls out which checks nx prepush does not cover (example apps, empty TypeDoc pages, cross-OS e2e), and replaces narrative phrasing with imperative steps.
by Jason Jean
Failed
35325
Generating fix→
4924e1fd fix(testing): import updateJson in federate-module e2e tests Both federate-module.{rspack,webpack}.test.ts call updateJson() to set remote port after generation, but the previous port-reservation migration missed importing it. Tests fail with TS2304 'Cannot find name updateJson'. Also bump bust.
by Jason Jean
Failed
35204
Generating fix→
0ae0a848 fix(core): clear stale NX_ env vars on daemon env reflection The daemon mirrors each client's env on the first message of every CLI process so the project graph computation sees the right env. The reflection was additive only - it set keys present in payload.env but never deleted keys the daemon already had that the new client didn't. A var set by one CLI invocation (e.g. NX_PREFER_NODE_STRIP_TYPES=true for a single 'nx report' call) therefore persisted in the daemon forever, leaking into every subsequent client's plugin loading. The plugin worker's setWorkerEnv handler had the same bug. Extract applyDaemonEnvFromClient in daemon-environment.ts and use it from both call sites. Deletion is scoped to NX_-prefixed keys (skipping the daemon-side exclusions and required-settings sets) so unrelated process env (PATH, HOME, etc.) is left alone.
by Jason Jean
Failed
35325
f3f61f5b chore(repo): bump bust to invalidate caches
by Jason Jean
Failed
35325
Fix applied→
f3f61f5b chore(repo): bump bust to invalidate caches
by Jason Jean
Succeeded
master
1cb67a25 chore(module-federation): re-enable webpack module federation e2e suites Reverts the temporary describe.skip blocks added in #35214. The @module-federation/enhanced dependency has been bumped (now 2.3.3) and upstream webpack compatibility is expected to be restored, so we let CI verify whether the suites pass again. NXC-4220
by Jason Jean
Failed
master
1cb67a25 chore(module-federation): re-enable webpack module federation e2e suites Reverts the temporary describe.skip blocks added in #35214. The @module-federation/enhanced dependency has been bumped (now 2.3.3) and upstream webpack compatibility is expected to be restored, so we let CI verify whether the suites pass again. NXC-4220
by Jason Jean
Succeeded
master
1cb67a25 chore(module-federation): re-enable webpack module federation e2e suites Reverts the temporary describe.skip blocks added in #35214. The @module-federation/enhanced dependency has been bumped (now 2.3.3) and upstream webpack compatibility is expected to be restored, so we let CI verify whether the suites pass again. NXC-4220
by Jason Jean
Failed
35325
d1e65bf8 chore(repo): bump bust to invalidate caches
by Jason Jean
Succeeded
35204
9693e88b chore(testing): assert nx success line in remaining maven tests Apply the same fix as maven-batch.test.ts to maven-name-overrides and maven-batch-v4: the install/clean targets run through the resident batch executor (which prints 'Nx Maven Summary'), so 'BUILD SUCCESS' (Maven CLI footer) never reaches the user-visible output. Drop the unused verbose flag too.
by Jason Jean
Succeeded
34946
b2a3ff47 chore(repo): expand dist-build-migration skill with steps learned from devkit migration Adds steps for the patched-jest-resolver condition update, hardcoded dist/packages path search in patches and e2e tests, typedoc tsconfig include/exclude/paths updates, and stronger guidance around internal.ts for previously-private subpath imports.
by Jason Jean
Canceled
35204
9693e88b chore(testing): assert nx success line in remaining maven tests Apply the same fix as maven-batch.test.ts to maven-name-overrides and maven-batch-v4: the install/clean targets run through the resident batch executor (which prints 'Nx Maven Summary'), so 'BUILD SUCCESS' (Maven CLI footer) never reaches the user-visible output. Drop the unused verbose flag too.
by Jason Jean
Canceled
35204
fb4170ae chore(testing): assert nx success line in remaining maven tests Apply the same fix as maven-batch.test.ts to maven-name-overrides and maven-batch-v4: the install/clean targets run through the resident batch executor (which prints 'Nx Maven Summary'), so 'BUILD SUCCESS' (Maven CLI footer) never reaches the user-visible output. Drop the unused verbose flag too.
by Jason Jean
Canceled
35204
f00e143f chore(testing): drop verbose flag from maven batch tests verbose: true flips Maven's -X debug flag, flooding output with class realm/mojo internals that aren't useful for the assertions. Drop the unused option from the runBatchCLI helper too.
by Jason Jean
Failed
35204
Flaky task→
f00e143f chore(testing): drop verbose flag from maven batch tests verbose: true flips Maven's -X debug flag, flooding output with class realm/mojo internals that aren't useful for the assertions. Drop the unused option from the runBatchCLI helper too.
by Jason Jean
Failed
35204
Flaky task→
0fd6d2e5 chore(testing): revert cache.test.ts line-216 assertion to local cache the rerunWithNewUnrelatedFile case writes an extra file into dist before the rerun. with daemon on, the outputs-hash check sees the extra file, returns no-match, and nx restores from cache → that prints '[local cache]', not '[existing outputs match the cache]'. my earlier sweep updated this line incorrectly. revert to 'local cache' and add a comment explaining the daemon-on path.
by Jason Jean
Failed
35204
Flaky task→
fd74f4e3 fix(core): avoid race in startInBackground that nulls out file handles startInBackground opens two log file handles into this._out / this._err across two awaits, then passes their .fd to spawn(). If the previous daemon's socket close handler fires reset() during either await — which happens whenever lockfile-update or any other restart-the-daemon path overlaps with the close — reset() sets this._out = this._err = null, and the spawn line throws "Cannot read properties of null (reading 'fd')". Open into local consts first, assign to instance fields after the spawn line has captured the fds. Hits in the e2e release suite where the daemon restart happens between cli invocations.
by Jason Jean
Canceled
35204
fd74f4e3 fix(core): avoid race in startInBackground that nulls out file handles startInBackground opens two log file handles into this._out / this._err across two awaits, then passes their .fd to spawn(). If the previous daemon's socket close handler fires reset() during either await — which happens whenever lockfile-update or any other restart-the-daemon path overlaps with the close — reset() sets this._out = this._err = null, and the spawn line throws "Cannot read properties of null (reading 'fd')". Open into local consts first, assign to instance fields after the spawn line has captured the fds. Hits in the e2e release suite where the daemon restart happens between cli invocations.
by Jason Jean
Canceled
35204
fd74f4e3 fix(core): avoid race in startInBackground that nulls out file handles startInBackground opens two log file handles into this._out / this._err across two awaits, then passes their .fd to spawn(). If the previous daemon's socket close handler fires reset() during either await — which happens whenever lockfile-update or any other restart-the-daemon path overlaps with the close — reset() sets this._out = this._err = null, and the spawn line throws "Cannot read properties of null (reading 'fd')". Open into local consts first, assign to instance fields after the spawn line has captured the fds. Hits in the e2e release suite where the daemon restart happens between cli invocations.
by Jason Jean