-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Emit export errors to stderr to prevent invalid output #4110
Conversation
An error in export could emit error messages to stdout, causing the requirements.txt output to stdout to be invalid. Fixes python-poetry#4109
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.
Thanks a lot 👍
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.
Some tests are failing in tests/console/commands/test_export.py
because the output is checked in stdout.
So you have to change tester.io.fetch_output()
to tester.io.fetch_error()
where needed.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Fixed! I noted that when I ran tests with |
@finswimmer This is a simple one, good to merge? Your requested change has been addressed, the remaining test failure looks unrelated ("connection reset by peer") |
@colindean: Could you please rebase your branch, to force the checks to run again? |
Checks are running now! |
…#4110) * Emit export errors to stderr to prevent invalid output An error in export could emit error messages to stdout, causing the requirements.txt output to stdout to be invalid. Fixes python-poetry#4109 * Looks at stderr for export tests
…#4110) * Emit export errors to stderr to prevent invalid output An error in export could emit error messages to stdout, causing the requirements.txt output to stdout to be invalid. Fixes python-poetry#4109 * Looks at stderr for export tests
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
An error in export could emit error messages to stdout, causing the requirements.txt output to stdout to be invalid.
Pull Request Check List
Resolves: #4109
N.b. I made this change in GitHub so I did not run tests or add tests to ensure the bad behavior doesn't happen.