Group output option
See original GitHub issueWhen running things concurrently using --no-pretty
, the logs are mixed together from all the different processes.
You could have an option, or default to, to log out the outputs in groups. You’d have to wait for them to end of course and then just output the whole thing for each one as it ends.
Perhaps as --group-logs
, though tbh it’s a reasonable default.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Defining Output Groups - TechDocs - Broadcom Inc.
Output Groups are used to group similar Output Devices together into useful sets-they are basically a classification mechanism. Single Output ...
Read more >Creating and setting up outputs in File output groups
With File output groups, each asset that the service creates corresponds to one output, rather than one output group. Each asset contains all...
Read more >Option groups - cloup v2.0
The recommended way of defining option groups is through the option_group() ... "Output options", "This is a an optional description of the option...
Read more >Output Enable Group logic option - Intel
A logic option that assigns an output enable group number for the specified node. Turning on this option directs the Fitter to view...
Read more ><optgroup>: The Option Group element - MDN Web Docs
The name of the group of options, which the browser can use when labeling the options in the user interface. This attribute is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As mentioned before, for one off builds,
--pretty
already behaves as the proposed--group-logs
options. Once the build finished, a full (non truncated) logs is flushed to the terminal.I’ve also just released v3.4.1 which now properly adds the current package name to the
--no-pretty
output, for watching builds etc.Hope this helps!
@tshelburne thank you for clarifying. I actually have a very similar setup for another project, but the errors are pretty small in my case most of the time.
Unfortunately it’s pretty hard to make the truncation configurable. The reason for this is that I’m using terminal escape sequences to change the output. It’s not possible to change output beyond what’s visible on the screen. So you can’t use a screen buffer bigger than your terminals amount of rows.
The only way I can think of to make this happen, would be using an ncurses like interface as blessed, but this would be beyond the scope of
ultra
imho.