Repository navigation
Unsupported signal 2 delivered #28
Description
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 run replay-recordings ls I get:
{
"id": 663276012,
"createTime": "Thu Oct 21 2021 16:39:05 GMT-0400 (Eastern Daylight Time)",
"runtime": "node",
"metadata": {
"argv": [
"./node_modules/.bin/ts-node",
"scripts/dev-backfill.ts",
]
},
"status": "unusable",
"path": "/Users/dan/.replay/recording-663276012.dat",
"unusableReason": "Recording invalidated: Unsupported signal 2 delivered"
}
Activity
nathggns commentedon May 26, 2022
I have the same issue.
gideonred commentedon May 26, 2022
@bhackett1024 do we have plans to support breaking out of infinite loops during node recordings?
bhackett1024 commentedon May 27, 2022
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.
gideonred commentedon May 27, 2022
@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).
gideonred commentedon Jun 9, 2022
This ticket has been moved to RUN-309