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

DispatcherSameAsParent not working with cluster ActorRefProvider #28842

Closed
patriknw opened this issue Mar 30, 2020 · 1 comment
Closed

DispatcherSameAsParent not working with cluster ActorRefProvider #28842

patriknw opened this issue Mar 30, 2020 · 1 comment
Assignees
Labels
3 - in progress Someone is working on this ticket bug t:typed
Milestone

Comments

@patriknw
Copy link
Member

No description provided.

@patriknw patriknw added 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted bug t:typed labels Mar 30, 2020
@patriknw patriknw self-assigned this Mar 30, 2020
@patriknw patriknw added 3 - in progress Someone is working on this ticket and removed 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted labels Mar 30, 2020
patriknw added a commit that referenced this issue Mar 30, 2020
* add test
* the check for valid config is not needed in RemoteActorRefProvider,
  since it is delegating to LocalActorRefProvider for all cases but the
  remote deployment case
octonato added a commit that referenced this issue Apr 1, 2020
fix DispatcherSameAsParent when using ClusterActorRefProvider, #28842
@octonato
Copy link
Member

octonato commented Apr 1, 2020

Fixed in #28843

@octonato octonato closed this as completed Apr 1, 2020
@octonato octonato added this to the 2.6.5 milestone Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - in progress Someone is working on this ticket bug t:typed
Projects
None yet
Development

No branches or pull requests

2 participants