-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Log ending round state @ during resolver debug #12264
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
Log ending round state @ during resolver debug #12264
Conversation
(not sure if this is worthy of a change note) |
This is not a typo -- encoding the entire state into the message was deemed not useful and causes a lot of noise when extremely long resolves take place. |
@pradyunsg should it be logged with DEBUG level instead of INFO, then? It's probably useful in some cases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DEBUG or VERBOSE would make sense. I think I prefer DEBUG slightly, the state can be very verbose.
DEBUG or VERBOSE would make sense (maybe DEBUG)
DEBUG works. :) |
62fae81
to
8b63fe6
Compare
@pradyunsg do you think this needs a change note? |
Personally I think this is fine, an additional log shouldn’t break things (you’re doing somethign wrong if it does…) |
@pradyunsg it should be easy to merge this? |
This change corrects a tiny-little mistake made in 9f318de that was causing the word "state" to be printed out in the log instead of the value of the `ending_round()`'s state` argument.
8b63fe6
to
ea5f26e
Compare
This change corrects a tiny-little mistake made in 9f318de that was causing the word "state" to be printed out in the log instead of the value of the
ending_round()
's state` argument.