Double Ctrl+C might leave the scan unsealed
Seen on ID10.
Running a loopscan and pressing Ctrl+C twice might leave the scan open (and Flint would then fail to properly display later scans).
This is relatively easy to reproduce.
Traceback (most recent call last):
File "/home/blissadm/local/bliss2.git/bliss/scanning/scan.py", line 1372, in wrapper
yield
File "/home/blissadm/local/bliss2.git/bliss/scanning/scan.py", line 1516, in _runctx_scan_data
self._scan_data.close()
File "/home/blissadm/local/bliss2.git/blissdata/blissdata/redis_engine/scan.py", line 56, in wrapper
return func(self, *args, **kwargs)
File "/home/blissadm/local/bliss2.git/blissdata/blissdata/redis_engine/scan.py", line 301, in close
self._close_stream_writers()
File "/home/blissadm/local/bliss2.git/blissdata/blissdata/redis_engine/scan.py", line 56, in wrapper
return func(self, *args, **kwargs)
File "/home/blissadm/local/bliss2.git/blissdata/blissdata/redis_engine/scan.py", line 271, in _close_stream_writers
stream_writer.seal()
File "/home/blissadm/local/bliss2.git/blissdata/blissdata/redis_engine/stream.py", line 96, in wrapper
return func(self, *args, **kwargs)
File "/home/blissadm/local/bliss2.git/blissdata/blissdata/redis_engine/stream.py", line 274, in seal
self._sink.stop()
File "/home/blissadm/local/bliss2.git/blissdata/blissdata/redis_engine/sink.py", line 72, in stop
self._cmd_queue.join()
...
KeyboardInterrupt
The scientist also suggested to used the Escape key to abort scans.