-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Console.Unix: fix, make CancelKeyPress work when input is redirected. (…
…#52891) * Console.Unix: fix, make SIGINT work when input is redirected. * Fix misplaced s_initialized assignment
- Loading branch information
Showing
2 changed files
with
36 additions
and
33 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ff5b9e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stephentoub are there any planes to backport this (i.e. #52891) to the 5.0 branch? After closing #51221 5.0.7 and 5.0.8 have been release, but unfortunately they do not include the fix. Any chance for 5.0.9?
(sorry for commenting here, but the original issue as well as the PR are locked for comments now. Please let me know when there are preferred alternatives)
ff5b9e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc: @jeffhandley
ff5b9e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jbaehr If you have a need for the fix to be backported, could you file a new issue to express that need please? To justify backporting it, we would need to understand how the issue is affecting you against 5.0 and what your timeline would be for updating to 6.0 once it's released. Additionally, we would benefit from getting validation from you that this fix is proven to address the issue for you.
Thanks!