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 "writing output failed" error of non ASCII output on Windows #2633

Merged
merged 1 commit into from
Jun 28, 2023

Conversation

itchyny
Copy link
Contributor

@itchyny itchyny commented Jun 28, 2023

This PR closes #1671 PR which is outdated created by a deleted user, also fixes the code I wrote in #2632 where I copied from the potentially problematic code on Windows.

@itchyny itchyny added the bug label Jun 28, 2023
@itchyny itchyny added this to the 1.7 release milestone Jun 28, 2023
Copy link
Member

@wader wader left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But a bit confused how the fwrite caused the "No such file or directory" error in #1671 :)

Tricky to add some kind of test for this? would require conditionally only on windows test?

@itchyny
Copy link
Contributor Author

itchyny commented Jun 28, 2023

That bug is reproducible only on TTY, so it looks difficult to add tests.

@wader
Copy link
Member

wader commented Jun 28, 2023

@itchyny yeap that is a mess to test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants