Describe the Issue
Keyboard Interrupt / Ctrl+C isn't being caught/acknowledged when an ImageAcquirer is in existence. Interesting that quit() instead of Ctrl+C works for me.
Sample Code
I can show a piece of code that demonstrates the reported phenomenon:
[x] Yes
[ ] No
If yes, please provide a sample code:
Stops on KeyboardInterrupt once "waiting!" starts printing:
import time
from harvesters.core import Harvester
if __name__ == "__main__":
h = Harvester()
h.add_file("") # insert producer path here
h.update()
# with h.create() as ia:
# pass
while True:
print("waiting!")
time.sleep(1)
Doesn't stop on KeyboardInterrupt once "waiting!" starts printing:
import time
from harvesters.core import Harvester
if __name__ == "__main__":
h = Harvester()
h.add_file("") # insert producer path here
h.update()
with h.create() as ia:
pass
while True:
print("waiting!")
time.sleep(1)
Expected Behavior
Configuration
OS: Ubuntu 22.04
Python: 3.8
Harvester: 1.4.3
Reproducibility
This phenomenon can be stably reproduced:
[x] Yes
[ ] No.
If applicable, please provide your observation about the reproducibility.
I'm unsure if this happens with other cameras (or producers to be honest).
Describe the Issue Keyboard Interrupt / Ctrl+C isn't being caught/acknowledged when an
ImageAcquirer
is in existence. Interesting thatquit()
instead of Ctrl+C works for me.Sample Code I can show a piece of code that demonstrates the reported phenomenon:
If yes, please provide a sample code:
Stops on KeyboardInterrupt once
"waiting!"
starts printing:Doesn't stop on KeyboardInterrupt once
"waiting!"
starts printing:Expected Behavior
Configuration
Reproducibility
This phenomenon can be stably reproduced:
If applicable, please provide your observation about the reproducibility. I'm unsure if this happens with other cameras (or producers to be honest).
Actions You Have Taken