Skip to content

Conversation

He-Pin
Copy link
Member

@He-Pin He-Pin commented Aug 26, 2025

refs: #2093

@He-Pin He-Pin requested review from mdedetrich and pjfanning August 26, 2025 04:02
@He-Pin He-Pin added this to the 2.0.0-M1 milestone Aug 26, 2025
@He-Pin He-Pin force-pushed the terminated branch 4 times, most recently from 3380771 to d4c9d68 Compare August 26, 2025 06:40
import scala.concurrent.Await
terminate()
Await.result(whenTerminated, atMost)
}
Copy link
Member Author

Choose a reason for hiding this comment

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

Added two methods for both Java and Scala

Copy link
Contributor

@mdedetrich mdedetrich left a comment

Choose a reason for hiding this comment

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

Lets hold off merging this for now, main reason is as @raboof stated at #2093 (comment) if we are going to this it makes sense to just call the method close() while implementing the Java closable interface.

@He-Pin
Copy link
Member Author

He-Pin commented Aug 26, 2025

A close is a terminateAndWait(Duration.Inf)

@He-Pin
Copy link
Member Author

He-Pin commented Aug 26, 2025

@pjfanning @raboof wdyt?

@pjfanning
Copy link
Member

Let's see what alternative proposals are made before choosing one. In this PR, I would prefer if the classic ActorSystem terminate was not changed so that existing users won't have a migration problem.

@He-Pin
Copy link
Member Author

He-Pin commented Aug 26, 2025

OK, I was alias it with the typed one.

@He-Pin
Copy link
Member Author

He-Pin commented Aug 26, 2025

@pjfanning I changed back to the old terminate

@He-Pin
Copy link
Member Author

He-Pin commented Aug 29, 2025

@mdedetrich Wdyt, if I change the terminateAndAwait to close()?

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.

3 participants