-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Upgrade proto to 1.7.0 #13075
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
Upgrade proto to 1.7.0 #13075
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #13075 +/- ##
==========================================
- Coverage 91.60% 91.48% -0.13%
==========================================
Files 505 506 +1
Lines 28526 28557 +31
==========================================
- Hits 26132 26125 -7
- Misses 1880 1917 +37
- Partials 514 515 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Access to these lookup tables isn't really useful, as they only provide a slice of values, and we can't check which one is being used by the current profile. Also, with open-telemetry/opentelemetry-collector#13075, the lookup tables are moving out of the profile and into a new dictionary object. So as a first step to the proto migration, this removes access to the lookup tables for a profile. The replacement for this is #39681, which will give acces to the profile attributes, as we do with other signals and abstract away the lookup tables. --------- Co-authored-by: Edmo Vamerlatti Costa <11836452+edmocosta@users.noreply.github.com>
@@ -33,6 +34,8 @@ func TestMergeProfilesInvalidInput(t *testing.T) { | |||
} | |||
|
|||
func TestMergeSplitProfiles(t *testing.T) { | |||
t.Skip("merging of profiles has been temporarily disabled") |
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.
Should we return an error explicitly stating that, and add a test to check that we indeed return such an error?
Also, can we link to the issue tracking this (I guess the same as in my previous comment would suffice)
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 behavior is not to return an error, but not to perform any merging. We return the same slice of requests as we get.
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.
Is there any component on contrib using this merging functionality?
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.
There is no occurence of MergeSplit(
on contrib.
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 modulo documenting the mergesplit thing in a couple more places
8568c97
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR goes in sync with open-telemetry/opentelemetry-collector#13075, and upgrades pdata to 1.7.0. This is currently based after #40227. It can either come together or separately from that other PR. This has been tested locally. CI can't pass now because it relies on the changes in the core PR, which haven't been merged yet.
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This upgrades protobuf/pdata to [v1.7.0](https://github.com/open-telemetry/opentelemetry-proto/releases/tag/v1.7.0). Note: due to the move of the lookup tables, merging profiles required more non-trivial work. In order to facilitate this review, merging is therefore currently disabled for profiles. We will bring it back in a separate PR. Note: this needs its contrib counterpart before it can be moved out of draft.
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This upgrades protobuf/pdata to [v1.7.0](https://github.com/open-telemetry/opentelemetry-proto/releases/tag/v1.7.0). Note: due to the move of the lookup tables, merging profiles required more non-trivial work. In order to facilitate this review, merging is therefore currently disabled for profiles. We will bring it back in a separate PR. Note: this needs its contrib counterpart before it can be moved out of draft.
Description
This upgrades protobuf/pdata to v1.7.0.
Note: due to the move of the lookup tables, merging profiles required more non-trivial work.
In order to facilitate this review, merging is therefore currently disabled for profiles. We will bring it back in a separate PR.
Note: this needs its contrib counterpart before it can be moved out of draft.