Incomplete SpanContext type on npm
See original GitHub issueIt looks like the SpanContext
class definition in the published version is empty (i.e. missing toTraceId
and toSpanId
methods). Interestingly enough, when I build this locally the class definition that’s produced looks proper. Caching issue maybe?
published span_context.d.ts
:
export declare class SpanContext {
}
export default SpanContext;
locally built span_context.d.ts
:
export declare class SpanContext {
/**
* Returns a string representation of the implementation internal trace ID.
*
* @returns {string}
*/
toTraceId(): string;
/**
* Returns a string representation of the implementation internal span ID.
*
* @returns {string}
*/
toSpanId(): string;
}
export default SpanContext;
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Top 5 shimmer Code Examples - Snyk
Learn more about how to use shimmer, based on shimmer code examples created from the most popular ways it is used in public...
Read more >open-telemetry/opentelemetry-java - Gitter
@jkwatson no problem, I just find actual it has been streamed to the collector and export to zipkin and jaeger, but since there...
Read more >Manual Instrumentation | OpenTelemetry
OpenTelemetry provides a text-based approach to propagate context to remote services using ... Extract the SpanContext and other elements from the request.
Read more >@datafire/google_monitoring - npm
The filter may reference the type, labels, and metadata of ... errors that may have caused the time series data returned to be...
Read more >opentracing - Go Packages
New("opentracing: SpanContext type incompatible with tracer") // ErrInvalidCarrier errors occur when Tracer.Inject() or Tracer.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve published 0.14.4 to npm which fixes this issue, thanks!
what’s the approximate release date?