-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenTelemetry is sometimes requested before it is created and thus build fails #2253
Comments
Seems like |
Hi, in our team we use Quarkus with OTEL on a bunch of components (~20) and every other build, 1 or 2 of these components end up with this issue. Once a build displays this problem, it will remain broken. Only way to fix it, is to do another build and hope for the best. This is really starting to interfere with our CI/CD process because sometimes multiple builds are necessary to get all components working properly. Is this bug on the radar? Can we expect a solution in a nearby update? |
Yes #2540 addressed that issue. It'll be a part of Quarkus 3.10 |
Thx, that's great news! |
I experienced this issue just once here https://github.com/quarkus-qe/beefy-scenarios/actions/runs/5770827990/job/15644520776?pr=404 and can't reproduce it, but judging by logs it seems like the order of build items is not ensured so that
KafkaOpenTelemetryInstrumenter
may invokeGlobalOpenTelemetry.get()
before it was set.Reproducer (theoretically :-) it's random):
git clone [email protected]:quarkus-qe/beefy-scenarios.git
cd beefy-scenarios
mvn -fae -V -B -s .github/mvn-settings.xml -Dvalidate-format clean test -pl 301-quarkus-vertx-kafka/
Logged exception:
The text was updated successfully, but these errors were encountered: