Open jeffora opened 6 months ago
This issue has been automatically marked as stale because it hasn't had any activity for 6 months. Many things may have changed within this time. The issue may have already been fixed or it may not be relevant anymore. If at this point, this is still an issue, please respond with updated information. It will be closed in 21 days if no further activity occurs. Thanks for being a part of the Nx community! 🙏
Current Behavior
We have some build machines that run a portion of our CI process (on-premise Mac machines for running xcode / iOS builds). Our app is an ionic/cordova app in a monorepo with nx, so the build process on these machines runs nx tasks (via
npx nx run ...
). The repository is connected to nx cloud, however we are not callingstart-ci-run
or similar from these machines.We are seeing a behaviour on these machines that a heartbeat process is started from nx cloud, and it never exits. Individually this doesn't seem to be a big issue, but the process appears to be orphaned or become unresponsive, and over time we end up with hundreds of these processes running:
We have seen this grow up to 250 processes in a relatively short time (few hours), and they don't seem to have any impact (i.e. killing them all doesn't cause anything to fail).
Is there a way to disable this process or ensure it properly cleans itself up? I'm not sure where to start in diagnosing why they are not exiting.
Expected Behavior
The heartbeat process should automatically exit, or not start in the first place, if it is not needed.
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response