Keyboard interrupts not working properly with run

[qherreros]

• Solus OS
• Poetry 0.12.10

Hello,

I've been playing around with poetry and crossbar.io (a websocket server). Whenever i run "poetry run crossbar start", the CTRL-C interrupts my server in a brutal way (unclean shutdown). If i do the same thing after a "poetry shell" then "crossbar start", my CTRL-C works as intended.

I'm not fluent in SIGTERM but there is something strange happening with poetry run.

Thanks anyway for this amazing tool.

[sybrenstuvel]

I can confirm this with Poetry 0.12.15 on Ubuntu 18.04 LTS. Running poetry run py.test and then interrupting with Ctrl+C does not send the interrupt to py.test, but rather instantly kills the process.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[sybrenstuvel]

This is still an issue in Poetry 0.12.17.

[dfontenot]

This issue is still present in 1.1.12. Running into this issue with a dockerized Python codebase that uses Poetry. Am using a virtualenv within the container due to this issue #3139

Are there any other workarounds? I'm relying on the signals to reach the Python script itself so that it can do the proper cleanup.

[neersighted]

I'm unable to reproduce this on 1.2.1 -- if you can consistently reproduce it, please post instructions here

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.