-
Notifications
You must be signed in to change notification settings - Fork 61
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
Finishing clusterd #1165
base: main
Are you sure you want to change the base?
Finishing clusterd #1165
Conversation
@ktoso we can focus on your PR though, can close this one. It's just easier for me to finish it here. |
Happy for you to take it over. Fixed up CI so we now just do 5.10+ jobs. |
# Conflicts: # Sources/MultiNodeTestKitRunner/boot+MultiNodeTestKitRunner+Exec.swift
case `static`(endpoints: Set<Cluster.Endpoint>, subscribe: (@escaping (Result<[Cluster.Endpoint], Error>) -> Void, @escaping (CompletionReason) -> Void) -> CancellationToken?) | ||
case dynamic(serviceDiscovery: AnyServiceDiscovery, subscribe: (@escaping (Result<[Cluster.Endpoint], Error>) -> Void, @escaping (CompletionReason) -> Void) -> CancellationToken?) | ||
case clusterDaemon(endpoint: Cluster.Endpoint, initialize: (ClusterSystem) -> Void) |
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.
Decided to put subscribe and initialize closures here, as otherwise it's quite confusing to have optional values in settings itself.
@ktoso I've went through code, cleaned up some stuff, executable is now called |
Quite often people ask "How actors find each other" and clusterd could be a good example to show discoverability.
Again just stealing your code here @ktoso 🙂 Will just try to finish and prettify.