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

Bl should not stomp verbosity #8857

Closed
wants to merge 4 commits into from

Conversation

Forgind
Copy link
Member

@Forgind Forgind commented Jun 7, 2023

Fixes #4543

The binary logger, when turned on, sets the verbosity to diagnostic. This should not be true if the user explicitly requests another verbosity.

This is based on #8805, but it was noticed that that disabled logging task parameters in the build. This is the same changes but reenables that if the BinaryLogger is present.

The binary logger, when turned on, sets the verbosity to diagnostic. This should not be true if the user explicitly requests another verbosity.
Copy link
Member

@JanKrivanek JanKrivanek left a comment

Choose a reason for hiding this comment

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

Looks good.
Can we add some test that would catch the missing parameters case?

Regardless of verbosity
@Forgind Forgind force-pushed the bl-should-not-stomp-verbosity branch from 31e1875 to adce0f2 Compare June 15, 2023 23:26
@Forgind
Copy link
Member Author

Forgind commented Oct 6, 2023

I intended to get back around to this but haven't for a while. Closing. If you think it's actually ready to go, and I should just resolve the conflict, let me know, and I can.

@Forgind Forgind closed this Oct 6, 2023
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.

Binary logger should respect verbosity
2 participants