You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CTRL+C any Nx running task since upgrading to Nx 17 and I'm seeing this error in the console:
ELIFECYCLE Command failed with exit code 128.
It also happens in Nx 18.
So I think they've refactored how tasks & processes are managed, and somehow exiting the task runner more aggressively.
This appears to be affecting the Firebase serve executor, since it no longer gets the SIGINT and just bails out, which means the Firebase emulator no longer gets opportunity to shutdown.
Anyone else seeing this?
The text was updated successfully, but these errors were encountered:
simondotm
changed the title
Nx 17.x+ terminates tasks with ELIFECYCLE Command failed with exit code 128.
Nx 17+ terminates tasks with ELIFECYCLE Command failed with exit code 128.May 1, 2024
This was happening in Node 18, and I tried updating to Node 20 based on a random comment elsewhere, but no difference (yet).
I'm short on ideas for how to fix this, because we have to invoke the custom serve executor from nx task runner, even when spinning up our own process in there, it gets killed without firebase CLI command getting the SIGINT it needs to shutdown the emulator cleanly.
Ideas are very welcome, since it's not great for workflow atm.
CTRL+C any Nx running task since upgrading to Nx 17 and I'm seeing this error in the console:
It also happens in Nx 18.
So I think they've refactored how tasks & processes are managed, and somehow exiting the task runner more aggressively.
This appears to be affecting the Firebase
serve
executor, since it no longer gets the SIGINT and just bails out, which means the Firebase emulator no longer gets opportunity to shutdown.Anyone else seeing this?
The text was updated successfully, but these errors were encountered: