Skip to content
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

Revert "Enable 'quiet: true' in condarc" #220

Merged
merged 2 commits into from
Jan 6, 2025

Conversation

bdice
Copy link
Contributor

@bdice bdice commented Dec 23, 2024

Reverts #217.

It seems like we have lost some useful information from conda, and Python exception names are no longer being printed. This makes rapids-conda-retry ineffective. @pentschev and I suspect the change to quiet mode may be the root cause. We would like to try reverting it to see if this changes.

We may also need to do something to make conda stop printing all the extra newlines in progress bars that led to #217 in the first place…

@bdice bdice requested a review from a team as a code owner December 23, 2024 15:55
@bdice bdice requested review from msarahan and removed request for a team December 23, 2024 15:55
@jameslamb jameslamb requested review from jameslamb and removed request for msarahan December 23, 2024 15:55
Copy link
Member

@pentschev pentschev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @bdice !

@bdice bdice merged commit 8312f41 into main Jan 6, 2025
407 checks passed
@jakirkham jakirkham deleted the revert-217-having-fewer-log-lines-is-golden branch January 16, 2025 17:32
@jakirkham
Copy link
Member

Could you please share a bit more what information is lost?

Some examples would be instructive

@bdice
Copy link
Contributor Author

bdice commented Jan 16, 2025

The exact problem is that when we enable quiet mode, Python exception names are no longer being printed. This makes rapids-conda-retry ineffective, as it depends on parsing logs for exception names to decide whether to retry.

@bdice
Copy link
Contributor Author

bdice commented Jan 16, 2025

Ah, there is a better continuation of this discussion in #228. Let’s continue there.

@jakirkham
Copy link
Member

Please feel free to share some examples in that thread. Links to logs are ok. Just need something with more detail

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants