Open
Description
Description
It was observed that the server stop functionality during a KeyboardInterrupt
in unresponsive. Ideally, stop functionality should work in both of the following scenarios (currently not the case):
- Scenario 1:
start server -> stop server
- Scenario 2:
start server -> start client -> stop server
Reproduce
An example scenario can be reproduced locally by following the steps below:
python3 s2s_pipeline.py --recv_host 0.0.0.0 --send_host 0.0.0.0 # wait for server to start..
kill -2 <server_PID> # send KeyboardInterrupt signal to server
# server does not stop
This bug also relates to issue #139 . Implementation and a description of the fix can be found in pull request #138 .
Metadata
Metadata
Assignees
Labels
No labels