-
Notifications
You must be signed in to change notification settings - Fork 3
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
Unsupported signal 2 delivered #28
Comments
I have the same issue. |
@bhackett1024 do we have plans to support breaking out of infinite loops during node recordings? |
Not presently, but this could go on the roadmap if we want it fixed. Both infinite loops and infinite recursions can be handled, but both will require special handling / participation from the runtime being recorded. |
@ceceliacreates it might be worth calling out in the documents that in our Node recording you currently need to have code that actually finishes since we don't support SIGKILL-ing out of the Node processes (and having a usable recording). |
This ticket has been moved to RUN-309 |
I tried to record a recording of an infinite loop because I wanted to see how it was getting stuck. The only way to terminate my program was to send it a
SIGKILL
via ctrl+c. Unfortunately that seems to render the recording unusable. When I runreplay-recordings ls
I get:The text was updated successfully, but these errors were encountered: