Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIGBREAK signal from keyboard not propagated by Windows Terminal #6185

Closed
bozhodimitrov opened this issue May 25, 2020 · 2 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@bozhodimitrov
Copy link

bozhodimitrov commented May 25, 2020

Environment

Windows build number:
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable):
1.0.1401.0

PowerShell Core:
7.0.1

PowerShell: 
Name                           Value
----                           -----
PSVersion                      5.1.18362.752
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.752
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Steps to reproduce

  1. Open PowerShell or PowerShell Core in Windows Terminal
  2. Simulate blocking behavior with Python command:
    python -c "import time; import threading; t = threading.Thread(None, lambda: time.sleep(9999)); t.start(); t.join()"
  3. Press keyboard shortcut Ctrl+Break

Expected behavior

Terminated Python process

Actual behavior

Python process is still running

Additional notes:

I tried the same steps in pure PowerShell (powershell.exe)/PowerShell Core (pwsh.exe)/CMD (cmd.exe) - and the result is terminated Python process.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 25, 2020
@zadjii-msft
Copy link
Member

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #1119 for more discussion.

/dup #1119

@ghost
Copy link

ghost commented May 26, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed May 26, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 26, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants