We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When opentelemtry is enabled, and using "-o yaml" on any command, the last span generated references an unexisting parent span.
On the image:
In fact, there is no root span at all in this trace - so I expect that the root span is not correctly sent.
All spans should be exported. E.g. when we do not add the "-o yaml" option:
Here we do have the root span exported (last one: parentId is undefined)
Any command that supports -o yaml:
none
I suspect some span not correctly finished - but I'm not an expert on opentracing api JS
garden version
garden version: 0.13.38
The text was updated successfully, but these errors were encountered:
Update: Same issue occurs when using "-o json"
Sorry, something went wrong.
Thanks for the bug report and repro! We'll look into this.
eysi09
Successfully merging a pull request may close this issue.
Bug
Current behavior
When opentelemtry is enabled, and using "-o yaml" on any command, the last span generated references an unexisting parent span.
On the image:
In fact, there is no root span at all in this trace - so I expect that the root span is not correctly sent.
Expected behavior
All spans should be exported.
E.g. when we do not add the "-o yaml" option:
Here we do have the root span exported (last one: parentId is undefined)
Reproducible example
Any command that supports -o yaml:
Workaround
none
Suggested solution(s)
I suspect some span not correctly finished - but I'm not an expert on opentracing api JS
Additional context
Your environment
garden version
garden version: 0.13.38
The text was updated successfully, but these errors were encountered: