- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 11 Jan 2022 17:00:50 +0000
- To: public-trace-context@w3.org
- Message-Id: <E1n7KVu-00075X-UD@uranus.w3.org>
Issues
------
* w3c/trace-context (+1/-3/💬0)
1 issues created:
- Incorrect randomness claim in 50-privacy.md (by dyladan)
https://github.com/w3c/trace-context/issues/481
3 issues closed:
- Clarify handling of duplicate keys in tracestate https://github.com/w3c/trace-context/issues/369 [workshop-fall-2020]
- Clarify tracestate keys MUST be unique https://github.com/w3c/trace-context/issues/446
- Expected behavior with regard to starting a trace should be spelled out explicitly https://github.com/w3c/trace-context/issues/442
Pull requests
-------------
* w3c/trace-context (+1/-2/💬0)
1 pull requests submitted:
- Remove incorrect randomness claim from privacy considerations (by dyladan)
https://github.com/w3c/trace-context/pull/482
2 pull requests merged:
- Specify uniqueness of tracestate keys as the sender's responsibility
https://github.com/w3c/trace-context/pull/477
- Specify expected behaviour when no traceparent is received
https://github.com/w3c/trace-context/pull/475
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/trace-context
* https://github.com/w3c/correlation-context
* https://github.com/w3c/distributed-tracing-wg
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 January 2022 17:00:52 UTC