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.

Sign up for GitHub

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

Jump to bottom

Windows terminal pane is non-responsive after long idle git log #12828

Closed
scaramushe opened this issue Apr 5, 2022 · 2 comments
Closed

Windows terminal pane is non-responsive after long idle git log #12828

scaramushe opened this issue Apr 5, 2022 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.

Comments

@scaramushe
Copy link

scaramushe commented Apr 5, 2022 •
edited
Loading

Windows Terminal version

1.13.10734.0

Windows build number

10.0.22000.556

Other Software

git - git version 2.35.0.windows.1
profile is powershell, PSVersion 5.1.22000.282

Steps to reproduce

Working via RDP,
Opening a terminal pane with git repo,
Run git log and leave it "alive"
Return after a few hours and try to send any keyboard command in this pane

Expected Behavior

Response to the keyboard command

Actual Behavior

nothing - no keyboard command is received. Then pane next to it works fine.
Also mouse scrolling works as expected. Only keyboard input is the issue.
Recovery - Alt+Pause to exit the state
The issue is seen occasionally, not easily reproduced

After hitting this once, and recovering - got issue PowerShell/PSReadLine#3260
@scaramushe scaramushe added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Apr 5, 2022
@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 Apr 5, 2022
@scaramushe scaramushe mentioned this issue Apr 5, 2022
Closed
3 tasks
@zadjii-msft
Copy link
Member

Does this happen if you run the same git log command with a different shell? Command Prompt, or even a 7.x version of pwsh instead/?

This gives me vibes of #13386 and #12607, but at least in the latter case, there's not usually a way to break out of it

@ghost ghost added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Aug 1, 2022
@ghost
Copy link

ghost commented Aug 5, 2022

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost ghost closed this as completed Aug 9, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @scaramushe