Distributed Tracing Working Group - Activity in 2018
No matches.
Participants
-
1 organization joined.
-
Adobe joined.
-
GitHub
w3c/trace-context
-
3 issues opened.
-
Behaviour for invalid headers in forwarding mode not defined w3c/trace-context#220, by @AloisReitbauer.
-
HEXDIG has uppercase [A-F] w3c/trace-context#219, by @bogdandrutu.
-
Can a tracer/application only carry trace-parent and drop trace-state? w3c/trace-context#218, by @AloisReitbauer.
-
-
2 issues closed.
-
Compatibility and Interoperability Test Suite w3c/trace-context#87.
-
How does the trace-context distinguish "child of" from "follows from"? w3c/trace-context#202.
-
-
6 issues received 9 new comments.
-
w3c/trace-context#120 (3 comments by @plehegar)
-
w3c/trace-context#87 (1 comment by @SergeyKanzhelev)
-
How does the trace-context distinguish "child of" from "follows from"? w3c/trace-context#202 (1 comment by @smullins3000)
-
Privacy risk if trace context is used as response headers in cross-origin calls w3c/trace-context#209 (1 comment by @plehegar)
-
-
12 pull requests opened.
-
Improve grammar, spelling and structure of HTTP-Header Format and processing model w3c/trace-context#227, by @danielkhan.
-
Fix file case w3c/trace-context#226, by @danielkhan.
-
Grammar, Spelling and wording w3c/trace-context#225, by @danielkhan.
-
- Fixes minor spelling- and grammar mistakes w3c/trace-context#224, by @danielkhan.
-
Update privacy statement for CR readiness w3c/trace-context#223, by @AloisReitbauer.
-
Add processing model to spec w3c/trace-context#222, by @AloisReitbauer.
-
[WIP] Changed abstract to define the problem we are solving and the proposed solution w3c/trace-context#221, by @AloisReitbauer.
-
AMQP draft: PR was moved to different repository w3c/trace-context#217, by @SergeyKanzhelev.
-
[WIP] Rework spec an get ready for CR w3c/trace-context#216, by @AloisReitbauer.
-
Draft of binary format: moved to other repository w3c/trace-context#215, by @SergeyKanzhelev.
-
moved semantics-related notes in the semantics document w3c/trace-context#214, by @SergeyKanzhelev.
-
Restructure: placeholders for other protocols w3c/trace-context#213, by @SergeyKanzhelev.
-
-
1 pull request merged.
-
Restructure: placeholders for other protocols w3c/trace-context#213.
-
-
1 pull request closed.
-
[WIP] Rework spec an get ready for CR w3c/trace-context#216.
-
-
5 pull requests received 58 new comments.
-
[WIP] Rework spec an get ready for CR w3c/trace-context#216 (35 comments by @AloisReitbauer, @SergeyKanzhelev)
-
Draft of binary format: moved to other repository w3c/trace-context#215 (16 comments by @SergeyKanzhelev, @watson, @yurishkuro)
-
Restructure: placeholders for other protocols w3c/trace-context#213 (4 comments by @AloisReitbauer, @SergeyKanzhelev)
-
moved semantics-related notes in the semantics document w3c/trace-context#214 (1 comment by @SergeyKanzhelev)
-
w3c/baggage
-
1 pull request opened.
-
Fix typo in w3c.json w3c/baggage#7, by @dontcallmedom.
-
-
1 pull request merged.
-
Fix typo in w3c.json w3c/baggage#7.
-
w3c/distributed-tracing-wg
-
2 pull requests opened.
-
Add more goverance wording to the contribution.md w3c/distributed-tracing-wg#6, by @AloisReitbauer.
-
Replace link to calendar with one that does not require Google login w3c/distributed-tracing-wg#5, by @dontcallmedom.
-
-
1 pull request merged.
-
Replace link to calendar with one that does not require Google login w3c/distributed-tracing-wg#5.
-
TR publications
-
2 documents published.
-
Trace Context published as a Working Draft. History of Trace Context
-
Trace Context published as a First Public Working Draft. History of Trace Context
-
Participants
-
1 participant joined.
-
Yuri Shkuro (Meta) joined.
-
-
1 organization joined.
-
New Relic, Inc. joined.
-
GitHub
w3c/trace-context
-
7 issues opened.
-
Test case for invalid traceparent restart should validate that all children has the same ID w3c/trace-context#211, by @SergeyKanzhelev.
-
Mechanism to audit randomness of trace-id w3c/trace-context#210, by @SergeyKanzhelev.
-
Privacy risk if trace context is used as response headers in cross-origin calls w3c/trace-context#209, by @SergeyKanzhelev.
-
Replace "span" nomenclature w3c/trace-context#205, by @yurishkuro.
-
Graph construction is unclear with current form of traceparent / tracestate w3c/trace-context#204, by @falenn.
-
abstract needs editing w3c/trace-context#203, by @dret.
-
How does the trace-context distinguish "child of" from "follows from"? w3c/trace-context#202, by @smullins3000.
-
-
9 issues closed.
-
Replace "span" nomenclature w3c/trace-context#205.
-
discuss where to place reference implementations w3c/trace-context#169.
-
Let's discuss recorded flag before FPWD announcement w3c/trace-context#167.
-
What to do when malformed headers are received? w3c/trace-context#172.
-
What to do when empty tracestate? w3c/trace-context#171.
-
Correlation Context Should be Split w3c/trace-context#36.
-
Support for a PII property of a Correlation Context value w3c/trace-context#24.
-
One level down correlation context propagation (TTL=1) w3c/trace-context#23.
-
Support for a type property of a Correlation Context value w3c/trace-context#22.
-
-
13 issues received 35 new comments.
-
Replace "span" nomenclature w3c/trace-context#205 (6 comments by @AloisReitbauer, @falenn, @SergeyKanzhelev, @yurishkuro)
-
Question on test-harness cases around invalid tracestate w3c/trace-context#195 (5 comments by @reyang, @SergeyKanzhelev)
-
Graph construction is unclear with current form of traceparent / tracestate w3c/trace-context#204 (4 comments by @falenn, @roncohen, @yurishkuro)
-
How does the trace-context distinguish "child of" from "follows from"? w3c/trace-context#202 (2 comments by @AloisReitbauer, @yurishkuro)
-
discuss where to place reference implementations w3c/trace-context#169 (1 comment by @SergeyKanzhelev)
-
Let's discuss recorded flag before FPWD announcement w3c/trace-context#167 (1 comment by @SergeyKanzhelev)
-
What to do when malformed headers are received? w3c/trace-context#172 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#36 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#24 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#23 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#22 (1 comment by @SergeyKanzhelev)
-
7 pull requests opened.
-
Fixing typo's w3c/trace-context#212, by @ryanspletzer.
-
no span nomenclature w3c/trace-context#208, by @SergeyKanzhelev.
-
simply aligned the line width w3c/trace-context#207, by @SergeyKanzhelev.
-
Fixes shortName for w3c publication w3c/trace-context#206, by @plehegar.
-
mention cloud events w3c/trace-context#201, by @SergeyKanzhelev.
-
support STRICT_LEVEL environment variable w3c/trace-context#200, by @reyang.
-
Update docs w3c/trace-context#199, by @chenrui333.
-
-
9 pull requests merged.
-
no span nomenclature w3c/trace-context#208.
-
Fixing typo's w3c/trace-context#212.
-
simply aligned the line width w3c/trace-context#207.
-
Fixes shortName for w3c publication w3c/trace-context#206.
-
mention cloud events w3c/trace-context#201.
-
support STRICT_LEVEL environment variable w3c/trace-context#200.
-
failure to parse clarification (already covered in tests) w3c/trace-context#191.
-
allow empty headers w3c/trace-context#188.
-
Update docs w3c/trace-context#199.
-
-
4 pull requests received 5 new comments.
-
support STRICT_LEVEL environment variable w3c/trace-context#200 (2 comments by @reyang, @SergeyKanzhelev)
-
failure to parse clarification (already covered in tests) w3c/trace-context#191 (1 comment by @SergeyKanzhelev)
-
w3c/distributed-tracing-wg
-
1 issue opened.
-
Where test suite should be located at? w3c/distributed-tracing-wg#2, by @SergeyKanzhelev.
-
-
1 issue closed.
-
Where test suite should be located at? w3c/distributed-tracing-wg#2.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
w3c privacy group meeting w3c/distributed-tracing-wg#4, by @SergeyKanzhelev.
-
Remove tests. See individual spec repos w3c/distributed-tracing-wg#3, by @plehegar.
-
added TPAC minutes w3c/distributed-tracing-wg#1, by @SergeyKanzhelev.
-
-
3 pull requests merged.
-
w3c privacy group meeting w3c/distributed-tracing-wg#4.
-
Remove tests. See individual spec repos w3c/distributed-tracing-wg#3.
-
added TPAC minutes w3c/distributed-tracing-wg#1.
-
-
1 pull request received 1 new comment.
w3c/trace-context-protocols-registry
-
1 issue received 6 new comments.
-
Tracing propagation over plain TLS w3c/trace-context-protocols-registry#5 (6 comments by @falenn, @james-callahan)
-
w3c/baggage
-
4 issues opened.
-
Correlation Context Should be Split w3c/baggage#6, by @SergeyKanzhelev.
-
Support for a PII property of a Correlation Context value w3c/baggage#5, by @SergeyKanzhelev.
-
One level down correlation context propagation (TTL=1) w3c/baggage#4, by @SergeyKanzhelev.
-
Support for a type property of a Correlation Context value w3c/baggage#3, by @SergeyKanzhelev.
-
-
2 pull requests opened.
-
fix issues after refactoring of repos w3c/baggage#2, by @SergeyKanzhelev.
-
+ link to header format w3c/baggage#1, by @ericprud.
-
-
1 pull request closed.
-
+ link to header format w3c/baggage#1.
-
-
1 pull request received 2 new comments.
GitHub
w3c/trace-context
-
4 issues opened.
-
Use IETF Dictionary for tracestate w3c/trace-context#197, by @discostu105.
-
Question on test-harness cases around invalid tracestate w3c/trace-context#195, by @discostu105.
-
Trace-id and Span-id - What makes up valid bytes? w3c/trace-context#194, by @chris-rogala.
-
Clarity on the definition of Span-id w3c/trace-context#193, by @chris-rogala.
-
-
1 issue closed.
-
Change in example's tracestate value is confusing w3c/trace-context#181.
-
-
5 issues received 22 new comments.
-
Use IETF Dictionary for tracestate w3c/trace-context#197 (8 comments by @AloisReitbauer, @discostu105, @mtwo, @SergeyKanzhelev, @yurishkuro)
-
Clarity on the definition of Span-id w3c/trace-context#193 (8 comments by @basvanbeek, @chris-rogala, @yurishkuro)
-
Question on test-harness cases around invalid tracestate w3c/trace-context#195 (2 comments by @discostu105, @reyang)
-
-
6 pull requests opened.
-
Don't allow spaces in tracestate to make parsing easier w3c/trace-context#196, by @AloisReitbauer.
-
export test data in JSON format w3c/trace-context#192, by @reyang.
-
failure to parse clarification (already covered in tests) w3c/trace-context#191, by @SergeyKanzhelev.
-
Editorial: fix the list in markdown w3c/trace-context#190, by @SergeyKanzhelev.
-
fix example - = is not allowed as a tracestate entry value w3c/trace-context#189, by @SergeyKanzhelev.
-
allow empty headers w3c/trace-context#188, by @SergeyKanzhelev.
-
-
4 pull requests merged.
-
Editorial: fix the list in markdown w3c/trace-context#190.
-
fix example - = is not allowed as a tracestate entry value w3c/trace-context#189.
-
export test data in JSON format w3c/trace-context#192.
-
switch to a single recorded flag w3c/trace-context#180.
-
-
1 pull request closed.
-
Don't allow spaces in tracestate to make parsing easier w3c/trace-context#196.
-
-
5 pull requests received 22 new comments.
-
allow empty headers w3c/trace-context#188 (13 comments by @AloisReitbauer, @discostu105, @SergeyKanzhelev, @yurishkuro)
-
Don't allow spaces in tracestate to make parsing easier w3c/trace-context#196 (5 comments by @discostu105, @reyang)
-
failure to parse clarification (already covered in tests) w3c/trace-context#191 (2 comments by @reyang, @zoidyzoidzoid)
-
w3c/trace-context-protocols-registry
-
1 issue opened.
-
Tracing propagation over plain TLS w3c/trace-context-protocols-registry#5, by @james-callahan.
-
Participants
-
1 organization joined.
-
Google LLC joined.
-
GitHub
w3c/trace-context
-
2 issues opened.
-
Change in example's tracestate value is confusing w3c/trace-context#181, by @sdboyer-stripe.
-
Action on tracestate header larger than 512 is confusing w3c/trace-context#175, by @rghetia.
-
-
1 issue closed.
-
which mailing list to use w3c/trace-context#152.
-
-
1 issue reopened.
-
Let's discuss recorded flag before FPWD announcement w3c/trace-context#167, by @bogdandrutu.
-
-
9 issues received 23 new comments.
-
Let's discuss recorded flag before FPWD announcement w3c/trace-context#167 (12 comments by @AloisReitbauer, @bogdandrutu, @discostu105, @SergeyKanzhelev, @yurishkuro)
-
What to do when malformed headers are received? w3c/trace-context#172 (2 comments by @reyang, @rghetia)
-
Action on tracestate header larger than 512 is confusing w3c/trace-context#175 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#109 (1 comment by @discostu105)
-
-
12 pull requests opened.
-
add CI badges w3c/trace-context#187, by @reyang.
-
Do Not Merge w3c/trace-context#186, by @reyang.
-
integrate with Travis CI w3c/trace-context#185, by @reyang.
-
return error code for test results w3c/trace-context#184, by @reyang.
-
fix tracestate sample w3c/trace-context#183, by @reyang.
-
adjust OWS implementation to meet with RFC7230 w3c/trace-context#182, by @reyang.
-
switch to a single recorded flag w3c/trace-context#180, by @SergeyKanzhelev.
-
As we moved to CR milestone - clarifying the status of specs w3c/trace-context#179, by @SergeyKanzhelev.
-
Update 2018-09-11.md w3c/trace-context#178, by @SergeyKanzhelev.
-
add meeting notes for w3c call 2018-09-11 w3c/trace-context#177, by @discostu105.
-
add tracestate test w3c/trace-context#176, by @reyang.
-
add more test cases, improve debug output w3c/trace-context#174, by @reyang.
-
-
11 pull requests merged.
-
add CI badges w3c/trace-context#187.
-
integrate with Travis CI w3c/trace-context#185.
-
fix tracestate sample w3c/trace-context#183.
-
return error code for test results w3c/trace-context#184.
-
adjust OWS implementation to meet with RFC7230 w3c/trace-context#182.
-
Update 2018-09-11.md w3c/trace-context#178.
-
As we moved to CR milestone - clarifying the status of specs w3c/trace-context#179.
-
add tracestate test w3c/trace-context#176.
-
add meeting notes for w3c call 2018-09-11 w3c/trace-context#177.
-
add more test cases, improve debug output w3c/trace-context#174.
-
Implement Test Harness w3c/trace-context#166.
-
-
2 pull requests closed.
-
Do Not Merge w3c/trace-context#186.
-
Add clarification for #142 w3c/trace-context#162.
-
-
6 pull requests received 19 new comments.
-
Implement Test Harness w3c/trace-context#166 (10 comments by @discostu105, @NatalieWolfe, @reyang, @SergeyKanzhelev)
-
As we moved to CR milestone - clarifying the status of specs w3c/trace-context#179 (1 comment by @bogdandrutu)
-
Participants
-
1 organization joined.
-
Dynatrace LLC joined.
-
GitHub
w3c/trace-context
-
11 issues opened.
-
What to do when malformed headers are received? w3c/trace-context#172, by @bogdandrutu.
-
What to do when empty tracestate? w3c/trace-context#171, by @bogdandrutu.
-
discuss where to place reference implementations w3c/trace-context#169, by @SergeyKanzhelev.
-
Value format section is confusing w3c/trace-context#168, by @bogdandrutu.
-
Let's discuss recorded flag before FPWD announcement w3c/trace-context#167, by @SergeyKanzhelev.
-
Document procedures for spec changes w3c/trace-context#165, by @yurishkuro.
-
which mailing list to use w3c/trace-context#152, by @SergeyKanzhelev.
-
Integrate Timing Information in Trace-Context w3c/trace-context#149, by @AloisReitbauer.
-
Do we need a response header? w3c/trace-context#148, by @AloisReitbauer.
-
How and when are you allowed to restart a trace w3c/trace-context#146, by @AloisReitbauer.
-
Leading zeroes for smaller trace-id. Should it be documented? w3c/trace-context#140, by @SergeyKanzhelev.
-
-
15 issues closed.
-
Position zero in tracestate identifies the traceparent w3c/trace-context#80.
-
Allow to mutate mutliple keys of tracestate w3c/trace-context#117.
-
Structure of TraceState w3c/trace-context#123.
-
Allow multiple tracestate entries for one vendor w3c/trace-context#137.
-
Define behavior for response header context propagation w3c/trace-context#50.
-
Do we need a response header? w3c/trace-context#148.
-
charter could be clearer about who the expected implementers are w3c/trace-context#126.
-
Do we need sampling to be more than one bit in trace-parent to define priority w3c/trace-context#8.
-
Is the W3C 3-clause BSD License acceptable for integration tests? w3c/trace-context#94.
-
Leading zeroes for smaller trace-id. Should it be documented? w3c/trace-context#140.
-
Define behavior when library do not understand the version number w3c/trace-context#54.
-
Do we need a sampling bit in trace-parent? w3c/trace-context#122.
-
Are traceparent fields optional or fixed width? w3c/trace-context#115.
-
Find alternative meeting time w3c/trace-context#92.
-
-
18 issues received 56 new comments.
-
Leading zeroes for smaller trace-id. Should it be documented? w3c/trace-context#140 (10 comments by @codefromthecrypt, @SergeyKanzhelev, @yurishkuro)
-
which mailing list to use w3c/trace-context#152 (6 comments by @plehegar, @SergeyKanzhelev, @yurishkuro)
-
Allow multiple tracestate entries for one vendor w3c/trace-context#137 (6 comments by @codefromthecrypt, @discostu105, @SergeyKanzhelev)
-
Let's discuss recorded flag before FPWD announcement w3c/trace-context#167 (5 comments by @AloisReitbauer, @bogdandrutu, @codefromthecrypt, @SergeyKanzhelev)
-
discuss where to place reference implementations w3c/trace-context#169 (5 comments by @AloisReitbauer, @bogdandrutu, @codefromthecrypt, @SergeyKanzhelev, @yurishkuro)
-
Integrate Timing Information in Trace-Context w3c/trace-context#149 (2 comments by @SergeyKanzhelev, @yurishkuro)
-
Do we need a response header? w3c/trace-context#148 (2 comments by @codefromthecrypt, @SergeyKanzhelev)
-
w3c/trace-context#87 (2 comments by @SergeyKanzhelev)
-
What to do when malformed headers are received? w3c/trace-context#172 (1 comment by @AloisReitbauer)
-
w3c/trace-context#80 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#55 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#8 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#94 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#115 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context#92 (1 comment by @AloisReitbauer)
-
-
25 pull requests opened.
-
WIP: Trace Context Language Cleanup w3c/trace-context#173, by @nikmd23.
-
Create 2018-0-28.md w3c/trace-context#170, by @AloisReitbauer.
-
Implement Test Harness w3c/trace-context#166, by @reyang.
-
explanation why mutations of tracestate are not required w3c/trace-context#164, by @SergeyKanzhelev.
-
update status of the document to FPWD. Working towards completing thi… w3c/trace-context#163, by @SergeyKanzhelev.
-
Add clarification for #142 w3c/trace-context#162, by @SergeyKanzhelev.
-
Some minor corrections to grammar w3c/trace-context#161, by @tomsugden.
-
Update charter.html after Ian's feedback w3c/trace-context#160, by @SergeyKanzhelev.
-
demand hex for span-id and trace-id w3c/trace-context#159, by @SergeyKanzhelev.
-
added ordering rationale: w3c/trace-context#158, by @SergeyKanzhelev.
-
Language about security risks w3c/trace-context#157, by @SergeyKanzhelev.
-
notes from implementors workshop w3c/trace-context#156, by @SergeyKanzhelev.
-
Fix minor typo w3c/trace-context#155, by @jlian.
-
Various tweaks for a new WG w3c/trace-context#154, by @plehegar.
-
Allow @ in tracestate key names for multi-tenant vendors w3c/trace-context#153, by @SergeyKanzhelev.
-
cosmetics w3c/trace-context#151, by @SergeyKanzhelev.
-
response headers rationale w3c/trace-context#150, by @SergeyKanzhelev.
-
added browsers and mobile apps into the charter w3c/trace-context#147, by @SergeyKanzhelev.
-
rename options to flags w3c/trace-context#145, by @SergeyKanzhelev.
-
Fix changed Trace-Id that confused the example w3c/trace-context#144, by @danielkhan.
-
add wording about keeping random value right w3c/trace-context#143, by @SergeyKanzhelev.
-
Change traced flag semantics and add recorded flag w3c/trace-context#142, by @erabug.
-
versioning proposal during the implemetors workshop w3c/trace-context#141, by @SergeyKanzhelev.
-
Add instana as known implementation w3c/trace-context#139, by @SergeyKanzhelev.
-
update milestones in charter w3c/trace-context#138, by @SergeyKanzhelev.
-
-
22 pull requests merged.
-
WIP: Trace Context Language Cleanup w3c/trace-context#173.
-
Create 2018-0-28.md w3c/trace-context#170.
-
explanation why mutations of tracestate are not required w3c/trace-context#164.
-
update status of the document to FPWD. Working towards completing thi… w3c/trace-context#163.
-
added ordering rationale: w3c/trace-context#158.
-
Update charter.html after Ian's feedback w3c/trace-context#160.
-
Some minor corrections to grammar w3c/trace-context#161.
-
demand hex for span-id and trace-id w3c/trace-context#159.
-
Language about security risks w3c/trace-context#157.
-
notes from implementors workshop w3c/trace-context#156.
-
Fix minor typo w3c/trace-context#155.
-
Various tweaks for a new WG w3c/trace-context#154.
-
Allow @ in tracestate key names for multi-tenant vendors w3c/trace-context#153.
-
cosmetics w3c/trace-context#151.
-
response headers rationale w3c/trace-context#150.
-
added browsers and mobile apps into the charter w3c/trace-context#147.
-
rename options to flags w3c/trace-context#145.
-
update milestones in charter w3c/trace-context#138.
-
Fix changed Trace-Id that confused the example w3c/trace-context#144.
-
add wording about keeping random value right w3c/trace-context#143.
-
Change traced flag semantics and add recorded flag w3c/trace-context#142.
-
versioning proposal during the implemetors workshop w3c/trace-context#141.
-
-
1 pull request closed.
-
Add instana as known implementation w3c/trace-context#139.
-
-
1 pull request reopened.
-
Update charter.html after Ian's feedback w3c/trace-context#160, by @SergeyKanzhelev.
-
-
11 pull requests received 64 new comments.
-
Language about security risks w3c/trace-context#157 (14 comments by @mtwo, @SergeyKanzhelev, @yurishkuro)
-
versioning proposal during the implemetors workshop w3c/trace-context#141 (13 comments by @AloisReitbauer, @codefromthecrypt, @SergeyKanzhelev, @yurishkuro)
-
Add clarification for #142 w3c/trace-context#162 (10 comments by @AloisReitbauer, @codefromthecrypt, @SergeyKanzhelev)
-
Change traced flag semantics and add recorded flag w3c/trace-context#142 (8 comments by @codefromthecrypt, @discostu105, @justindsmith, @SergeyKanzhelev)
-
Allow @ in tracestate key names for multi-tenant vendors w3c/trace-context#153 (7 comments by @codefromthecrypt, @discostu105, @SergeyKanzhelev)
-
Implement Test Harness w3c/trace-context#166 (3 comments by @NatalieWolfe, @reyang, @SergeyKanzhelev)
-
Add instana as known implementation w3c/trace-context#139 (3 comments by @bripkens, @SergeyKanzhelev)
-
WIP: Trace Context Language Cleanup w3c/trace-context#173 (2 comments by @nikmd23, @SergeyKanzhelev)
-
explanation why mutations of tracestate are not required w3c/trace-context#164 (1 comment by @SergeyKanzhelev)
-
Lifecycle
-
1 charter started.
-
Chartered until 30 April 2020. Participants had to rejoin under this charter.
-
Participants
-
1 participant joined.
-
Philippe Le Hegaret (W3C) joined.
-
-
1 organization joined.
-
Microsoft Corporation joined.
-
GitHub
w3c/trace-context
-
1 issue opened.
-
Allow multiple tracestate entries for one vendor w3c/trace-context#137, by @discostu105.
-
-
1 issue received 9 new comments.
-
Allow multiple tracestate entries for one vendor w3c/trace-context#137 (9 comments by @codefromthecrypt, @discostu105, @yurishkuro)
-
-
1 pull request merged.
-
Change reports from CG to WG w3c/trace-context#136.
-