- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2022 17:01:09 +0000
- To: public-trace-context@w3.org
- Message-Id: <E1oiIcv-00GY2g-JK@uranus.w3.org>
Issues
------
* w3c/correlation-context (+0/-2/💬0)
2 issues closed:
- Clarify Baggage Propagation Limits https://github.com/w3c/baggage/issues/108
- limitations do not appear to have standard implementation for enforcement https://github.com/w3c/baggage/issues/30 [workshop-fall-2020]
Pull requests
-------------
* w3c/trace-context (+0/-1/💬0)
1 pull requests merged:
- Level 2 tweaks
https://github.com/w3c/trace-context/pull/497 [Editorial] [ready-for-review]
* w3c/correlation-context (+0/-1/💬3)
2 pull requests received 3 new comments:
- #113 Clarify what happens when limits are violated (1 by dyladan)
https://github.com/w3c/baggage/pull/113
- #111 Add note that applications using baggage must be aware that data can be propagated to other systems (2 by kalyanaj, pes10k)
https://github.com/w3c/baggage/pull/111
1 pull requests merged:
- Clarify what happens when limits are violated
https://github.com/w3c/baggage/pull/113
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 October 2022 17:01:11 UTC