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

fix: don't abort on first encountered error when resetting Windows console #67

Merged
merged 1 commit into from
Mar 7, 2023

Conversation

muesli
Copy link
Contributor

@muesli muesli commented Oct 21, 2022

When resetting the Windows console modes, we must not abort on the first encountered error, otherwise we might leave the console in an unexpected state.

This is easily reproducible by calling SetRaw while stdout is redirected: Reset will abort restoring console modes after failing to reset stdout, which leaves stderr in its raw state.

…nsole

When resetting the Windows console modes, we must not abort on the
first encountered error, otherwise we might leave the console in an
unexpected state.

This is easily reproducible by calling SetRaw while stdout is
redirected: Reset will abort restoring console modes after failing
to reset stdout, which leaves stderr in its raw state.

Signed-off-by: Christian Muehlhaeuser <muesli@gmail.com>
@kzys
Copy link
Member

kzys commented Mar 7, 2023

@kevpar @dcantah PTAL

@kzys kzys merged commit 56fb9de into containerd:main Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

3 participants