- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 13 Dec 2022 17:00:57 +0000
- To: public-trace-context@w3.org
- Message-Id: <E1p58eH-002p44-2S@uranus.w3.org>
Issues
------
* w3c/trace-context (+0/-3/💬2)
1 issues received 2 new comments:
- #508 Why should keys be restricted to lowercase ASCII? (2 by aphillips, basti1302)
https://github.com/w3c/trace-context/issues/508 [i18n-needs-resolution]
3 issues closed:
- Version number relationship to ASCII and UTF-8 https://github.com/w3c/trace-context/issues/507 [i18n-needs-resolution]
- specification of lowercase is incomplete https://github.com/w3c/trace-context/issues/506 [i18n-needs-resolution]
- Why should keys be restricted to lowercase ASCII? https://github.com/w3c/trace-context/issues/508 [i18n-needs-resolution]
Pull requests
-------------
* w3c/trace-context (+0/-4/💬1)
1 pull requests received 1 new comments:
- #515 add reasoning for the restriction of tracestate keys (1 by basti1302)
https://github.com/w3c/trace-context/pull/515 [Editorial] [backport-to-level-2]
4 pull requests merged:
- improve description of version field in traceparent request header
https://github.com/w3c/trace-context/pull/511 [Editorial] [backport-to-level-2]
- improve wording for casing of request header names
https://github.com/w3c/trace-context/pull/513 [Editorial] [backport-to-level-2]
- improve description of version field in traceresponse header
https://github.com/w3c/trace-context/pull/512 [Editorial]
- improve wording for casing of response header name
https://github.com/w3c/trace-context/pull/514 [Editorial]
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, 13 December 2022 17:00:58 UTC