Roch Devost

@robaca I believe that was fixed a little while ago, maybe it was just not released. We're releasing 2.0 soon which will include everything on master, so I'd say to...

@duki994 We're working on refactoring our tests so that eventually we can test each integration with ESM, but this is a several months long project. In the meantime, can you...

We changed the default scope manager in 0.30.6, so it's likely that this is the issue. Can you try with 0.30.5, or otherwise if it's easier can you try with...

Can you provide a reproduction case? Otherwise, do you know the exact version when it started happening? There were quite a bit of changes between 0.26 and 0.36 so it's...

@tlhunter Do you still have the issue with the latest version?

> Could it be that some metadata that we're attaching is causing this issue? It's unlikely if it was working before. Are you able to pinpoint exactly in which version...

> I could send a private message with the output of npm ls in case a package is conflicting Sure, that might help although we're currently handling the ones we...

@Qard Sounds like this could be related to the issue we discussed offline this week about an unexpected span ending up as a parent of all request spans.

> The final solution would be if dd-trace has method for this function. I don't think this covers everything. Even if we were to expose everything that is needed by...

@icebob Any way you can simply create spans using the existing API? Unless I'm misunderstanding something I think our public API already offers what you need, as long as it's...