-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Fix lint commands frozen on empty stdin #33523
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
Conversation
8daae93
to
06702ed
Compare
The fact it works is relying on a race condition. Don't be fooled. For 4.4 only, master shouldn't rely on ftell() |
Sure, but it's a behavior change which might give false positives in a CI. Take e.g: cat unexisting | bin/console lint:yaml On 4.3 the output is an error message and exit code is 1. On 4.4-dev it succeeds with code 0. |
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.
Oh I thought you submitted that again master. For 4.4 it works for me!
5f1ac9d
to
6472304
Compare
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.
Much better imo, thanks!
Thank you @chalasr. |
This PR was merged into the 4.4 branch. Discussion ---------- Fix lint commands frozen on empty stdin | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | - | License | MIT | Doc PR | - Running e.g. `lint:yaml -` with no piped content makes the command hangs currently, this makes it fail instead. Also fixes the command help which we forgot to update Commits ------- b60e0c1 Fix lint commands frozen on empty stdin
Running e.g.
lint:yaml -
with no piped content makes the command hangs currently, this makes it fail instead. Also fixes the command help which we forgot to update