hi there ! I'm finding the dagger logs

[hidden sun]

👋 in non-tty outputs the only flag you can use to suppress the logs is the -s one. That will suprress all of them.

I guess we could implement -q in the same way -v works for the plain mode. I guess the challenge there will be bikeshedding the right verbosity level . Happy to chat about in a GH issue if you're ok with opening it

[uncut robin]

Hi @hidden sun thanks for your answer. would --silent report any error still ?

i'm happy with silent in a non-error scenario ( since my function returns (string, error) and i can still see its output )

[hidden sun]

yes, errors will still be displayed via stderr

but it'll be hard to troubelshoot without Dagger Cloud or the standard output

[uncut robin]

yeah i might have to set up dagger cloud ! Thanks @hidden sun appreciate the help

[hidden sun]

Sure, np. Give Dagger Cloud a try, it's free for a single user and super helpful to visualize your pipelines

[uncut robin]

yeah it's awesome. was using it for local traces. gonna set it up for my CI now. Do you know if i can set up the dagger cloud token at the engine level ? ( as opposed to the cli side ) ?

[velvet valley]

I'd have to find them but I believe there are several issues opened in the dagger repo regarding improving the verbosity for both TUI and non-tty.

[acoustic rose]

I find the cloud analysis helpful.

The only thing I could want from it is a mixing of event entries at a timeline like the plain output.