-
Notifications
You must be signed in to change notification settings - Fork 76
Issues: w3c/trace-context
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Can Traceresponse enable parent-child relationship between browser and server spans?
#572
opened Apr 30, 2024 by
scheler
Autopublishing level2/Level3 specs need to work with multiple markdown files
#545
opened Aug 29, 2023 by
kalyanaj
Random part of trace ID should be uniformly distributed
backport-to-level-2-required
This is a PR against main that is meant to be backported to level 2.
#544
opened Jun 30, 2023 by
oertl
Level 3 spec: Update privacy section to include information about traceresponse headers.
#542
opened Jun 6, 2023 by
kalyanaj
Request to republish level-1 spec (to publish a recent editorial change)
#503
opened Oct 12, 2022 by
kalyanaj
Inconsistent text style
Editorial
The reported issue can be addressed with an editorial change. This tag could be combined with others
#485
opened Apr 12, 2022 by
dyladan
Be consistent with normative / non-normative sections
Editorial
The reported issue can be addressed with an editorial change. This tag could be combined with others
privacy-needs-resolution
Issue the Privacy Group has raised and looks for a response on.
todo
Privacy: What information may be revealed?
privacy-needs-resolution
Issue the Privacy Group has raised and looks for a response on.
workshop-fall-2020
Previous Next
ProTip!
Follow long discussions with comments:>50.