-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Fixes log level for got supported group message #8207
Fixes log level for got supported group message #8207
Conversation
4ed27a2
to
d9f2280
Compare
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.
LGTM
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.
Looks good to me except that it should have a changelog entry since this is a reported bug.
I've checked that this debug line isn't present in 2.28 (it was added in 3.2), so no backport is needed.
Signed-off-by: mcagriaksoy <[email protected]>
Please don't include merge commits in pull requests unless necessary to resolve a merge conflict with a complicated history, or a CI failure. They are time-consuming to review. |
998ad9c
to
cd7e82d
Compare
0329593
to
7f84471
Compare
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.
LGTM
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.
LGTM
ChangeLog.d/fix-log-level-msg.txt
Outdated
@@ -0,0 +1,2 @@ | |||
Bugfix | |||
* Fix log level for the got supported group message. Fixes #6765 |
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.
The comment in the PR is much more useful than this, so could you change this to something like the following (also note the final period/full stop).
* Fix an incorrect log level that was causing excessive messages during
DTLS handshakes. Fixes #6765.
bf351dd
7f84471
to
bf351dd
Compare
Signed-off-by: mcagriaksoy <[email protected]>
bf351dd
to
920ee02
Compare
Description
This is the copy PR of the previous #7314
somehow I cannot re-open that.
This PR resolve #6765 issue. During one successful DTLS handshake, user seeing many message caused by wrong log level.
PR checklist
Please tick as appropriate and edit the reasons (e.g.: "backport: not needed because this is a new feature")
Notes for the submitter
Please refer to the contributing guidelines, especially the
checklist for PR contributors.