Skip to content
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

Killing process #9

Open
alexandreday opened this issue Jun 28, 2018 · 2 comments
Open

Killing process #9

alexandreday opened this issue Jun 28, 2018 · 2 comments

Comments

@alexandreday
Copy link
Contributor

When running fitsne Python wrapper, it is common that you want to kill the process (say you screwed a parameter, etc.). However, while you can use CTRL-C to send a kill signal, this won't actually kill the c C-code that's running. Is there a way to fix this ? It seems important that you should be able to terminate the code even though it is just a wrapper.

@linqiaozhi
Copy link
Member

This is a great question. I frequently struggle with this in other packages as well: when calling C code in R, it does not seem to check for signals (e.g. ctrl-c). It looks like this might be a solution.

I will leave this open and add an enhancement label, as I think this would be a great feature. Perhaps at every iteration it can check signals.

@alexandreday
Copy link
Contributor Author

Great, yes, I'll try to see if there's a simple fix to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants