-
Notifications
You must be signed in to change notification settings - Fork 27
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
Restore CTRL-C handling by setting new flag in libmamba #340
Conversation
See for the proper fix upstream too: mamba-org/mamba#2946 |
Haven't figured out the correct windows signal incantation yet. |
…amba-solver into pthread-sigmask-ctrl-c
libmamba 1.5.3 is out already so we might not need the workaround after all. Let's rerun things. |
Is that "skip signal handling" true, or false by default? |
Co-authored-by: jaimergp <[email protected]>
Linux and macOS are failing for unrelated reasons (fixed in #347). Windows tests fail because (I hope) the test is not sending the right signal to the subprocess. Need to debug locally. |
…nda-libmamba-solver into pthread-sigmask-ctrl-c
Co-authored-by: Jannis Leidel <[email protected]>
Seems to be working now! I can't test Windows locally but I'm assuming the tests are fine. |
Ran the tests on Windows 11 again and confirmed manually the working of CTRL+C to cancel both collecting repodata and solving. |
Thanks all! 🙏 |
Description
mamba-org/mamba#1594 is the issue in Mamba. Possibly for the solver only we could have a second boolean on context init that skipped mamba's pthread call entirely.
Fix #337
Checklist - did you ...
news
directory (using the template) for the next release's release notes?