-
Notifications
You must be signed in to change notification settings - Fork 918
Please use DEBUG_WOLFSSL not WOLFSSL_DEBUG #9054
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
Conversation
|
Jenkins retest this please. History lost |
JacobBarthelmeh
left a comment
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.
Some good changes where WOLFSSL_DEBUG was corrected to DEBUG_WOLFSSL. I don't think we should start error'ing though when encountering WOLFSSL_DEBUG.
11b5dca to
e0bde96
Compare
e0bde96 to
7c9327a
Compare
|
Refresh from upstream for #9061 fix, squashed commits & force-pushed to retest. This forced logic removed per code review, consider spell check instead: |
|
Jenkins retest this please For AgentOfflineException: Unable to create live FilePath for wolf-linux-cloud-node-[n]; wolf-linux-cloud-node-[n]was marked offline: Connection was broken |
Description
I've made this mistake myself on more that one occasion:
WOLFSSL_DEBUGvsDEBUG_WOLFSSL.The correct macro for wolfSSL debugging is
DEBUG_WOLFSSL.I've made some corrections that already exist in the codebase and added this to
settings.hto avoid future mistakes:As for the pattern:
It is best to use WOLFSSL_MSG from
wolfssl/wolfcrypt/logging.h.Fixes zd#
Testing
Manual testing only
Checklist