Skip to content

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

Merged
merged 14 commits into from
Jun 2, 2025
Merged

Upgrade proto to 1.7.0 #13075

merged 14 commits into from
Jun 2, 2025

Conversation

dmathieu
Copy link
Member

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.

Copy link

codecov bot commented May 22, 2025

Codecov Report

Attention: Patch coverage is 95.86207% with 6 lines in your changes missing coverage. Please review.

Project coverage is 91.48%. Comparing base (bc58775) to head (38f5e87).
Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
pdata/internal/wrapper_profiles.go 0.00% 2 Missing ⚠️
pdata/pprofile/json.go 95.65% 2 Missing ⚠️
...r/exporterhelper/xexporterhelper/profiles_batch.go 80.00% 1 Missing ⚠️
pdata/pprofile/profiles.go 66.66% 1 Missing ⚠️
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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dmathieu dmathieu marked this pull request as ready for review May 26, 2025 11:59
@dmathieu dmathieu requested review from a team and mx-psi as code owners May 26, 2025 11:59
atoulme pushed a commit to open-telemetry/opentelemetry-collector-contrib that referenced this pull request May 27, 2025
<!--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")
Copy link
Member

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)

Copy link
Member Author

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.

Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Member

@mx-psi mx-psi left a 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

@mx-psi mx-psi enabled auto-merge June 2, 2025 08:00
@mx-psi mx-psi added this pull request to the merge queue Jun 2, 2025
Merged via the queue into open-telemetry:main with commit 8568c97 Jun 2, 2025
50 of 56 checks passed
@dmathieu dmathieu deleted the proto-1-7-0 branch June 2, 2025 08:36
mx-psi pushed a commit to open-telemetry/opentelemetry-collector-contrib that referenced this pull request Jun 2, 2025
<!--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.
bogdandrutu pushed a commit to bogdandrutu/opentelemetry-collector that referenced this pull request Jun 2, 2025
<!--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.
malus2077 pushed a commit to malus2077/opentelemetry-collector that referenced this pull request Jun 3, 2025
<!--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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy