You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, every process we start is on the same process group as the parent process, and that means a Ctrl-C in the terminal will cause a SIGINT to be sent to every process we start, but our parent process also has logic to detect a SIGINT and forward it to every child, so by default every child ends up receiving two SIGINTs, unless one adds a start_new_session=True item to open_in_process()s subprocess_kwargs` dict, like we do in trinity
As Piper suggested, though, we might want to have that as the default behaviour here
The text was updated successfully, but these errors were encountered:
Can we even go as far as detecting this property of the child process and disabling the SIGINT behavior in the cases where the child process gets it automatically?
Currently, every process we start is on the same process group as the parent process, and that means a
Ctrl-C
in the terminal will cause a SIGINT to be sent to every process we start, but our parent process also has logic to detect a SIGINT and forward it to every child, so by default every child ends up receiving two SIGINTs, unless one adds astart_new_session=True
item to open_in_process()s
subprocess_kwargs` dict, like we do in trinityAs Piper suggested, though, we might want to have that as the default behaviour here
The text was updated successfully, but these errors were encountered: