Skip to content
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

fix: Named CircuitBreakerApi should take ClassicActorSystemProvider #32411

Merged
merged 2 commits into from May 7, 2024

Conversation

johanandren
Copy link
Member

Binary breaking but source compatible change. ExtendedActorSystem was a really inconvenient parameter requiring an explicit cast in user code.

References #32307

Binary breaking but source compatible change. ExtendedActorSystem was a really inconvenient parameter
requiring an explicit cast in user code.
@johanandren johanandren added this to the 2.9.3 milestone May 7, 2024
Copy link
Member

@octonato octonato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but waiting for a second opinion before merging because of compatibility issue.

Copy link
Member

@patriknw patriknw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Really strange that it was ExtendedActorSystem

# Migration Guide 2.9.2 to 2.9.3

Named circuit breaker lookup was taking a `ExtendedActorSystem` requiring a typecast, is now requiring a `ClassicActorSystemProvider`.
This change is source compatible, but not binary compatible, so will require a recompile if you are using named circuit breakers.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good to mention here

@patriknw patriknw merged commit 44e8dad into main May 7, 2024
5 checks passed
@patriknw patriknw deleted the wip-actorsystem-for-named-breaker branch May 7, 2024 09:10
@patriknw patriknw removed this from the 2.9.3 milestone May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants