W3C home > Mailing lists > Public > public-trace-context@w3.org > November 2021

Weekly github digest (Distributed Tracing WG specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 23 Nov 2021 17:00:57 +0000
To: public-trace-context@w3.org
Message-Id: <E1mpZA9-0000gt-K3@uranus.w3.org>



Issues
------
* w3c/trace-context (+0/-2/💬12)
  7 issues received 12 new comments:
  - #469 Release trace context level-1 (3 by basti1302, dyladan, plehegar)
    https://github.com/w3c/trace-context/issues/469 
  - #446 Clarify tracestate keys MUST be unique (2 by basti1302, dyladan)
    https://github.com/w3c/trace-context/issues/446 [discuss-next-meeting] 
  - #405 Requirements for CORS safe-list (1 by basti1302)
    https://github.com/w3c/trace-context/issues/405 [security-tracker] [workshop-fall-2020] 
  - #401 Make initial traceparent optional (2 by SergeyKanzhelev, kalyanaj)
    https://github.com/w3c/trace-context/issues/401 [revisit-later] 
  - #398 Should response header fields be optional? (1 by kalyanaj)
    https://github.com/w3c/trace-context/issues/398 [workshop-fall-2020] 
  - #396 Be consistent with normative / non-normative sections (1 by kalyanaj)
    https://github.com/w3c/trace-context/issues/396 [Editorial] [todo] 
  - #394 Can the intelligence-free nature of ids be confirmed or audited by external parties? (2 by kalyanaj, npdoty)
    https://github.com/w3c/trace-context/issues/394 [privacy-needs-resolution] [workshop-fall-2020] 

  2 issues closed:
  - Can the intelligence-free nature of ids be confirmed or audited by external parties? https://github.com/w3c/trace-context/issues/394 [privacy-needs-resolution] [workshop-fall-2020] 
  - Should response header fields be optional? https://github.com/w3c/trace-context/issues/398 [workshop-fall-2020] 



Pull requests
-------------
* w3c/trace-context (+0/-1/💬12)
  4 pull requests received 12 new comments:
  - #480 An alternative proposal on implementing randomness by updating level … (2 by SergeyKanzhelev, yurishkuro)
    https://github.com/w3c/trace-context/pull/480 
  - #479 must->should for keys mutation fix up (1 by dyladan)
    https://github.com/w3c/trace-context/pull/479 [trace-context-1] 
  - #475 Specify expected behaviour when no traceparent is received (1 by basti1302)
    https://github.com/w3c/trace-context/pull/475 
  - #474 Add the random trace id flag (8 by dyladan, yurishkuro)
    https://github.com/w3c/trace-context/pull/474 

  1 pull requests merged:
  - must->should for keys mutation fix up
    https://github.com/w3c/trace-context/pull/479 [trace-context-1] 


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, 23 November 2021 17:01:00 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:58 UTC