-
Notifications
You must be signed in to change notification settings - Fork 893
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
Clarify SDK ReadableSpan's parent Context (fix accidentally requiring full parent chain) #3257
Clarify SDK ReadableSpan's parent Context (fix accidentally requiring full parent chain) #3257
Conversation
81d8390
to
4f83da5
Compare
Please tell me if I should create a tracking issue for this |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
I think this would be a rather important clarification to align the spec with reality. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
It might be a boring PR but I still think it should not be ignored |
I will mention this again tomorrow in the Spec call. Also, I will take a quick look at a few SIGs implementations to triple verify we are cool. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Can this be merged? |
… full parent chain) (open-telemetry#3257) Resolves open-telemetry/oteps#182 (comment)
Resolves open-telemetry/oteps#182 (comment)
Changes
Clarify required parent information in ReadableSpan. Technically a relaxation, but previously it was easy to overlook certain properties were required.
Related OTEP: open-telemetry/oteps#182