Closed cristiboariu closed 2 years ago
@yurishkuro can you please help? Our PROD build is no longer working :(
Bug seems to be introduced here: https://github.com/opentracing/opentracing-javascript/commit/1380d0ffab6401fed9cdaabdcb88f2edf1b3c7dd#diff-d0d962ccc0784d6699fb4dcfc79d3acd8cff4d081f77e13a164510c48459d35fR14
we are experiencing the same issue. non-stop uncaught exceptions in some of our services (opentracing
is pulled in by those services' dd-trace
dependency)
Seeing this as well
@yurishkuro Just want to make sure you are aware. We are currently trying to force a rollback to v0.14.5 in our systems as we currently can't deploy any new code.
dd-trace datadogs agent uses this dependency and we can not deploy any code now. this is a major issue.
apologies, everyone, I am reverting the change in a new patch
opentracing@0.14.7 published that is equal to opentracing@0.14.5
btw, I think the original null-ptr issue is here: https://github.com/DataDog/dd-trace-js/blob/21179be27f7f9487e8287056fa08e404f5e6ef14/packages/datadog-plugin-http/src/client.js#L54
This code is calling new Reference(type, parentCtx)
constructor with parentCtx=null
, which is invalid per constructor signature: https://github.com/opentracing/opentracing-javascript/blob/9a4856ef20597c1a1a2ffc4072dd9a497af22b8d/src/reference.ts#L57
While not ideal, #174 adds support for previous "illegal" usage of the constructor.
I was facing this issue as well and can confirm that the 0.14.7 build fixes the problem. I was about to post this exact issue with the suggestion that the line in question add a null/undefined check...but, without digging further, that may just kick the problem further downstream
@cristiboariu @lmuench @jneal-afs @amopportunities @dhay can you test your code with PR #174 (it's on a public branch) to confirm if it resolves the issue?
After your latest release (v0.14.6) we encounter: