-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
=rem #17729 Don't use Implicits.global in remoting shutdown #17876
Conversation
@@ -146,6 +145,7 @@ private[remote] class Remoting(_system: ExtendedActorSystem, _provider: RemoteAc | |||
endpointManager = None | |||
} | |||
|
|||
import system.dispatcher |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it still alive and kicking here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I can see, it is. endpointManager is an actor.
I have verified (with printlns) that the callback is running with the system.dispatcher in all cases when running the tests in akka-remote.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think the caller of this shutdown() method actually blocks on an Await, so this is probably safe.
Refs #17729 |
Test PASSed. |
LGTM |
LGTM, nice detective work! |
=rem #17729 Don't use Implicits.global in remoting shutdown
…triknw =rem akka#17729 Don't use Implicits.global in remoting shutdown
I have verified (with printlns) that the callback is running with the system.dispatcher in all cases when running the tests in akka-remote.