You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tool want to display a progress bar and the latest target being compiled prettily to the terminal. And it does that. However for non terminal type stdout/stderr (IIRC checked via isatty and GetConsoleScreenBufferInfo), the output is a bit of a mess. For instance, via Gnu parallel, invoking parallel et build -c ::: host_profile_arm64 android_profile_arm64 will dump a whole mess of text that is hard to parse. The same happens when the build system is invoked via editor build system integration.
An instance of the text output:
The text was updated successfully, but these errors were encountered:
I don't know if #147903 is tracking a flag that explicitly opts out of pretty printing of if this is just a straight up duplicate. But, if its a flag, we should flip default its value to isatty. cc @matanlurey
chinmaygarde
changed the title
[et] The tools doesn't handle non-terminal type stdout and stderr correctly.
[et] The tool doesn't handle non-terminal type stdout and stderr correctly.
May 7, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
The tool want to display a progress bar and the latest target being compiled prettily to the terminal. And it does that. However for non terminal type stdout/stderr (IIRC checked via
isatty
andGetConsoleScreenBufferInfo
), the output is a bit of a mess. For instance, via Gnu parallel, invokingparallel et build -c ::: host_profile_arm64 android_profile_arm64
will dump a whole mess of text that is hard to parse. The same happens when the build system is invoked via editor build system integration.An instance of the text output:
The text was updated successfully, but these errors were encountered: