Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.6k
[Console] avoid multiple new line when message already ends with a new line in section output#51378
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
[Console] avoid multiple new line when message already ends with a new line in section output#51378
Uh oh!
There was an error while loading.Please reload this page.
Conversation
7b73257
tob8c2675
CompareUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
b8c2675
to1f20f72
CompareThank you@joelwurtz. |
[](https://renovatebot.com)This PR contains the following updates:| Package | Type | Update | Change ||---|---|---|---|| [symfony/console](https://symfony.com)([source](https://togithub.com/symfony/console)) | require | patch |`6.3.2` -> `6.3.4` || [symfony/process](https://symfony.com)([source](https://togithub.com/symfony/process)) | require | patch |`6.3.2` -> `6.3.4` |---### Release Notes<details><summary>symfony/console (symfony/console)</summary>### [`v6.3.4`](https://togithub.com/symfony/console/releases/tag/v6.3.4)[CompareSource](https://togithub.com/symfony/console/compare/v6.3.2...v6.3.4)**Changelog**(symfony/console@v6.3.3...v6.3.4)- bug[symfony/symfony#51378](https://togithub.com/symfony/symfony/issues/51378)\[Console] avoid multiple new line when message already ends with a newline in section output([@​joelwurtz](https://togithub.com/joelwurtz))- bug[symfony/symfony#51223](https://togithub.com/symfony/symfony/issues/51223)\[Console] Fix linewraps in `OutputFormatter` (@​maxbeckers)- bug[symfony/symfony#51355](https://togithub.com/symfony/symfony/issues/51355)\[Console] fix section output when multiples section with max height([@​joelwurtz](https://togithub.com/joelwurtz))</details><details><summary>symfony/process (symfony/process)</summary>###[`v6.3.4`](https://togithub.com/symfony/process/compare/v6.3.2...v6.3.4)[CompareSource](https://togithub.com/symfony/process/compare/v6.3.2...v6.3.4)</details>---### Configuration📅 **Schedule**: Branch creation - At any time (no schedule defined),Automerge - At any time (no schedule defined).🚦 **Automerge**: Enabled.♻ **Rebasing**: Whenever PR becomes conflicted, or you tick therebase/retry checkbox.🔕 **Ignore**: Close this PR and you won't be reminded about theseupdates again.---- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, checkthis box---This PR has been generated by [MendRenovate](https://www.mend.io/free-developer-tools/renovate/). Viewrepository job log[here](https://developer.mend.io/github/Lendable/composer-license-checker).<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNi41Ni4wIiwidXBkYXRlZEluVmVyIjoiMzYuNTYuMCIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
😢 This broke our project, which uses progress bars to build a checklist-style output. It results in too many lines being cleared when the progress bar advances:https://github.com/acquia/cli/issues/1620 I'd appreciate your input, as it's not obvious to me why it broke. |
@danepowell Please consider submitting a new issue on this repo so that it's properly tracked |
I opened#52446 |
Uh oh!
There was an error while loading.Please reload this page.
When we write to the section with a new line in the message it ends up adding a double new line, it can be easily seen when we set a section as a console handler for the logs, each line of log will have a double new line ending adding a lot of noise.
I began to fix the implementation to correctly handle this case, but with all the logic of the max height and other stuff it appears to be way more complicated.
Simulating this case by removing the new line at the end of the message and recalling the write function with the newline parameter to true was way easier and avoid too many headcache when looking at the code.
Shouldfix#50382