All customs spans broken in Puter after upgrading opentelemetry

[KernelDeimos]

Hello, I maintain the backend for Puter. For years I've had opentelemetry and jaeger working together to diagnose performance issues but after upgrading it appears we've lost this. I've spent the past 2 days trying to get it back to no avail. This week we're planning on going full-focus on performance and this is really messing up our plans.

It all started after we upgraded opentelemetry packages. I wasn't able to run Puter with the performance module enabled anymore until these two commits fixed it:

• the fix, and this fix for an error in the fix

This fix itself seems pretty harmless - we pass spanProcessors in the constructor of the provider now instead of calling addSpanProcessor. While I feel introducing this regression was unnecessary it wasn't a big deal once we found out what we needed to do. (however if the method was replaced with a method that throws an exception explaining the regression we would have found this much quicker)

If I try to run everything the same as before I don't see any custom spans. In jaeger, I only ever see the built-in spans for things like HTTP requests and accessing files on the system. I've tried a lot of different things to fix it - re-ordering things, using getTracer from getTraceProvider() instead, calling getTracer where specific things are instrumented as the documentation recommends, etc; nothing is working. I'm writing this now because I don't know what to try next - I have run out of ideas.

For now we have downgraded and everything is working again.