-
Notifications
You must be signed in to change notification settings - Fork 2.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
make otel-from-tree
results in ambiguous import errors
#30330
Labels
bug
Something isn't working
Comments
alanwest
added
bug
Something isn't working
needs triage
New item requiring triage
labels
Jan 8, 2024
I was able to reproduce and I've filed #30333 to fix this. |
dmitryax
pushed a commit
that referenced
this issue
Jan 10, 2024
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> From testing I found out that golang's `replace` directive didn't work properly when using an absolute path with the `../` included. Using a relative path or an absolute path (without `../` in the middle) resolves the issue. The simple and most clear solution is to use a true absolute path, so I've used `dirname` with the repo's root dir to determine the parent dir. **Link to tracking Issue:** <Issue number if applicable> Fixes #30330 **Testing:** <Describe what testing was performed and which tests were added.> Commands in bug description are all working.
cparkins
pushed a commit
to AmadeusITGroup/opentelemetry-collector-contrib
that referenced
this issue
Jan 10, 2024
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> From testing I found out that golang's `replace` directive didn't work properly when using an absolute path with the `../` included. Using a relative path or an absolute path (without `../` in the middle) resolves the issue. The simple and most clear solution is to use a true absolute path, so I've used `dirname` with the repo's root dir to determine the parent dir. **Link to tracking Issue:** <Issue number if applicable> Fixes open-telemetry#30330 **Testing:** <Describe what testing was performed and which tests were added.> Commands in bug description are all working.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
No response
What happened?
Running the following:
Results in lots of ambiguous import errors:
Collector version
v0.91.0
Environment information
No response
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: