W3C home > Mailing lists > Public > public-trace-context@w3.org > February 2019

Weekly github digest (Distributed Tracing WG specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 12 Feb 2019 17:01:32 +0000
To: public-trace-context@w3.org
Message-Id: <E1gtbR6-0005O5-LG@uranus.w3.org>



Issues
------
* w3c/trace-context (+3/-5/💬12)
  3 issues created:
  - Should services in forward mode parse headers? (by danielkhan)
    https://github.com/w3c/trace-context/issues/251 
  - I think processing mode with only `tracestate` modification should be a valid case. It may be privacy-enforcing proxy or proxy that adds information about itself without touching `traceparent`. Like (potentially) service mesh scenario. (by danielkhan)
    https://github.com/w3c/trace-context/issues/250 
  - Mark "Other Protocols" section non-formative (by SergeyKanzhelev)
    https://github.com/w3c/trace-context/issues/247 [editorial] 

  10 issues received 12 new comments:
  - #193 Clarity on the definition of Span-id (2 by SergeyKanzhelev, chris-rogala)
    https://github.com/w3c/trace-context/issues/193 [editorial] 
  - #237 Section on Recorded flag should be shorter and more precise (2 by SergeyKanzhelev, danielkhan)
    https://github.com/w3c/trace-context/issues/237 [discuss-next-meeting] [editorial] 
  - #35 Additional Protocol Support (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/issues/35 
  - #165 Document procedures for spec changes (1 by AloisReitbauer)
    https://github.com/w3c/trace-context/issues/165 [w3c] 
  - #168 Value format section is confusing (1 by AloisReitbauer)
    https://github.com/w3c/trace-context/issues/168 [editorial] 
  - #109 Explain/remove 512 limit of tracestate in spec (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/issues/109 [discuss-next-meeting] 
  - #175 Action on tracestate header larger than 512 is confusing (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/issues/175 [enhancement] 
  - #218 Can a tracer/application only carry trace-parent and drop trace-state? (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/issues/218 [discuss-next-meeting] 
  - #251 Should services in forward mode parse headers? (1 by danielkhan)
    https://github.com/w3c/trace-context/issues/251 [discuss-next-meeting] 
  - #239 Header limits are obsolete and should be removed (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/issues/239 [discuss-next-meeting] [enhancement] 

  5 issues closed:
  - Action on tracestate header larger than 512 is confusing https://github.com/w3c/trace-context/issues/175 [enhancement] 
  - Explain/remove 512 limit of tracestate in spec https://github.com/w3c/trace-context/issues/109 [discuss-next-meeting] 
  - Can a tracer/application only carry trace-parent and drop trace-state? https://github.com/w3c/trace-context/issues/218 [discuss-next-meeting] 
  - Document procedures for spec changes https://github.com/w3c/trace-context/issues/165 [w3c] 
  - Clarity on the definition of Span-id https://github.com/w3c/trace-context/issues/193 [editorial] 



Pull requests
-------------
* w3c/trace-context (+2/-1/💬13)
  2 pull requests submitted:
  - Mark section non-informative (by SergeyKanzhelev)
    https://github.com/w3c/trace-context/pull/249 
  - Make tracestate limit the responsibility of a platform (by SergeyKanzhelev)
    https://github.com/w3c/trace-context/pull/248 

  5 pull requests received 13 new comments:
  - #246 Consolidates all work done on individual CR* branches (5 by SergeyKanzhelev, AloisReitbauer, danielkhan)
    https://github.com/w3c/trace-context/pull/246 [discuss-next-meeting] 
  - #248 Make tracestate limit the responsibility of a platform (5 by AloisReitbauer, danielkhan, bogdandrutu, yurishkuro)
    https://github.com/w3c/trace-context/pull/248 
  - #214 moved semantics-related notes in the semantics document (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/pull/214 
  - #243 Echidna (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/pull/243 
  - #222 Add processing model to spec (1 by danielkhan)
    https://github.com/w3c/trace-context/pull/222 [discuss-next-meeting] [substantive] 

  1 pull requests merged:
  - Echidna
    https://github.com/w3c/trace-context/pull/243 


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, 12 February 2019 17:01:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:36:41 UTC