Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Readme not up to date
See original GitHub issueLooks like the suggested tracing.ts mentioned in the Readme is not up to date.
HttpTraceContextPropagator needs to be W3CTraceContextPropagator
HttpBaggagePropagator needs to be W3CBaggagePropagator
import { BatchSpanProcessor } from '@opentelemetry/tracing'; needs to be import {BatchSpanProcessor} from '@opentelemetry/sdk-trace-base';
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
README not up to date for the section "Compatibility ... - GitHub
Hello, This is not a software bug, but more a documentation "bug" in the README. It's writen in section "Compatibility Clarifications" I ...
Read more >Why can I not commit? (Your branch is up-to-date with 'origin ...
README.md was a tracked file, but you deleted without using git rm README.md . Git detects that the file has been deleted, but...
Read more >Keep Your README Install Instructions Up To Date - DockYard
Keep Your README Install Instructions Up To Date ... Install version constraint in README.md does not match to current app version.
Read more >Are you supposed to keep the up to date README file in your ...
I try not making more than 3 candidates, doing so results in the least viable for stability to be deleted. It sounds a...
Read more >Readme.txt not up to date (#246) · Issues - 3GPP Forge
The readme.txt file in the main project folder is not up to date at least wrt.: recent updates in self-test scripts and tests....
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 Free
Top 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
As always is the way, I found the solution almost immediately after posting. The opentelemetry packages need to be pinned to
<1.1.0as1.1.0isn’t compatible with@opentelemetry/sdk-nodewhich hasn’t been updated yet.FYI, this full example has the new changes https://github.com/pragmaticivan/nestjs-otel/blob/c11cfa377df82ac8443a5cd95790e6d499b823d8/examples/nestjs-prom-grafana-tempo/src/tracing.ts