In the terminal, type Ctrl-C to send an interrupt signal to the process (SIGINT).
Expected behavior:
Server should stop.
Actual behavior:
Nothing happens on first Ctrl-C.
Workaround:
Typing Ctrl-C a second time succeeds in stopping the server.
Notes: It seems like the process.once('SIGINT') handler in ./src/bin.ts must be capturing the first interrupt signal. For some reason though, it's not stopping the server from listening. Perhaps better debug logging would reveal which step is the problem.
Investigate to what degree this affects other methods of invoking the server, such as via ts-node and nodemon.
This appears to be fixed with the latest merge. The only appreciable change was the addition of logging. Why this would resolve the issue is unclear. Closing for now, but will reopen if the problem resurfaces.
Steps to reproduce:
npm install memorelay
.npx memorelay
.Ctrl-C
to send an interrupt signal to the process (SIGINT
).Expected behavior:
Actual behavior:
Ctrl-C
.Workaround:
Ctrl-C
a second time succeeds in stopping the server.Notes: It seems like the
process.once('SIGINT')
handler in./src/bin.ts
must be capturing the first interrupt signal. For some reason though, it's not stopping the server from listening. Perhaps better debug logging would reveal which step is the problem.Investigate to what degree this affects other methods of invoking the server, such as via
ts-node
andnodemon
.