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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Output in automatic provisioning like 0.10 #7137
Comments
You can also increase verbosity to debug level:
And you can swap the TUI with the older output:
So it boils down to not wanting to install the \cc @vito |
Running with
|
I wasn't aware there was a difference, thanks. Can you see if this helps (
|
Does not make a difference, see output:
|
\cc @vito |
Ah. I've just realized why this is. This is a result of the specific way we do I think we need a bit of a refactor here, I'm going to look at this at some point soon, since the way that the logs are done with this make some of our tests produce enormous quantities of output, and it would be nice to avoid that. |
What are you trying to do?
Dagger 0.11 made changes to the console output which I believe to be a large downgrade.
What I used to do:
I would run my pipeline without the dagger binary, simply running
python main.py
. This would print the output from the container as well as my program output (i.e., calls tologger.info()
) to the console in real time. Once the process was complete, all the container logs + my own would still be clearly visible for reference.I found this approach to be the best for 2 reasons:
dagger-io
was installed in my Python virtual environment.The Downgrade
With dagger 0.11, simply running
python main.py
produces only the program output and none from the containerised process itself.The best alternative is to run
dagger run -vvv python main.py
, but I find that to be significantly worse than runningpython main.py
with dagger 0.10 due to the following points:Why is this important to you?
Seeing the output of a program is incredibly helpful for pretty much every part of the development process.
How are you currently working around this?
I am not upgrading to dagger 0.11, and using 0.10 instead.
The text was updated successfully, but these errors were encountered: