Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
34523
Environment issue→
7cb2bda4 fix(core): expand macOS FileEventKind allowlist in daemon watcher After the watchexec upgrade in #34329, the macOS event kind allowlist only permitted Create(Folder) and Modify(Metadata(_)). macOS FSEvents emits Create(Any), Remove(Any), and Modify(Any) event kinds for file operations, so the catch-all fallback silently dropped all file modification, creation, and removal events. This adds Create(Any), Remove(Any), and Modify(Any) to the macOS cfg block, matching the existing Linux and Windows allowlists. Fixes #34522 -Agent Generated Commit Message Amp-Thread-ID: https://ampcode.com/threads/T-019c77cb-45ff-73bb-8d3c-a32d99d87ad3 Co-authored-by: Amp <amp@ampcode.com>
4 hours ago by comp615
Failed
33572
Flaky task→
9eb4d953 fix(core): run post-task lifecycle for run-command parallel exections
1 month ago by comp615
Succeeded
33562
795059a1 fix(core): revise to match
2 months ago by comp615
Failed
33562
Flaky task→
795059a1 fix(core): revise to match
2 months ago by comp615
Failed
33562
Fix ready→
96e77789 fix(core): revise to match
2 months ago by comp615
Succeeded
master
d5bd57e6 fix(core): include PNPM patches in externalDependencies hash computations (#33551) ## Current Behavior If a workspace uses pnpm and adds a local patch to a dependency (e.g. `vitest`), this patch is not taken into account when computing that dependency's hash for purposes of determining cache changes. In practice, you could patch vitest locally, and tests would pull from the cache. ## Expected Behavior Patches can alter behavior in the same way that updating the version could, it's just that the version is not created and the patch is applied locally. This updates the pnpm lockfile parsing functionality to read the patches field into a map and then combine the patch hash with the integrity hash. The integrity hash ONLY represents the remote / tarball intergrity, so these have to be combined in order to create a proper key. ## Related Issue(s) (Could not find any, but saw this in my work today) --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
2 months ago by comp615
Failed
33562
Flaky task→
b584d735 fix(core): revise to match
2 months ago by comp615
Failed
33562
Flaky task→
b584d735 fix(core): revise to match
2 months ago by comp615
Succeeded
master
d5bd57e6 fix(core): include PNPM patches in externalDependencies hash computations (#33551) ## Current Behavior If a workspace uses pnpm and adds a local patch to a dependency (e.g. `vitest`), this patch is not taken into account when computing that dependency's hash for purposes of determining cache changes. In practice, you could patch vitest locally, and tests would pull from the cache. ## Expected Behavior Patches can alter behavior in the same way that updating the version could, it's just that the version is not created and the patch is applied locally. This updates the pnpm lockfile parsing functionality to read the patches field into a map and then combine the patch hash with the integrity hash. The integrity hash ONLY represents the remote / tarball intergrity, so these have to be combined in order to create a proper key. ## Related Issue(s) (Could not find any, but saw this in my work today) --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
2 months ago by comp615
Failed
33572
0a1400b9 fix(core): run post-task lifecycle for run-command parallel exections
2 months ago by comp615
Canceled
master
d5bd57e6 fix(core): include PNPM patches in externalDependencies hash computations (#33551) ## Current Behavior If a workspace uses pnpm and adds a local patch to a dependency (e.g. `vitest`), this patch is not taken into account when computing that dependency's hash for purposes of determining cache changes. In practice, you could patch vitest locally, and tests would pull from the cache. ## Expected Behavior Patches can alter behavior in the same way that updating the version could, it's just that the version is not created and the patch is applied locally. This updates the pnpm lockfile parsing functionality to read the patches field into a map and then combine the patch hash with the integrity hash. The integrity hash ONLY represents the remote / tarball intergrity, so these have to be combined in order to create a proper key. ## Related Issue(s) (Could not find any, but saw this in my work today) --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
2 months ago by comp615
Failed
33562
Environment issue→
59d6c3fc fix(core): include continuous tasks in taskResults
2 months ago by comp615
Failed
33572
0a1400b9 fix(core): run post-task lifecycle for run-command parallel exections
2 months ago by comp615
Succeeded
33551
3f7fcc23 fix(core): handle pnpm patch specifiers
2 months ago by comp615
Failed
33551
Environment issue→
c24c7a67 fix(core): include PNPM patches in externalDependncy hash computations
2 months ago by comp615