Break circular dependency when zipkin tracing is enabled #1049
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Creating the default http client in the constructor of
DefaultOAuth2HttpTransportFactory
was causing a circular dependency when Zipkin tracing is enabled. There were no tests forStackDriverSenderFactory
in thegcp-tracing
module, thus the bug was undiscovered until users tried out the new release and reported the issue.DefaultOAuth2HttpTransportFactory
is updated to lazily create the default http client via a memoizedSupplier
, in the same manner as we do in the Micronaut Security JWKS client, and this breaks the dependency cycle.A simple
StackdriverConfigurationSpec
is added to reproduce the issue and verify the fix.This resolves #1045