-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[builder] remove ambigious import codepath #10015
[builder] remove ambigious import codepath #10015
Conversation
This code was added to handled an ambiguous import caused by a dependency that has been updated since v0.98.0. Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10015 +/- ##
==========================================
+ Coverage 91.54% 91.55% +0.01%
==========================================
Files 360 360
Lines 16695 16693 -2
==========================================
Hits 15284 15284
+ Misses 1074 1073 -1
+ Partials 337 336 -1 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
@@ -137,7 +137,7 @@ func TestVersioning(t *testing.T) { | |||
cfg.Distribution.Go = "go" | |||
cfg.Exporters = []Module{ | |||
{ | |||
GoMod: "go.opentelemetry.io/collector/exporter/otlpexporter v0.96.0", | |||
GoMod: "go.opentelemetry.io/collector/exporter/otlpexporter v0.97.0", |
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 do we need to update these?
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.
previous versions relied on the ambiguous import
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.
So... previous versions now fail to build? Sorry, I don't get it
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.
Sorry I wasn't really clear. Yes previous versions of the components (ones that import the problematic dependency) continue to raise an ambiguous import error unless they're updated.
This code was added to handled an ambiguous import caused by a dependency that has been updated since v0.98.0. --------- Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
This code was added to handled an ambiguous import caused by a dependency that has been updated since v0.98.0.