-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Problems interrupting pmap with Ctrl-C #6752
Comments
^C interrupts the currently executing task, which may be the last worker to block @JeffBezanson maybe InterruptException should be propagated to the root task, if the current task is in the uv_run scheduler? |
Bump. Would be nice to have a fix for this. Interrupting a long-running distributed task is pretty common. |
Bump. This is really annoying. |
Related (dupe?) #6283 |
@amitmurthy have recent refactorings improved the situation here at all? |
possibly fixed. i get the following error on OS X for the latest master, and sth similar on linux:
|
hold on. while on OS X it does return me to the command line, on linux it does not. rather, it keeps repeating the error message over and over. |
Unable to interrupt a pmap call with 2 or more workers
I added a debug statement to the sigint handler as well as the try-catch block in
pmap
. Looks like while the sigint handler is called everytime, only one the async tasks in pmap (for the first Ctrl-C) is being interrupted.Are all the tasks interrupted upon a Ctrl-C? If so, then it could be a REPL bug too.
If not, the "main" task, which in the case of pmap is the REPL waiting on a
@sync
block should be interrupted, instead of a@async
task chosen at random.The text was updated successfully, but these errors were encountered: