Update Dotnet compliance matrix #1392
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carlosalberto
approved these changes
Feb 1, 2021
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Samplers doesn't allow modifying tracestate: open-telemetry/opentelemetry-dotnet#1708
New Span ID created also for non-recording Spans: open-telemetry/opentelemetry-dotnet#1709
No explicit parent Span open-telemetry/opentelemetry-dotnet#1676
Changes
Please provide a brief description of the changes here. Update the
CHANGELOG.mdfor non-trivial changes. IfCHANGELOG.mdis updated,also be sure to update
spec-compliance-matrix.mdif necessary.Related issues #
Related oteps #