Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
RSDK-9150 - Client log interceptor should not use zap.Logger #375
RSDK-9150 - Client log interceptor should not use zap.Logger #375
Changes from 1 commit
380000c
df59cdf
5c58e22
735945f
48190b0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 69 in logger_test.go
Check failure on line 88 in logger_test.go
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.
Why is this necessary? I would expect if the level were not enabled, then the calls to
logger.Debuw
/logger.Infow
/etc... would early return. Are we not observing that?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.
ya this is probably unnecessary, let me check. I was thinking too much about replicating the functionality of grpc_zap.DefaultMessageProducer, which also does a check before logging
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.
Cool, definitely speak up if removing this is problematic.
If removing is not problematic, then we can cascade and delete the interface change that added
Level
and the dummy implementations for the testing 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.
updated to remove
Check failure on line 352 in rpc/wrtc_client_channel.go
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.
this is pretty ugly, but the
Write()
methods differ between zap loggers and rdk loggers so I could either write another conversion method likeAddFieldsToLogger
or do this and this is easierThere 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.
note: rdk loggers' WithFields() do not play nicely with zapcore.Field at all. which probably means that zap loggers will not play nicely with
AddFieldsToLogger
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.
Thanks for filing that ticket; sounds like zap loggers will almost certainly not play nicely with
AddFieldsToLogger
. But, from the sample "after changes" output you put in the PR description, the added fields do seem to be getting added. Is that right?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.
yep, but the way they're getting passed in now is different - no longer a list of zap.Fields