- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 31 Mar 2020 17:00:55 +0000
- To: public-trace-context@w3.org
- Message-Id: <E1jJKFz-0007DZ-Va@uranus.w3.org>
Issues
------
* w3c/trace-context (+12/-14/💬38)
12 issues created:
- Clarify use of trace-id in response header (by dyladan)
https://github.com/w3c/trace-context/issues/407
- Remove proposed-parent-id from response header (by dyladan)
https://github.com/w3c/trace-context/issues/406
- Requirements for CORS safe-list (by dyladan)
https://github.com/w3c/trace-context/issues/405
- Fix numbering/level in rendered spec (by danielkhan)
https://github.com/w3c/trace-context/issues/403
- Make initial traceparent optional (by adriancole)
https://github.com/w3c/trace-context/issues/401
- [response header] Representing optional fields (by dyladan)
https://github.com/w3c/trace-context/issues/400
- [response header] Representing server span ID vs proposed parent ID (by dyladan)
https://github.com/w3c/trace-context/issues/399
- Should response header fields be optional? (by dyladan)
https://github.com/w3c/trace-context/issues/398
- Be consistent with normative / non-normative sections (by danielkhan)
https://github.com/w3c/trace-context/issues/396
- Can the intelligence-free nature of ids be confirmed or audited by external parties? (by danielkhan)
https://github.com/w3c/trace-context/issues/394
- Privacy: What information may be revealed? (by danielkhan)
https://github.com/w3c/trace-context/issues/393
- Define the intended implementer (by danielkhan)
https://github.com/w3c/trace-context/issues/392
23 issues received 38 new comments:
- #407 Clarify use of trace-id in response header (3 by dyladan, yurishkuro)
https://github.com/w3c/trace-context/issues/407
- #406 Remove proposed-parent-id from response header (4 by dyladan, yurishkuro)
https://github.com/w3c/trace-context/issues/406
- #405 Requirements for CORS safe-list (1 by danielkhan)
https://github.com/w3c/trace-context/issues/405 [security-tracker]
- #401 Make initial traceparent optional (2 by adriancole, danielkhan)
https://github.com/w3c/trace-context/issues/401
- #399 [response header] Representing server span ID vs proposed parent ID (6 by adriancole, dyladan, yurishkuro)
https://github.com/w3c/trace-context/issues/399
- #398 Should response header fields be optional? (3 by dyladan, yurishkuro)
https://github.com/w3c/trace-context/issues/398
- #392 Define the intended implementer (1 by mtwo)
https://github.com/w3c/trace-context/issues/392 [privacy-tracker]
- #390 Bogus trace and parent IDs when not sampling (1 by danielkhan)
https://github.com/w3c/trace-context/issues/390 [discuss-next-meeting]
- #389 W3C Trace Context only support HTTP protocol？ (1 by danielkhan)
https://github.com/w3c/trace-context/issues/389
- #387 Stop using vendor terminology (1 by danielkhan)
https://github.com/w3c/trace-context/issues/387
- #384 Discourage vendors from validating other vendors' tracestate entries (1 by SergeyKanzhelev)
https://github.com/w3c/trace-context/issues/384
- #369 Clarify handling of duplicate keys in tracestate (1 by danielkhan)
https://github.com/w3c/trace-context/issues/369 [discuss-next-meeting]
- #364 ABNF improvement (1 by danielkhan)
https://github.com/w3c/trace-context/issues/364 [editorial] [enhancement]
- #361 Create a first draft of a response header spec (1 by danielkhan)
https://github.com/w3c/trace-context/issues/361
- #353 We mention in joint blog post that opentelemetry is a reference implementation while readme says opencensus (1 by danielkhan)
https://github.com/w3c/trace-context/issues/353
- #348 Clarify "opaque" (1 by danielkhan)
https://github.com/w3c/trace-context/issues/348
- #343 Clarify: Should be the 32 list item limit be part of limits? (1 by danielkhan)
https://github.com/w3c/trace-context/issues/343
- #335 How multiple APMs in a process can "collaborate" on a given trace-context? (1 by danielkhan)
https://github.com/w3c/trace-context/issues/335
- #303 Edit 'Sampled Flag' section to be more concise. (1 by danielkhan)
https://github.com/w3c/trace-context/issues/303 [editorial]
- #296 Should implementation propagate flag it doesn't know about (1 by danielkhan)
https://github.com/w3c/trace-context/issues/296
- #279 Explain multi-graph pattern of tracestate (1 by danielkhan)
https://github.com/w3c/trace-context/issues/279 [discuss-next-meeting] [editorial]
- #120 IETF/IANA registration of header fields (3 by danielkhan, dyladan, plehegar)
https://github.com/w3c/trace-context/issues/120 [discuss-next-meeting] [todo] [w3c]
- #69 Investigate Server-Timing for passing back response headers (1 by danielkhan)
https://github.com/w3c/trace-context/issues/69
14 issues closed:
- [response header] Representing server span ID vs proposed parent ID https://github.com/w3c/trace-context/issues/399
- Discourage vendors from validating other vendors' tracestate entries https://github.com/w3c/trace-context/issues/384
- Unused file in spec directory https://github.com/w3c/trace-context/issues/363
- Create a first draft of a response header spec https://github.com/w3c/trace-context/issues/361
- We mention in joint blog post that opentelemetry is a reference implementation while readme says opencensus https://github.com/w3c/trace-context/issues/353
- Clarify: Should be the 32 list item limit be part of limits? https://github.com/w3c/trace-context/issues/343
- Edit 'Sampled Flag' section to be more concise. https://github.com/w3c/trace-context/issues/303 [editorial]
- Should implementation propagate flag it doesn't know about https://github.com/w3c/trace-context/issues/296
- Remove description on how to fill up shorter trace-ids https://github.com/w3c/trace-context/issues/262
- Should services in forward mode parse headers? https://github.com/w3c/trace-context/issues/251
- Integrate Timing Information in Trace-Context https://github.com/w3c/trace-context/issues/149
- Investigate Server-Timing for passing back response headers https://github.com/w3c/trace-context/issues/69
- Fix grammar in higher-version flags parsing https://github.com/w3c/trace-context/issues/368
- W3C Trace Context only support HTTP protocol？ https://github.com/w3c/trace-context/issues/389
* w3c/correlation-context (+2/-3/💬35)
2 issues created:
- Use simple value format and add version (by danielkhan)
https://github.com/w3c/correlation-context/issues/18
- Rename the header to Baggage (by SergeyKanzhelev)
https://github.com/w3c/correlation-context/issues/17
7 issues received 35 new comments:
- #17 Rename the header to Baggage (19 by JonathanMace, SergeyKanzhelev, adriancole, discostu105, dyladan, mtwo, mwear, rfonseca, shakuzen, tedsuo, yurishkuro)
https://github.com/w3c/correlation-context/issues/17
- #16 OpenTelemetry and Correlation Context (1 by SergeyKanzhelev)
https://github.com/w3c/correlation-context/issues/16
- #15 Consider using dictionary spec for the value (1 by danielkhan)
https://github.com/w3c/correlation-context/issues/15
- #13 Consider renaming the header from Correlation-Context to correlationcontext (10 by SergeyKanzhelev, adriancole, dyladan, felixbarny, mtwo, nicmunroe)
https://github.com/w3c/correlation-context/issues/13
- #10 Use cases for correlation context (2 by discostu105)
https://github.com/w3c/correlation-context/issues/10
- #6 Correlation Context Should be Split (1 by SergeyKanzhelev)
https://github.com/w3c/correlation-context/issues/6
- #3 Support for a type property of a Correlation Context value (1 by SergeyKanzhelev)
https://github.com/w3c/correlation-context/issues/3
3 issues closed:
- Consider using dictionary spec for the value https://github.com/w3c/correlation-context/issues/15
- Correlation Context Should be Split https://github.com/w3c/correlation-context/issues/6
- Support for a type property of a Correlation Context value https://github.com/w3c/correlation-context/issues/3
* w3c/distributed-tracing-wg (+5/-2/💬2)
5 issues created:
- March 2020 Online Workshop Notes (by dyladan)
https://github.com/w3c/distributed-tracing-wg/issues/33
- Review the charter (by danielkhan)
https://github.com/w3c/distributed-tracing-wg/issues/31
- Add an example of how tracestate will be used (by tigrannajaryan)
https://github.com/w3c/distributed-tracing-wg/issues/30
- Create structure for guides in /docs (by danielkhan)
https://github.com/w3c/distributed-tracing-wg/issues/29
- Explain multi-graph pattern of tracestate (by SergeyKanzhelev)
https://github.com/w3c/distributed-tracing-wg/issues/28
2 issues received 2 new comments:
- #30 Add an example of how tracestate will be used (1 by danielkhan)
https://github.com/w3c/distributed-tracing-wg/issues/30
- #27 Expected Completion dates (1 by SergeyKanzhelev)
https://github.com/w3c/distributed-tracing-wg/issues/27
2 issues closed:
- March 2020 Online Workshop Notes https://github.com/w3c/distributed-tracing-wg/issues/33
- Review the charter https://github.com/w3c/distributed-tracing-wg/issues/31
Pull requests
-------------
* w3c/trace-context (+4/-5/💬17)
4 pull requests submitted:
- Fixes wrong headline level of tracestate Header Field Values (by danielkhan)
https://github.com/w3c/trace-context/pull/404
- Update the status of the document in readme (by SergeyKanzhelev)
https://github.com/w3c/trace-context/pull/402
- Add Jaeger's Java implementation (by yurishkuro)
https://github.com/w3c/trace-context/pull/397
- Fix minor typo (by danielkhan)
https://github.com/w3c/trace-context/pull/395
2 pull requests received 17 new comments:
- #386 Clarifies the ABNF on tracestate keys (9 by SergeyKanzhelev, adriancole, basti1302, danielkhan, discostu105, felixbarny, yurishkuro)
https://github.com/w3c/trace-context/pull/386 [discuss-next-meeting]
- #365 Add response headers (8 by adriancole, dyladan, yurishkuro)
https://github.com/w3c/trace-context/pull/365 [discuss-next-meeting]
5 pull requests merged:
- Add Jaeger's Java implementation
https://github.com/w3c/trace-context/pull/397
- Add response headers
https://github.com/w3c/trace-context/pull/365 [discuss-next-meeting]
- Fix minor typo
https://github.com/w3c/trace-context/pull/395
- List Instana's current implementation
https://github.com/w3c/trace-context/pull/388
- Minor grammar fix
https://github.com/w3c/trace-context/pull/376
* w3c/correlation-context (+2/-0/💬1)
2 pull requests submitted:
- Add normative wording and use set-cookie value format (by danielkhan)
https://github.com/w3c/correlation-context/pull/20
- Add a version and further specification of value format (by danielkhan)
https://github.com/w3c/correlation-context/pull/19
1 pull requests received 1 new comments:
- #19 Add a version and further specification of value format (1 by danielkhan)
https://github.com/w3c/correlation-context/pull/19
* w3c/distributed-tracing-wg (+1/-0/💬0)
1 pull requests submitted:
- Feedback from March virtual meeting (by plehegar)
https://github.com/w3c/distributed-tracing-wg/pull/32
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/trace-context
* https://github.com/w3c/correlation-context
* https://github.com/w3c/distributed-tracing-wg
Received on Tuesday, 31 March 2020 17:01:00 UTC