How does the dispatcher know when to exit? #66
-
While developing |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
If I were implementing this myself, I would try to wake up the dispatcher in response to a pipe event from the client (over the IPC/abstract socket) and then make a decision at that point. Is that what happens? If so, do you think in those rare cases, the dispatcher somehow sleeps through the pipe event? (And if that is what happens, what if the dispatcher wakes itself up every ~5 minutes up to check the pipe proactively? I know this gets uncomfortably close to polling and heartbeating, but all this would need is a way to make sure these dispatcher processes do not run forever. I am thinking about shared clusters like SLURM where hundreds of people share the same login nodes, those nodes keep running for months, and any downtime to clear things out is a major disruption.) |
Beta Was this translation helpful? Give feedback.
The very rare crashes would in my experience be due to
devtools
usage combined with updates to the compiled code innanonext
. If I am just making updates tomirai
I don’t experience any crashes – and I regularly install new versions without necessarily resetting daemons first. If there is a difference in experience, then it might be a MacOS thing assuming you are developing on that platform. I would certainly not expect end users to experience any crashes or dispatcher not exiting.As to how dispatcher exits: