-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Handling regular signals sent to cargo-shuttle on Windows #872
Comments
ping buddy @piewhat |
Hey @pedromfedricci and @piewhat, are you still interested in this issue, or should I open it up again? |
/bounty $50 |
|
I went through the SIG* handlers for UNIX, and able to reproduce the issue on windows. Stabbing into it. |
💡 @Shubham8287 submitted a pull request that claims the bounty. You can visit your org dashboard to reward. |
🎉🎈 @Shubham8287 has been awarded $50! 🎈🎊 |
Describe the feature
We must handle gracefully when the local deployment of user services is interrupted by sending a signal to the cargo-shuttle project, or any of the user’s services panic, or the cargo-shuttle process is gracefully killed. At this moment we cover some of these in cargo-shuttle for *unix systems (SIGINT, SIGTERM, and user service panic). We must do similar handling for regular signals sent to cargo-shuttle process on Windows.
Requirements:
Suggestion or Example of how the feature would be used
No response
Duplicate declaration
The text was updated successfully, but these errors were encountered: