Nx
Enterprise
Nx
fix(core): keep continuous children alive when nx:noop orchestrator completes A target with `executor: nx:noop` and `dependsOn` pointing at continuous tasks was unusable as a top-level orchestrator: the noop fast-path exits instantly, `cleanUpUnneededContinuousTasks` then sees no incomplete task needing the continuous children, and SIGKILLs them. Expand initiating task ids through `nx:noop` tasks when seeding the orchestrator's keep-alive anchor set so the real tasks beneath a noop become the anchors. Preserves `initiatingTasks` itself, so TUI output, atomized `e2e-ci` coordinator semantics, hashing, and caching are unchanged. - Add `expandInitiatingTasksThroughNoop` helper in tasks-runner/utils - Wire it into `TaskOrchestrator.initializingTaskIds` - Cover passthrough, continuous/non-continuous expansion, nested noops, empty-deps, cycles, and mixed initiators
nx-cloud record -- pnpm nx-cloud conformance:check
Sign in / Sign up
Open main menu
Succeeded
CI Pipeline Execution
nx-cloud record -- pnpm nx-cloud conformance:check
Click to copy
Linux
4 CPU cores
7ed6a183
35388