Distributed Tracing Working Group - Activity in 2019
No matches.
GitHub
w3c/trace-context
-
5 issues opened.
-
Response header name w3c/trace-context#371, by @dyladan.
-
Clarify handling of duplicate keys in tracestate w3c/trace-context#369, by @tsloughter.
-
Fix grammar in higher-version flags parsing w3c/trace-context#368, by @orthoplex64.
-
Use consistent notation in section 3.2.2.1 w3c/trace-context#367, by @orthoplex64.
-
Test suite server crashes with newer multidict version w3c/trace-context#366, by @Oberon00.
-
-
1 issue closed.
-
Response header name w3c/trace-context#371.
-
-
1 issue received 5 new comments.
-
3 pull requests opened.
-
Typo fix: s/complaint/compliant/ w3c/trace-context#372, by @c24t.
-
move header format rationale to root w3c/trace-context#370, by @dyladan.
-
Add response headers w3c/trace-context#365, by @dyladan.
-
-
2 pull requests merged.
-
Update links to implementations w3c/trace-context#357.
-
Typo fix: s/complaint/compliant/ w3c/trace-context#372.
-
-
3 pull requests received 24 new comments.
-
Add response headers w3c/trace-context#365 (20 comments by @dyladan, @justinfoote, @mtwo, @tylerbenson, @yurishkuro)
-
w3c/baggage
-
1 issue opened.
-
Consider renaming the header from Correlation-Context to correlationcontext w3c/baggage#13, by @mwear.
-
-
1 issue received 1 new comment.
-
Consider renaming the header from Correlation-Context to correlationcontext w3c/baggage#13 (1 comment by @SergeyKanzhelev)
-
-
1 pull request opened.
-
Rename header from Correlation-Context to correlationcontext w3c/baggage#14, by @mwear.
-
-
1 pull request received 3 new comments.
-
Rename header from Correlation-Context to correlationcontext w3c/baggage#14 (3 comments by @iredelmeier, @SergeyKanzhelev)
-
TR publications
-
2 documents published.
-
Trace Context published as a Proposed Recommendation. History of Trace Context
-
Trace Context Protocols Registry published as a Note. History of Trace Context Protocols Registry
-
Participants
-
1 organization joined.
-
Pearson plc joined.
-
GitHub
w3c/trace-context
-
6 issues opened.
-
ABNF improvement w3c/trace-context#364, by @plehegar.
-
Unused file in spec directory w3c/trace-context#363, by @dyladan.
-
Create a first draft of a response header spec w3c/trace-context#361, by @danielkhan.
-
Add general text format to the next version of the spec w3c/trace-context#360, by @danielkhan.
-
ReSpec issue w3c/trace-context#352, by @SergeyKanzhelev.
-
-
5 issues closed.
-
Last read-through and voting to go into PR w3c/trace-context#336.
-
Revert advice against backfilling of zeros w3c/trace-context#337.
-
Inter-operability of tracing systems operating with shorter trace-id w3c/trace-context#349.
-
ReSpec issue w3c/trace-context#352.
-
Warning message against implementation w3c/trace-context#345.
-
-
5 issues received 9 new comments.
-
Inter-operability of tracing systems operating with shorter trace-id w3c/trace-context#349 (4 comments by @codefromthecrypt, @morrisonlevi, @SergeyKanzhelev, @tedsuo)
-
w3c/trace-context#120 (2 comments by @plehegar)
-
We mention in joint blog post that opentelemetry is a reference implementation while readme says opencensus w3c/trace-context#353 (1 comment by @dyladan)
-
-
9 pull requests opened.
-
Use respec linking mechanisms w3c/trace-context#362, by @plehegar.
-
Clarify wording when no traceparent is received w3c/trace-context#359, by @tigrannajaryan.
-
Add links to Elastic APM implementations w3c/trace-context#358, by @felixbarny.
-
Update links to implementations w3c/trace-context#357, by @dyladan.
-
Fix the section on 64bit systems w3c/trace-context#356, by @SergeyKanzhelev.
-
Remove preview w3c/trace-context#355, by @plehegar.
-
Fixes #352 w3c/trace-context#354, by @plehegar.
-
moved content about trace-id into informative section as a first step… w3c/trace-context#351, by @SergeyKanzhelev.
-
Sergkanz/fix indentation w3c/trace-context#350, by @SergeyKanzhelev.
-
-
7 pull requests merged.
-
Use respec linking mechanisms w3c/trace-context#362.
-
Add links to Elastic APM implementations w3c/trace-context#358.
-
Fix the section on 64bit systems w3c/trace-context#356.
-
Fixes #352 w3c/trace-context#354.
-
Remove preview w3c/trace-context#355.
-
Sergkanz/fix indentation w3c/trace-context#350.
-
moved content about trace-id into informative section as a first step… w3c/trace-context#351.
-
-
5 pull requests received 48 new comments.
-
Fix the section on 64bit systems w3c/trace-context#356 (29 comments by @justinfoote, @reyang, @SergeyKanzhelev, @tedsuo, @yurishkuro)
-
Add links to Elastic APM implementations w3c/trace-context#358 (8 comments by @axw, @felixbarny, @hmdhk, @mtwo, @SergeyKanzhelev)
-
moved content about trace-id into informative section as a first step… w3c/trace-context#351 (5 comments by @SergeyKanzhelev, @tylerbenson, @yurishkuro)
-
Clarify wording when no traceparent is received w3c/trace-context#359 (3 comments by @plehegar, @SergeyKanzhelev, @tigrannajaryan)
-
Update links to implementations w3c/trace-context#357 (3 comments by @dyladan, @mtwo, @SergeyKanzhelev)
-
w3c/trace-context-protocols-registry
-
2 pull requests opened.
-
Echidna publication w3c/trace-context-protocols-registry#9, by @plehegar.
-
Add MQTT protocol w3c/trace-context-protocols-registry#8, by @plehegar.
-
-
2 pull requests merged.
-
Echidna publication w3c/trace-context-protocols-registry#9.
-
Add MQTT protocol w3c/trace-context-protocols-registry#8.
-
w3c/tracestate-ids-registry
-
1 issue received 1 new comment.
-
Use issues and issue templates instead of a PR to request a new ID w3c/tracestate-ids-registry#1 (1 comment by @discostu105)
-
-
1 pull request merged.
-
Replace pull request with creating an issue w3c/tracestate-ids-registry#3.
-
w3c/distributed-tracing-wg
-
1 pull request opened.
-
Fixed broken Slack link w3c/distributed-tracing-wg#26, by @mtwo.
-
-
1 pull request merged.
-
Fixed broken Slack link w3c/distributed-tracing-wg#26.
-
GitHub
w3c/trace-context
-
10 issues opened.
-
Inter-operability of tracing systems operating with shorter trace-id w3c/trace-context#349, by @SergeyKanzhelev.
-
Clarify "opaque" w3c/trace-context#348, by @ocelotl.
-
Wording in 4.2.2 is unclear w3c/trace-context#347, by @tigrannajaryan.
-
Warning message against implementation w3c/trace-context#345, by @ocelotl.
-
Clarify: Should be the 32 list item limit be part of limits? w3c/trace-context#343, by @danielkhan.
-
tracestate ows example fails before exercising service w3c/trace-context#341, by @toumorokoshi.
-
test fails on empty tracestate value w3c/trace-context#340, by @toumorokoshi.
-
Add application insights to the list w3c/trace-context#339, by @SychevIgor.
-
Revert advice against backfilling of zeros w3c/trace-context#337, by @codefromthecrypt.
-
Last read-through and voting to go into PR w3c/trace-context#336, by @danielkhan.
-
-
4 issues closed.
-
Trace-Context W3C Candidate Recommendation 24 September 2019 Review Notes w3c/trace-context#334.
-
tracestate ows example fails before exercising service w3c/trace-context#341.
-
test fails on empty tracestate value w3c/trace-context#340.
-
Clarify handling of multiple tracestate headers w3c/trace-context#289.
-
-
8 issues received 26 new comments.
-
Inter-operability of tracing systems operating with shorter trace-id w3c/trace-context#349 (12 comments by @codefromthecrypt, @danielkhan, @justinfoote, @mtwo, @nicmunroe, @SergeyKanzhelev, @tedsuo, @tylerbenson)
-
Trace-Context W3C Candidate Recommendation 24 September 2019 Review Notes w3c/trace-context#334 (7 comments by @bobstrecansky, @codefromthecrypt, @danielkhan)
-
Clarify: Should be the 32 list item limit be part of limits? w3c/trace-context#343 (1 comment by @danielkhan)
-
-
3 pull requests opened.
-
Address #337 w3c/trace-context#344, by @SergeyKanzhelev.
-
Fixes a problem with indentations that rendered incorrectly to HTML w3c/trace-context#342, by @danielkhan.
-
:lipstick: Fix spelling typo. w3c/trace-context#338, by @PureKrome.
-
-
2 pull requests merged.
-
Fixes a problem with indentations that rendered incorrectly to HTML w3c/trace-context#342.
-
:lipstick: Fix spelling typo. w3c/trace-context#338.
-
-
1 pull request closed.
-
Address #337 w3c/trace-context#344.
-
-
1 pull request reopened.
-
Fixes a problem with indentations that rendered incorrectly to HTML w3c/trace-context#342, by @danielkhan.
-
-
3 pull requests received 62 new comments.
-
Address #337 w3c/trace-context#344 (58 comments by @bogdandrutu, @codefromthecrypt, @danielkhan, @jcchavezs, @nicmunroe, @reyang, @SergeyKanzhelev, @tedsuo, @tylerbenson, @yurishkuro)
-
Fixes a problem with indentations that rendered incorrectly to HTML w3c/trace-context#342 (1 comment by @SergeyKanzhelev)
-
w3c/distributed-tracing-wg
-
1 issue opened.
-
Add an example of how tracestate will be used w3c/distributed-tracing-wg#30, by @tigrannajaryan.
-
-
2 pull requests merged.
-
Add link to meeting notes. w3c/distributed-tracing-wg#24.
-
Add link to new meeting notes w3c/distributed-tracing-wg#25.
-
GitHub
w3c/trace-context
-
3 issues opened.
-
How multiple APMs in a process can "collaborate" on a given trace-context? w3c/trace-context#335, by @yurishkuro.
-
Trace-Context W3C Candidate Recommendation 24 September 2019 Review Notes w3c/trace-context#334, by @bobstrecansky.
-
Update tracestate test to validate new tenant format w3c/trace-context#331, by @toddwest.
-
-
2 issues closed.
-
Add negative test cases for Tracestate value w3c/trace-context#304.
-
Update tracestate test to validate new tenant format w3c/trace-context#331.
-
-
1 issue reopened.
-
Provide vendor/open source product name register for tracestate w3c/trace-context#58, by @danielkhan.
-
-
4 issues received 10 new comments.
-
Update tracestate test to validate new tenant format w3c/trace-context#331 (3 comments by @reyang, @toddwest)
-
How multiple APMs in a process can "collaborate" on a given trace-context? w3c/trace-context#335 (1 comment by @untitaker)
-
2 pull requests opened.
-
Add implementation page w3c/trace-context#333, by @danielkhan.
-
Update test cases to reflect the latest spec change w3c/trace-context#332, by @reyang.
-
-
3 pull requests merged.
-
Update test cases to reflect the latest spec change w3c/trace-context#332.
-
Add implementation page w3c/trace-context#333.
-
Clarified how unknown trace-flags are passed w3c/trace-context#330.
-
-
1 pull request received 6 new comments.
-
Update test cases to reflect the latest spec change w3c/trace-context#332 (6 comments by @mwear, @reyang)
-
TR publications
-
1 document published.
-
Trace Context published as a Candidate Recommendation Snapshot. History of Trace Context
-
GitHub
w3c/trace-context
-
6 issues closed.
-
Clarify trace restarting scenarios w3c/trace-context#290.
-
Conflicting guidlines for handling multiple tracestate headers w3c/trace-context#325.
-
grammar in abstract w3c/trace-context#285.
-
Make downgrading the version an allowed mutation of traceparent w3c/trace-context#291.
-
Verify tracestate key and value limits w3c/trace-context#324.
-
tenant id format w3c/trace-context#316.
-
-
6 issues received 6 new comments.
-
Conflicting guidlines for handling multiple tracestate headers w3c/trace-context#325 (1 comment by @danielkhan)
-
Make downgrading the version an allowed mutation of traceparent w3c/trace-context#291 (1 comment by @danielkhan)
-
2 pull requests opened.
-
Clarified how unknown trace-flags are passed w3c/trace-context#330, by @mtwo.
-
A tiny bit of formatting, fix code quotation error w3c/trace-context#329, by @haf.
-
-
2 pull requests merged.
-
A tiny bit of formatting, fix code quotation error w3c/trace-context#329.
-
Clarify handling of tracestate as multiple header fields w3c/trace-context#328.
-
-
3 pull requests received 6 new comments.
-
Clarify handling of tracestate as multiple header fields w3c/trace-context#328 (2 comments by @mwear)
w3c/distributed-tracing-wg
-
3 pull requests opened.
-
Add link to new meeting notes w3c/distributed-tracing-wg#25, by @danielkhan.
-
Add link to meeting notes. w3c/distributed-tracing-wg#24, by @danielkhan.
-
Meeting minutes 2019-07-30 w3c/distributed-tracing-wg#23, by @danielkhan.
-
-
1 pull request merged.
-
Meeting minutes 2019-07-30 w3c/distributed-tracing-wg#23.
-
GitHub
w3c/trace-context
-
8 issues opened.
-
Conflicting guidlines for handling multiple tracestate headers w3c/trace-context#325, by @mwear.
-
Verify tracestate key and value limits w3c/trace-context#324, by @mwear.
-
tenant id format w3c/trace-context#316, by @mwear.
-
Typo in §2.3 Design overview (s/tracestate/traceparent/) w3c/trace-context#315, by @kqr.
-
tracestate validation w3c/trace-context#311, by @mwear.
-
Clarify 512 byte header size w3c/trace-context#310, by @mwear.
-
Anchor links across spec files don't work w3c/trace-context#309, by @iredelmeier.
-
Where should images be placed? w3c/trace-context#308, by @iredelmeier.
-
-
6 issues closed.
-
Typo in §2.3 Design overview (s/tracestate/traceparent/) w3c/trace-context#315.
-
tracestate validation w3c/trace-context#311.
-
Clarify 512 byte header size w3c/trace-context#310.
-
Where should images be placed? w3c/trace-context#308.
-
Anchor links across spec files don't work w3c/trace-context#309.
-
APA WG comment: fingerprinting of assistive technology users? w3c/trace-context#306.
-
-
9 issues received 21 new comments.
-
Conflicting guidlines for handling multiple tracestate headers w3c/trace-context#325 (6 comments by @mtwo, @mwear, @yurishkuro)
-
Typo in §2.3 Design overview (s/tracestate/traceparent/) w3c/trace-context#315 (2 comments by @mwear)
-
APA WG comment: fingerprinting of assistive technology users? w3c/trace-context#306 (1 comment by @michael-n-cooper)
-
-
13 pull requests opened.
-
Clarify handling of tracestate as multiple header fields w3c/trace-context#328, by @mwear.
-
Fix leftover spaces in markup of tracestate and traceparent w3c/trace-context#327, by @danielkhan.
-
Clarify behavior when receiving a tracestate header without traceparent w3c/trace-context#326, by @mwear.
-
Various edits - fixes to missing words, spaces, etc w3c/trace-context#323, by @mwear.
-
Relax tenant id format w3c/trace-context#322, by @mwear.
-
Remove non-normative duplication w3c/trace-context#321, by @mwear.
-
Remove italics from RFC 2119 keywords w3c/trace-context#320, by @mwear.
-
Fix respec rendering w3c/trace-context#319, by @mwear.
-
Fix typo in §2.3 w3c/trace-context#318, by @mwear.
-
Revert "Remove hard line breaks" w3c/trace-context#317, by @danielkhan.
-
Make tracestate validation optional w3c/trace-context#314, by @mwear.
-
Clarify tracestate header size w3c/trace-context#313, by @mwear.
-
Remove hard line breaks w3c/trace-context#312, by @iredelmeier.
-
-
13 pull requests merged.
-
Fix leftover spaces in markup of tracestate and traceparent w3c/trace-context#327.
-
Relax tenant id format w3c/trace-context#322.
-
Various edits - fixes to missing words, spaces, etc w3c/trace-context#323.
-
Clarify behavior when receiving a tracestate header without traceparent w3c/trace-context#326.
-
Remove non-normative duplication w3c/trace-context#321.
-
Fix typo in §2.3 w3c/trace-context#318.
-
Remove italics from RFC 2119 keywords w3c/trace-context#320.
-
Fix respec rendering w3c/trace-context#319.
-
Clarify tracestate header size w3c/trace-context#313.
-
Make tracestate validation optional w3c/trace-context#314.
-
Writing edits w3c/trace-context#307.
-
Revert "Remove hard line breaks" w3c/trace-context#317.
-
Remove hard line breaks w3c/trace-context#312.
-
-
2 pull requests reopened.
-
Revert "Remove hard line breaks" w3c/trace-context#317, by @danielkhan.
-
Revert "Remove hard line breaks" w3c/trace-context#317, by @danielkhan.
-
-
8 pull requests received 19 new comments.
-
Make tracestate validation optional w3c/trace-context#314 (7 comments by @discostu105, @mwear, @yurishkuro)
-
Clarify handling of tracestate as multiple header fields w3c/trace-context#328 (2 comments by @danielkhan, @mtwo)
-
Various edits - fixes to missing words, spaces, etc w3c/trace-context#323 (1 comment by @danielkhan)
-
Clarify behavior when receiving a tracestate header without traceparent w3c/trace-context#326 (1 comment by @danielkhan)
-
w3c/baggage
-
1 issue opened.
-
Security and encryption considerations w3c/baggage#12, by @remitly-srivatsa.
-
-
3 issues received 3 new comments.
-
Clarify distinction between correlation-context and trace-context's tracestate w3c/baggage#11 (1 comment by @iredelmeier)
GitHub
w3c/baggage
-
1 issue opened.
-
1 issue received 1 new comment.
-
Clarify distinction between correlation-context and trace-context's tracestate w3c/baggage#11 (1 comment by @yurishkuro)
-
w3c/trace-context
-
1 issue opened.
-
APA WG comment: fingerprinting of assistive technology users? w3c/trace-context#306, by @michael-n-cooper.
-
-
3 issues closed.
-
'Recorded' flag should be renamed in sampled flag w3c/trace-context#265.
-
Always propagate entire trace ID w3c/trace-context#292.
-
Section on Recorded flag should be shorter and more precise w3c/trace-context#237.
-
-
8 issues received 14 new comments.
-
Edit 'Sampled Flag' section to be more concise. w3c/trace-context#303 (3 comments by @AloisReitbauer, @mtwo)
-
APA WG comment: fingerprinting of assistive technology users? w3c/trace-context#306 (3 comments by @AloisReitbauer, @danielkhan, @michael-n-cooper)
-
Section on Recorded flag should be shorter and more precise w3c/trace-context#237 (1 comment by @danielkhan)
-
Should implementation propagate flag it doesn't know about w3c/trace-context#296 (1 comment by @discostu105)
-
-
1 pull request opened.
-
Writing edits w3c/trace-context#307, by @iredelmeier.
-
-
2 pull requests merged.
-
improve restart trace mutation wording w3c/trace-context#300.
-
flags -> trace-flags w3c/trace-context#305.
-
-
1 pull request received 3 new comments.
w3c/tracestate-ids-registry
-
1 pull request opened.
-
Replace pull request with creating an issue w3c/tracestate-ids-registry#3, by @danielkhan.
-
w3c/distributed-tracing-wg
-
1 pull request opened.
-
Added meeting notes w3c/distributed-tracing-wg#22, by @danielkhan.
-
-
2 pull requests merged.
-
Added meeting notes w3c/distributed-tracing-wg#22.
-
Fix documents status and removed broken links w3c/distributed-tracing-wg#17.
-
TR publications
-
1 document published.
-
Trace Context published as a Candidate Recommendation Snapshot. History of Trace Context
-
GitHub
w3c/tracestate-ids-registry
-
2 issues opened.
-
Register B3 w3c/tracestate-ids-registry#2, by @SergeyKanzhelev.
-
Use issues and issue templates instead of a PR to request a new ID w3c/tracestate-ids-registry#1, by @danielkhan.
-
-
1 issue received 1 new comment.
-
Use issues and issue templates instead of a PR to request a new ID w3c/tracestate-ids-registry#1 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context
-
8 issues opened.
-
Add negative test cases for Tracestate value w3c/trace-context#304, by @reyang.
-
Edit 'Sampled Flag' section to be more concise. w3c/trace-context#303, by @danielkhan.
-
Should implementation propagate flag it doesn't know about w3c/trace-context#296, by @SergeyKanzhelev.
-
Always propagate entire trace ID w3c/trace-context#292, by @arminru.
-
Make downgrading the version an allowed mutation of traceparent w3c/trace-context#291, by @arminru.
-
Clarify trace restarting scenarios w3c/trace-context#290, by @arminru.
-
Clarify handling of multiple tracestate headers w3c/trace-context#289, by @arminru.
-
grammar in abstract w3c/trace-context#285, by @dret.
-
-
3 issues closed.
-
Enable Rewrap or similar solution to limit the line width and simplify reviews w3c/trace-context#228.
-
Value format section is confusing w3c/trace-context#168.
-
Question on test-harness cases around invalid tracestate w3c/trace-context#195.
-
-
1 issue reopened.
-
grammar in abstract w3c/trace-context#285, by @SergeyKanzhelev.
-
-
8 issues received 31 new comments.
-
Edit 'Sampled Flag' section to be more concise. w3c/trace-context#303 (20 comments by @AloisReitbauer, @danielkhan, @mtwo, @nikmd23, @SergeyKanzhelev, @yurishkuro)
-
Add negative test cases for Tracestate value w3c/trace-context#304 (3 comments by @reyang, @SergeyKanzhelev)
-
Make downgrading the version an allowed mutation of traceparent w3c/trace-context#291 (1 comment by @SergeyKanzhelev)
-
Enable Rewrap or similar solution to limit the line width and simplify reviews w3c/trace-context#228 (1 comment by @SergeyKanzhelev)
-
-
13 pull requests opened.
-
flags -> trace-flags w3c/trace-context#305, by @SergeyKanzhelev.
-
Changes `recorded` to `sampled` w3c/trace-context#302, by @danielkhan.
-
Editorial change from 'recorded' flag to 'sampled' flag. w3c/trace-context#301, by @danielkhan.
-
improve restart trace mutation wording w3c/trace-context#300, by @SergeyKanzhelev.
-
added semicolon in java code w3c/trace-context#299, by @SergeyKanzhelev.
-
downgrade mutation w3c/trace-context#298, by @SergeyKanzhelev.
-
shorter trace id: should which meant MUST w3c/trace-context#297, by @SergeyKanzhelev.
-
Update 01-abstract.md w3c/trace-context#294, by @duerst.
-
Update report status and fix rationale link w3c/trace-context#293, by @arminru.
-
Improve recorded flag doc w3c/trace-context#288, by @arminru.
-
CR publication tweaks w3c/trace-context#287, by @plehegar.
-
Fix parent and trace ID being mixed up in example w3c/trace-context#286, by @arminru.
-
-
13 pull requests merged.
-
downgrade mutation w3c/trace-context#298.
-
shorter trace id: should which meant MUST w3c/trace-context#297.
-
Changes `recorded` to `sampled` w3c/trace-context#302.
-
Improve recorded flag doc w3c/trace-context#288.
-
Update report status and fix rationale link w3c/trace-context#293.
-
Update 01-abstract.md w3c/trace-context#294.
-
added semicolon in java code w3c/trace-context#299.
-
Add processing model to spec w3c/trace-context#270.
-
CR publication tweaks w3c/trace-context#287.
-
Fix parent and trace ID being mixed up in example w3c/trace-context#286.
-
spec is moved to CR w3c/trace-context#284.
-
Removed Trace-ID from the tracestate in examples w3c/trace-context#283.
-
-
1 pull request closed.
-
Editorial change from 'recorded' flag to 'sampled' flag. w3c/trace-context#301.
-
-
8 pull requests received 42 new comments.
-
Add processing model to spec w3c/trace-context#270 (17 comments by @AloisReitbauer, @mtwo, @nikmd23, @SergeyKanzhelev)
-
Editorial change from 'recorded' flag to 'sampled' flag. w3c/trace-context#301 (9 comments by @danielkhan, @SergeyKanzhelev)
-
Fix parent and trace ID being mixed up in example w3c/trace-context#286 (5 comments by @arminru, @discostu105, @SergeyKanzhelev)
-
Changes `recorded` to `sampled` w3c/trace-context#302 (4 comments by @danielkhan, @discostu105, @SergeyKanzhelev)
-
w3c/distributed-tracing-wg
-
6 pull requests opened.
-
added link to other repos w3c/distributed-tracing-wg#21, by @AloisReitbauer.
-
fixed typo w3c/distributed-tracing-wg#20, by @AloisReitbauer.
-
add github link to trace context w3c/distributed-tracing-wg#19, by @AloisReitbauer.
-
change status of trace context to CR w3c/distributed-tracing-wg#18, by @AloisReitbauer.
-
Fix documents status and removed broken links w3c/distributed-tracing-wg#17, by @SergeyKanzhelev.
-
Added meeting notes for 2019-05-07 w3c/distributed-tracing-wg#16, by @danielkhan.
-
-
6 pull requests merged.
-
added link to other repos w3c/distributed-tracing-wg#21.
-
fixed typo w3c/distributed-tracing-wg#20.
-
add github link to trace context w3c/distributed-tracing-wg#19.
-
Documentation fixes w3c/distributed-tracing-wg#15.
-
change status of trace context to CR w3c/distributed-tracing-wg#18.
-
Added meeting notes for 2019-05-07 w3c/distributed-tracing-wg#16.
-
-
1 pull request received 1 new comment.
-
Fix documents status and removed broken links w3c/distributed-tracing-wg#17 (1 comment by @AloisReitbauer)
-
w3c/baggage
-
1 issue opened.
-
Use cases for Baggage w3c/baggage#10, by @yurishkuro.
-
-
1 pull request merged.
-
fix issues after refactoring of repos w3c/baggage#2.
-
-
1 pull request received 2 new comments.
-
fix issues after refactoring of repos w3c/baggage#2 (2 comments by @AloisReitbauer, @SergeyKanzhelev)
-
GitHub
w3c/trace-context
-
3 issues opened.
-
Tracing for passthrough requests (CDN use case) w3c/trace-context#278, by @bobrik.
-
Extend glossary with additional terms w3c/trace-context#277, by @watson.
-
reSpec issues w3c/trace-context#274, by @SergeyKanzhelev.
-
-
13 issues closed.
-
Should we allow modifying tracestate without changing traceparent? w3c/trace-context#250.
-
What should we do when we restart a trace w3c/trace-context#252.
-
In header_format we state that implementations should create globally unique values w3c/trace-context#266.
-
Provide detailed description how to modify and use trace-parent data w3c/trace-context#269.
-
Tracing for passthrough requests (CDN use case) w3c/trace-context#278.
-
Add more editors for the document and add credits section w3c/trace-context#268.
-
reSpec issues w3c/trace-context#274.
-
abstract needs editing w3c/trace-context#203.
-
Mechanism to audit randomness of trace-id w3c/trace-context#210.
-
Header limits are obsolete and should be removed w3c/trace-context#239.
-
Privacy risk if trace context is used as response headers in cross-origin calls w3c/trace-context#209.
-
Trace-id and Span-id - What makes up valid bytes? w3c/trace-context#194.
-
How and when are you allowed to restart a trace w3c/trace-context#146.
-
-
9 issues received 15 new comments.
-
'Recorded' flag should be renamed in sampled flag w3c/trace-context#265 (4 comments by @codefromthecrypt, @felixbarny, @yurishkuro)
-
Tracing for passthrough requests (CDN use case) w3c/trace-context#278 (4 comments by @bobrik, @SergeyKanzhelev)
-
Add more editors for the document and add credits section w3c/trace-context#268 (1 comment by @SergeyKanzhelev)
-
Privacy risk if trace context is used as response headers in cross-origin calls w3c/trace-context#209 (1 comment by @SergeyKanzhelev)
-
Header limits are obsolete and should be removed w3c/trace-context#239 (1 comment by @SergeyKanzhelev)
-
Trace-id and Span-id - What makes up valid bytes? w3c/trace-context#194 (1 comment by @SergeyKanzhelev)
-
-
11 pull requests opened.
-
spec is moved to CR w3c/trace-context#284, by @SergeyKanzhelev.
-
Removed Trace-ID from the tracestate in examples w3c/trace-context#283, by @SergeyKanzhelev.
-
lines rewrap w3c/trace-context#282, by @SergeyKanzhelev.
-
Set strict-level on certain tracestate validation tests w3c/trace-context#281, by @discostu105.
-
returned biblio back w3c/trace-context#280, by @SergeyKanzhelev.
-
Add abstract w3c/trace-context#276, by @AloisReitbauer.
-
Adding abstract to spec w3c/trace-context#275, by @AloisReitbauer.
-
randomness requirement w3c/trace-context#273, by @SergeyKanzhelev.
-
acknowledgements w3c/trace-context#272, by @SergeyKanzhelev.
-
List Erlang implementation w3c/trace-context#271, by @deadtrickster.
-
Add processing model to spec w3c/trace-context#270, by @AloisReitbauer.
-
-
13 pull requests merged.
-
Set strict-level on certain tracestate validation tests w3c/trace-context#281.
-
lines rewrap w3c/trace-context#282.
-
acknowledgements w3c/trace-context#272.
-
randomness requirement w3c/trace-context#273.
-
Add abstract w3c/trace-context#276.
-
returned biblio back w3c/trace-context#280.
-
List Erlang implementation w3c/trace-context#271.
-
prepare for CR w3c/trace-context#267.
-
traceparent restart should require tracestate cleanup rationale w3c/trace-context#260.
-
added potential privacy risk w3c/trace-context#258.
-
describe what invalid means w3c/trace-context#257.
-
Make tracestate limit the responsibility of a platform w3c/trace-context#248.
-
Changes to wording, structure, grammar and spelling w3c/trace-context#259.
-
-
1 pull request closed.
-
Adding abstract to spec w3c/trace-context#275.
-
-
9 pull requests received 151 new comments.
-
Add processing model to spec w3c/trace-context#270 (89 comments by @AloisReitbauer, @danielkhan, @mwear, @nikmd23, @SergeyKanzhelev, @taisph)
-
randomness requirement w3c/trace-context#273 (18 comments by @AloisReitbauer, @nikmd23, @SergeyKanzhelev, @watson)
-
acknowledgements w3c/trace-context#272 (8 comments by @bogdandrutu, @nikmd23, @SergeyKanzhelev, @yurishkuro)
-
Set strict-level on certain tracestate validation tests w3c/trace-context#281 (2 comments by @discostu105, @SergeyKanzhelev)
-
Changes to wording, structure, grammar and spelling w3c/trace-context#259 (1 comment by @SergeyKanzhelev)
-
w3c/distributed-tracing-wg
-
1 issue opened.
-
Explain multi-graph pattern of tracestate w3c/distributed-tracing-wg#28, by @SergeyKanzhelev.
-
-
2 pull requests opened.
-
Documentation fixes w3c/distributed-tracing-wg#15, by @devinsba.
-
Meeting notes 2019-04-23 w3c/distributed-tracing-wg#14, by @danielkhan.
-
-
1 pull request merged.
-
Meeting notes 2019-04-23 w3c/distributed-tracing-wg#14.
-
TR publications
-
1 document published.
-
Trace Context Protocols Registry published as a Note. History of Trace Context Protocols Registry
-
GitHub
w3c/trace-context
-
7 issues opened.
-
Provide detailed description how to modify and use trace-parent data w3c/trace-context#269, by @AloisReitbauer.
-
Add more editors for the document and add credits section w3c/trace-context#268, by @SergeyKanzhelev.
-
In header_format we state that implementations should create globally unique values w3c/trace-context#266, by @danielkhan.
-
'Recorded' flag should be renamed in sampled flag w3c/trace-context#265, by @danielkhan.
-
Please clarify tracestate purpose w3c/trace-context#264, by @falenn.
-
Please clarify tracestate construction w3c/trace-context#263, by @falenn.
-
Remove description on how to fill up shorter trace-ids w3c/trace-context#262, by @danielkhan.
-
-
4 issues closed.
-
Please clarify tracestate construction w3c/trace-context#263.
-
Please clarify tracestate purpose w3c/trace-context#264.
-
Behaviour for invalid headers in forwarding mode not defined w3c/trace-context#220.
-
Test case for invalid traceparent restart should validate that all children has the same ID w3c/trace-context#211.
-
-
8 issues received 24 new comments.
-
Add more editors for the document and add credits section w3c/trace-context#268 (9 comments by @codefromthecrypt, @CodingFabian, @nikmd23, @plehegar, @SergeyKanzhelev)
-
Please clarify tracestate purpose w3c/trace-context#264 (7 comments by @falenn, @SergeyKanzhelev, @yurishkuro)
-
Please clarify tracestate construction w3c/trace-context#263 (3 comments by @falenn, @SergeyKanzhelev)
-
Test case for invalid traceparent restart should validate that all children has the same ID w3c/trace-context#211 (1 comment by @SergeyKanzhelev)
-
Should we allow modifying tracestate without changing traceparent? w3c/trace-context#250 (1 comment by @SergeyKanzhelev)
-
How and when are you allowed to restart a trace w3c/trace-context#146 (1 comment by @SergeyKanzhelev)
-
Behaviour for invalid headers in forwarding mode not defined w3c/trace-context#220 (1 comment by @danielkhan)
-
-
3 pull requests opened.
-
prepare for CR w3c/trace-context#267, by @SergeyKanzhelev.
-
respec changed its syntax w3c/trace-context#261, by @plehegar.
-
traceparent restart should require tracestate cleanup rationale w3c/trace-context#260, by @SergeyKanzhelev.
-
-
2 pull requests merged.
-
References appendix w3c/trace-context#256.
-
respec changed its syntax w3c/trace-context#261.
-
-
6 pull requests received 111 new comments.
-
Changes to wording, structure, grammar and spelling w3c/trace-context#259 (74 comments by @AloisReitbauer, @danielkhan, @mtwo, @mwear, @nikmd23, @plehegar, @SergeyKanzhelev, @yurishkuro)
-
Make tracestate limit the responsibility of a platform w3c/trace-context#248 (12 comments by @danielkhan, @devinsba, @mwear, @nikmd23, @plehegar, @SergeyKanzhelev, @yurishkuro)
-
prepare for CR w3c/trace-context#267 (11 comments by @AloisReitbauer, @mtwo, @plehegar, @SergeyKanzhelev)
-
traceparent restart should require tracestate cleanup rationale w3c/trace-context#260 (9 comments by @AloisReitbauer, @mtwo, @SergeyKanzhelev)
-
added potential privacy risk w3c/trace-context#258 (4 comments by @AloisReitbauer, @mtwo, @nikmd23, @plehegar)
-
w3c/distributed-tracing-wg
-
2 pull requests opened.
-
Meeting minutes 2019-03-13 w3c/distributed-tracing-wg#13, by @danielkhan.
-
Meeting notes 2019-02-26 w3c/distributed-tracing-wg#12, by @danielkhan.
-
-
2 pull requests merged.
-
Meeting minutes 2019-03-13 w3c/distributed-tracing-wg#13.
-
Meeting notes 2019-02-26 w3c/distributed-tracing-wg#12.
-
w3c/baggage
-
1 issue received 1 new comment.
GitHub
w3c/trace-context
-
5 issues opened.
-
Migrate other protocols to corresponding repositories w3c/trace-context#254, by @SergeyKanzhelev.
-
What should we do when we restart a trace w3c/trace-context#252, by @AloisReitbauer.
-
Should services in forward mode parse headers? w3c/trace-context#251, by @danielkhan.
-
Should we allow modifying tracestate without changing traceparent? w3c/trace-context#250, by @danielkhan.
-
Mark "Other Protocols" section non-formative and simply point to the registry w3c/trace-context#247, by @SergeyKanzhelev.
-
-
9 issues closed.
-
Graph construction is unclear with current form of traceparent / tracestate w3c/trace-context#204.
-
Migrate other protocols to corresponding repositories w3c/trace-context#254.
-
Mark "Other Protocols" section non-formative and simply point to the registry w3c/trace-context#247.
-
Use IETF Dictionary for tracestate w3c/trace-context#197.
-
Action on tracestate header larger than 512 is confusing w3c/trace-context#175.
-
Explain/remove 512 limit of tracestate in spec w3c/trace-context#109.
-
Can a tracer/application only carry trace-parent and drop trace-state? w3c/trace-context#218.
-
Document procedures for spec changes w3c/trace-context#165.
-
Clarity on the definition of Span-id w3c/trace-context#193.
-
-
2 issues reopened.
-
Should we allow modifying tracestate without changing traceparent? w3c/trace-context#250, by @danielkhan.
-
Header limits are obsolete and should be removed w3c/trace-context#239, by @SergeyKanzhelev.
-
-
17 issues received 42 new comments.
-
Should services in forward mode parse headers? w3c/trace-context#251 (7 comments by @AloisReitbauer, @danielkhan, @SergeyKanzhelev, @yurishkuro)
-
Migrate other protocols to corresponding repositories w3c/trace-context#254 (5 comments by @plehegar, @SergeyKanzhelev)
-
Mark "Other Protocols" section non-formative and simply point to the registry w3c/trace-context#247 (5 comments by @AloisReitbauer, @danielkhan, @nikmd23, @plehegar)
-
What should we do when we restart a trace w3c/trace-context#252 (4 comments by @AloisReitbauer, @bogdandrutu, @nikmd23, @SergeyKanzhelev)
-
Section on Recorded flag should be shorter and more precise w3c/trace-context#237 (3 comments by @danielkhan, @mtwo, @SergeyKanzhelev)
-
Header limits are obsolete and should be removed w3c/trace-context#239 (3 comments by @danielkhan, @SergeyKanzhelev)
-
Should we allow modifying tracestate without changing traceparent? w3c/trace-context#250 (2 comments by @danielkhan, @nikmd23)
-
Clarity on the definition of Span-id w3c/trace-context#193 (2 comments by @chris-rogala, @SergeyKanzhelev)
-
Privacy risk if trace context is used as response headers in cross-origin calls w3c/trace-context#209 (1 comment by @SergeyKanzhelev)
-
Graph construction is unclear with current form of traceparent / tracestate w3c/trace-context#204 (1 comment by @danielkhan)
-
Enable Rewrap or similar solution to limit the line width and simplify reviews w3c/trace-context#228 (1 comment by @nikmd23)
-
Action on tracestate header larger than 512 is confusing w3c/trace-context#175 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#109 (1 comment by @SergeyKanzhelev)
-
Can a tracer/application only carry trace-parent and drop trace-state? w3c/trace-context#218 (1 comment by @SergeyKanzhelev)
-
-
9 pull requests opened.
-
Changes to wording, structure, grammar and spelling w3c/trace-context#259, by @danielkhan.
-
added potential privacy risk w3c/trace-context#258, by @SergeyKanzhelev.
-
describe what invalid means w3c/trace-context#257, by @SergeyKanzhelev.
-
References appendix w3c/trace-context#256, by @plehegar.
-
remove protocol extensions w3c/trace-context#255, by @SergeyKanzhelev.
-
improve test coverage for multiple requests scenario w3c/trace-context#253, by @reyang.
-
Mark other protocols section point to the registry w3c/trace-context#249, by @SergeyKanzhelev.
-
Make tracestate limit the responsibility of a platform w3c/trace-context#248, by @SergeyKanzhelev.
-
Consolidates all work done on individual CR* branches w3c/trace-context#246, by @danielkhan.
-
-
6 pull requests merged.
-
improve test coverage for multiple requests scenario w3c/trace-context#253.
-
Update privacy statement for CR readiness w3c/trace-context#223.
-
remove protocol extensions w3c/trace-context#255.
-
Glossary section w3c/trace-context#231.
-
Mark other protocols section point to the registry w3c/trace-context#249.
-
Echidna w3c/trace-context#243.
-
-
7 pull requests closed.
-
Consolidates all work done on individual CR* branches w3c/trace-context#246.
-
[WIP] Changed abstract to define the problem we are solving and the proposed solution w3c/trace-context#221.
-
Add processing model to spec w3c/trace-context#222.
-
[WIP] MQTT format specification w3c/trace-context#245.
-
AMQP draft: PR was moved to different repository w3c/trace-context#217.
-
Draft of binary format: moved to other repository w3c/trace-context#215.
-
moved semantics-related notes in the semantics document w3c/trace-context#214.
-
-
13 pull requests received 123 new comments.
-
Changes to wording, structure, grammar and spelling w3c/trace-context#259 (51 comments by @danielkhan, @SergeyKanzhelev)
-
Add processing model to spec w3c/trace-context#222 (20 comments by @AloisReitbauer, @danielkhan, @SergeyKanzhelev)
-
Make tracestate limit the responsibility of a platform w3c/trace-context#248 (13 comments by @AloisReitbauer, @bogdandrutu, @danielkhan, @discostu105, @mtwo, @SergeyKanzhelev, @yurishkuro)
-
Consolidates all work done on individual CR* branches w3c/trace-context#246 (10 comments by @AloisReitbauer, @danielkhan, @discostu105, @SergeyKanzhelev)
-
AMQP draft: PR was moved to different repository w3c/trace-context#217 (8 comments by @calohmn, @grs, @SergeyKanzhelev)
-
improve test coverage for multiple requests scenario w3c/trace-context#253 (6 comments by @bogdandrutu, @plehegar, @reyang, @SergeyKanzhelev)
-
Update privacy statement for CR readiness w3c/trace-context#223 (4 comments by @AloisReitbauer, @danielkhan, @SergeyKanzhelev)
-
Mark other protocols section point to the registry w3c/trace-context#249 (4 comments by @AloisReitbauer, @plehegar, @SergeyKanzhelev)
-
[WIP] Changed abstract to define the problem we are solving and the proposed solution w3c/trace-context#221 (2 comments by @danielkhan, @SergeyKanzhelev)
-
[WIP] MQTT format specification w3c/trace-context#245 (2 comments by @AloisReitbauer, @SergeyKanzhelev)
-
Draft of binary format: moved to other repository w3c/trace-context#215 (1 comment by @SergeyKanzhelev)
-
moved semantics-related notes in the semantics document w3c/trace-context#214 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context-protocols-registry
-
1 issue opened.
-
Register cloud events tracecontext extension w3c/trace-context-protocols-registry#7, by @SergeyKanzhelev.
-
-
1 issue received 1 new comment.
-
w3c/trace-context-protocols-registry#4 (1 comment by @SergeyKanzhelev)
-
-
4 pull requests opened.
-
Add Sergey and plh as editors per today's call w3c/trace-context-protocols-registry#6, by @plehegar.
-
missing parenthesis w3c/trace-context-protocols-registry#3, by @plehegar.
-
readme and contributing update w3c/trace-context-protocols-registry#2, by @SergeyKanzhelev.
-
Make this spec markdown-based w3c/trace-context-protocols-registry#1, by @SergeyKanzhelev.
-
-
4 pull requests merged.
-
Add Sergey and plh as editors per today's call w3c/trace-context-protocols-registry#6.
-
missing parenthesis w3c/trace-context-protocols-registry#3.
-
readme and contributing update w3c/trace-context-protocols-registry#2.
-
Make this spec markdown-based w3c/trace-context-protocols-registry#1.
-
-
1 pull request received 1 new comment.
-
Make this spec markdown-based w3c/trace-context-protocols-registry#1 (1 comment by @SergeyKanzhelev)
-
w3c/baggage
-
2 issues opened.
-
Need to find a place for standard test suite w3c/baggage#9, by @reyang.
-
Need to have concrete ABNF syntax w3c/baggage#8, by @reyang.
-
-
1 issue closed.
-
Need to find a place for standard test suite w3c/baggage#9.
-
-
2 issues received 4 new comments.
-
Need to find a place for standard test suite w3c/baggage#9 (3 comments by @plehegar, @reyang, @SergeyKanzhelev)
-
w3c/distributed-tracing-wg
-
3 pull requests opened.
-
Meeting notes for 2019-02-19 w3c/distributed-tracing-wg#11, by @danielkhan.
-
Add link to meeting recordings w3c/distributed-tracing-wg#10, by @AloisReitbauer.
-
Meeting notes 2019-02-12 w3c/distributed-tracing-wg#9, by @danielkhan.
-
-
4 pull requests merged.
-
Meeting notes for 2019-02-19 w3c/distributed-tracing-wg#11.
-
Join the working group message w3c/distributed-tracing-wg#7.
-
Add link to meeting recordings w3c/distributed-tracing-wg#10.
-
Meeting notes 2019-02-12 w3c/distributed-tracing-wg#9.
-
-
1 pull request received 1 new comment.
GitHub
w3c/distributed-tracing-wg
-
2 pull requests opened.
-
Added minutes for 2019-01-15 w3c/distributed-tracing-wg#8, by @danielkhan.
-
Join the working group message w3c/distributed-tracing-wg#7, by @SergeyKanzhelev.
-
-
2 pull requests merged.
-
Add more goverance wording to the contribution.md w3c/distributed-tracing-wg#6.
-
Added minutes for 2019-01-15 w3c/distributed-tracing-wg#8.
-
-
1 pull request received 42 new comments.
-
Add more goverance wording to the contribution.md w3c/distributed-tracing-wg#6 (42 comments by @AloisReitbauer, @iredelmeier, @mtwo, @plehegar, @SergeyKanzhelev, @yurishkuro)
-
w3c/trace-context
-
11 issues opened.
-
Change wording of trace context propagation definition. w3c/trace-context#244, by @danielkhan.
-
Move mutations into processing model w3c/trace-context#240, by @danielkhan.
-
Header limits are obsolete and should be removed w3c/trace-context#239, by @danielkhan.
-
Decide, if we should explain OWS though we refer to the spec where it's defined w3c/trace-context#238, by @danielkhan.
-
Section on Recorded flag should be shorter and more precise w3c/trace-context#237, by @danielkhan.
-
Decide, if we want to mention span ID w3c/trace-context#236, by @danielkhan.
-
Decide, if we have to suggest an intrinsic format of trace-id w3c/trace-context#235, by @danielkhan.
-
Decide, if reuse of last trace ID in traceparent needs to be mentioned in spec w3c/trace-context#234, by @danielkhan.
-
Decide, if 'generic tracer' should be mentioned in intro example w3c/trace-context#233, by @danielkhan.
-
Decide, if generic tracer should be explained in HTTP Header Format w3c/trace-context#232, by @danielkhan.
-
Enable Rewrap or similar solution to limit the line width and simplify reviews w3c/trace-context#228, by @SergeyKanzhelev.
-
-
9 issues closed.
-
Decide, if we have to suggest an intrinsic format of trace-id w3c/trace-context#235.
-
Change wording of trace context propagation definition. w3c/trace-context#244.
-
Decide, if reuse of last trace ID in traceparent needs to be mentioned in spec w3c/trace-context#234.
-
Decide, if 'generic tracer' should be mentioned in intro example w3c/trace-context#233.
-
Decide, if we want to mention span ID w3c/trace-context#236.
-
Move mutations into processing model w3c/trace-context#240.
-
Decide, if we should explain OWS though we refer to the spec where it's defined w3c/trace-context#238.
-
HEXDIG has uppercase [A-F] w3c/trace-context#219.
-
Decide, if generic tracer should be explained in HTTP Header Format w3c/trace-context#232.
-
-
9 issues received 28 new comments.
-
Enable Rewrap or similar solution to limit the line width and simplify reviews w3c/trace-context#228 (12 comments by @AloisReitbauer, @danielkhan, @SergeyKanzhelev, @yurishkuro)
-
Decide, if we have to suggest an intrinsic format of trace-id w3c/trace-context#235 (3 comments by @AloisReitbauer, @danielkhan, @yurishkuro)
-
Decide, if we should explain OWS though we refer to the spec where it's defined w3c/trace-context#238 (3 comments by @AloisReitbauer, @SergeyKanzhelev)
-
Header limits are obsolete and should be removed w3c/trace-context#239 (3 comments by @AloisReitbauer, @danielkhan, @SergeyKanzhelev)
-
Decide, if 'generic tracer' should be mentioned in intro example w3c/trace-context#233 (2 comments by @AloisReitbauer, @danielkhan)
-
Decide, if reuse of last trace ID in traceparent needs to be mentioned in spec w3c/trace-context#234 (2 comments by @AloisReitbauer, @SergeyKanzhelev)
-
Section on Recorded flag should be shorter and more precise w3c/trace-context#237 (1 comment by @AloisReitbauer)
-
-
7 pull requests opened.
-
[WIP] MQTT format specification w3c/trace-context#245, by @SergeyKanzhelev.
-
[WIP] Editorial changes to HTTP Header Format w3c/trace-context#242, by @danielkhan.
-
WIP - CR HTTP Header Format. Editorial. w3c/trace-context#241, by @danielkhan.
-
Glossary section w3c/trace-context#231, by @SergeyKanzhelev.
-
use the lower case HEXDIGLC rule in abnf definition w3c/trace-context#229, by @SergeyKanzhelev.
-
-
7 pull requests merged.
-
[WIP] Editorial changes to HTTP Header Format w3c/trace-context#242.
-
- Fixes minor spelling- and grammar mistakes w3c/trace-context#224.
-
use the lower case HEXDIGLC rule in abnf definition w3c/trace-context#229.
-
Fix file case w3c/trace-context#226.
-
Fix link w3c/trace-context#230.
-
Improve grammar, spelling and structure of HTTP-Header Format and processing model w3c/trace-context#227.
-
Grammar, Spelling and wording w3c/trace-context#225.
-
-
1 pull request closed.
-
WIP - CR HTTP Header Format. Editorial. w3c/trace-context#241.
-
-
2 pull requests reopened.
-
WIP - CR HTTP Header Format. Editorial. w3c/trace-context#241, by @danielkhan.
-
WIP - CR HTTP Header Format. Editorial. w3c/trace-context#241, by @danielkhan.
-
-
12 pull requests received 96 new comments.
-
Add processing model to spec w3c/trace-context#222 (39 comments by @AloisReitbauer, @danielkhan, @mtwo, @SergeyKanzhelev, @yurishkuro)
-
- Fixes minor spelling- and grammar mistakes w3c/trace-context#224 (15 comments by @danielkhan, @mtwo, @yurishkuro)
-
Improve grammar, spelling and structure of HTTP-Header Format and processing model w3c/trace-context#227 (12 comments by @AloisReitbauer, @danielkhan, @SergeyKanzhelev)
-
AMQP draft: PR was moved to different repository w3c/trace-context#217 (10 comments by @calohmn, @clemensv, @SergeyKanzhelev, @yurishkuro)
-
Glossary section w3c/trace-context#231 (6 comments by @AloisReitbauer, @danielkhan, @SergeyKanzhelev, @yurishkuro)
-
[WIP] Changed abstract to define the problem we are solving and the proposed solution w3c/trace-context#221 (3 comments by @SergeyKanzhelev)
-
use the lower case HEXDIGLC rule in abnf definition w3c/trace-context#229 (3 comments by @AloisReitbauer, @SergeyKanzhelev)
-