Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
34506
303e102b Merge branch 'master' into fix/help-handler-exit
23 hours ago by FrozenPandaz
Canceled
34506
e0a692f3 fix(core): unref daemon client socket to allow natural process exit The main daemon client socket created in setUpConnection() was keeping the Node.js event loop alive after command completion, requiring every command handler to call process.exit() explicitly. By calling socket.unref(), the socket no longer prevents the process from exiting naturally. The existing keep-alive setTimeout in sendMessageToDaemon() ensures the process stays alive while actively awaiting daemon responses.
2 days ago by AgentEnder
Failed
34506
Environment issue→
c1c20fd0 fix(core): unref daemon client socket to allow natural process exit The main daemon client socket created in setUpConnection() was keeping the Node.js event loop alive after command completion, requiring every command handler to call process.exit() explicitly. By calling socket.unref(), the socket no longer prevents the process from exiting naturally. The existing keep-alive setTimeout in sendMessageToDaemon() ensures the process stays alive while actively awaiting daemon responses.
2 days ago by AgentEnder
Canceled
34506
bb154cc5 fix(core): exit process after showing help for known commands When running `nx show project --help` or similar commands that hit the help path in init-local.ts, the process would hang indefinitely. This is because yargs' built-in help is disabled (`.help(false)`) and the daemon client's socket connections keep the Node.js event loop alive. Adding `process.exit(0)` after `showHelp()` matches the pattern used by other commands (e.g., `init`) that already handle this correctly.
3 days ago by AgentEnder
Canceled
34506
253782ef fix(core): exit process after showing help for known commands When running `nx show project --help` or similar commands that hit the help path in init-local.ts, the process would hang indefinitely. This is because yargs' built-in help is disabled (`.help(false)`) and the daemon client's socket connections keep the Node.js event loop alive. Adding `process.exit(0)` after `showHelp()` matches the pattern used by other commands (e.g., `init`) that already handle this correctly.
3 days ago by AgentEnder