#How are people handling the developer
1 messages · Page 1 of 1 (latest)
We have a custom action to call dagger, which defaults to --progress dots. If the user re-runs their workflow with debug enabled, then we add the --progess plain -vvv
Something along these lines:
dagger ${{ runner.debug && '--progress plain -vv' || inputs.dagger-flags }}
So far, engineers have liked much more the --progress dots and is easier to read than any other dagger output (which is too verbose and too in-depth of what's going on)
Yeah, that is actually how we have been running for a while but this hides any errors from being displauyed at the end and the developer will have to go up and find the error amongst thousands of lines of dagger output.
Errors are typically bubbled up closer to the end of the output. @oak zealot did a lot of work to make the TUI do that. I'm curious why you have to scroll 1000s of lines to see errors. (this is with any --progress flag)
I think but am not totally sure the dots format should also print the report at the end 🤔 (if not that would be an easy change)