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
On Windows systems, the runner cannot be gracefully shutdown, which leaves the SyncManager process behind.
Desired solution
A new message type (e.g. shutdown) that tells the runner to gracefully exit as soon as possible.
Possible alternatives (optional)
Using SIGINT, which does not exist on Windows. There is a CtrlBreak feature which could be used, but as I understood is not part of the Windows API and thus is hard to use in the extension. It is currently used when Ctrl+C is pressed and the process is run in a console window.
Just kill the whole process tree when the runner should be shut down.
Screenshots (optional)
No response
Additional Context (optional)
Killing the process tree could still be used as a last resort, if after sending the shutdown message, a specific timeout expired and the process didn't shut down in time.
The text was updated successfully, but these errors were encountered:
Closes#24
### Summary of Changes
- added a shutdown message type that can be sent by the extension to
gracefully shut down the runner
- the sync child process should be shut down when sending a shutdown
message
---------
Co-authored-by: megalinter-bot <[email protected]>
Co-authored-by: Lars Reimann <[email protected]>
Is your feature request related to a problem?
On Windows systems, the runner cannot be gracefully shutdown, which leaves the
SyncManager
process behind.Desired solution
A new message type (e.g.
shutdown
) that tells the runner to gracefully exit as soon as possible.Possible alternatives (optional)
CtrlBreak
feature which could be used, but as I understood is not part of the Windows API and thus is hard to use in the extension. It is currently used when Ctrl+C is pressed and the process is run in a console window.Screenshots (optional)
No response
Additional Context (optional)
Killing the process tree could still be used as a last resort, if after sending the
shutdown
message, a specific timeout expired and the process didn't shut down in time.The text was updated successfully, but these errors were encountered: