-
Notifications
You must be signed in to change notification settings - Fork 496
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
no associated item named GRPC_STATUS
found for struct tonic::Status
#2165
Comments
I had the same issue, pinning tonic version to 0.12.3 fixes the issue |
Thank you for the workaround. By pinning the tonic version to 0.12.3, the error was resolved. |
Should force the bump to tonic 0.12.3 in the opentelemetry-proto instead of working around this downstream. |
@djc Can you assist with this? Resolving these dependency conflicts while keeping opentelemetry-sdk on Rust 1.65.0 and opentelemetry-proto on Rust 1.71.1 could be bit challenging, else I can fix it later this week. |
For those who have a Cargo.lock file in their Git repository for reproducible. it takes a simple cargo update command to fix the issue. Similarly In my case, the issue was due to the fact that my Cargo.lock still holds on to an older version of tonic crate. cargo update tonic This has upgraded tonic crate to the latest stable version 0.12.3 and this compilation error just gone. But, there are still other errors related to Traits exposed by the SDK for which I just opened another issue: #2167 |
Yes, the issue is only for the environments where tonic version is somehow locked/cached to the older version. Or else, where one of it's dependency has tonic pinned to v1.12.2 or lower. Doesn't necessarily require a patch release for the fix. |
Confirmed that |
Related Problems?
No response
Describe the solution you'd like:
The compilation succeeds.
Considered Alternatives
No response
Additional Context
I would like to report a compilation failure with opentelemetry-proto-0.26.0.
`cargo tree` output
The text was updated successfully, but these errors were encountered: