-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
zapgrpc upgrade for grpclog.LoggerV2 #534
Comments
I just ran into this as well. |
@geeknoid if you need an immediate workaround you can use: [[constraint]]
name = "go.uber.org/zap"
branch = "grpclog-v2"
source = "github.com/frankgreco/zap" |
Thanks.
…On Wed, Dec 20, 2017 at 1:02 PM, Frank B Greco Jr ***@***.***> wrote:
@geeknoid <https://github.com/geeknoid> if you need an immediate
workaround you can use:
[[constraint]]
name = "go.uber.org/zap"
branch = "grpclog-v2"
source = "github.com/frankgreco/zap"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#534 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AVucHfxjHH2o2BsKbgmbnni3mTNRO8Yxks5tCXX7gaJpZM4Qz_Wq>
.
|
Hi @frankgreco , do you have any estimation time when the feature will be merged ? Thanks |
@roytman This PR was held up because I still needed to implement |
Many thanks for the update and of course for your work. |
Gentle poke. |
This ended up adding significant API surface to the Sugar logger, which I don't think we want to do. This wrapper can sit outside of zap, and in future we may provide the gRPC adapter in a sub-package rather than extending the Sugar logger's API to support the gRPC logger. |
But #881 does not add any methods to the Sugar logger? In fact, it does not touch any files outside of |
You're completely right, it already is in a subpackage, so it's fine to extend it. Reviewed #881 |
gRPC has an updated [logger interface][1] that the v1 API has been deprecated in favor of. [1]: https://pkg.go.dev/google.golang.org/grpc/grpclog#LoggerV2 This adds support for it to the existing gRPC adapter in Zap. Fixes #534 Closes #538 Co-authored-by: Prashant Varanasi <github@prashantv.com> Co-authored-by: Abhinav Gupta <abg@uber.com>
gRPC has an updated [logger interface][1] that the v1 API has been deprecated in favor of. [1]: https://pkg.go.dev/google.golang.org/grpc/grpclog#LoggerV2 This adds support for it to the existing gRPC adapter in Zap. Fixes #534 Closes #538 Co-authored-by: Prashant Varanasi <github@prashantv.com> Co-authored-by: Abhinav Gupta <abg@uber.com>
gRPC has an updated [logger interface][1] that the v1 API has been deprecated in favor of. [1]: https://pkg.go.dev/google.golang.org/grpc/grpclog#LoggerV2 This adds support for it to the existing gRPC adapter in Zap. Fixes uber-go#534 Closes uber-go#538 Co-authored-by: Prashant Varanasi <github@prashantv.com> Co-authored-by: Abhinav Gupta <abg@uber.com>
The latest gRPC releases support an expanded logger interface (https://github.com/grpc/grpc-go/blob/master/grpclog/loggerv2.go). It'd be great if zap's gRPC support was updated accordingly.
Thanks.
The text was updated successfully, but these errors were encountered: