Skip to content

Conversation

@akbashev
Copy link
Contributor

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.

@akbashev
Copy link
Contributor Author

@ktoso we can focus on your PR though, can close this one. It's just easier for me to finish it here.

@ktoso
Copy link
Member

ktoso commented Oct 16, 2024

Happy for you to take it over. Fixed up CI so we now just do 5.10+ jobs.

@ktoso ktoso closed this Oct 16, 2024
@ktoso ktoso reopened this Oct 16, 2024
# Conflicts:
#	Sources/MultiNodeTestKitRunner/boot+MultiNodeTestKitRunner+Exec.swift
@akbashev akbashev marked this pull request as ready for review November 5, 2024 15:33
Comment on lines +494 to +496
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)
Copy link
Contributor Author

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.

@akbashev
Copy link
Contributor Author

akbashev commented Nov 5, 2024

@ktoso I've went through code, cleaned up some stuff, executable is now called swift-clusterd and tested myself, test is also working.
Except for ClusterD should be a "HIDDEN" member in the membership mentioned in original PR think it's already in a good shape to be merged.

@zastrozzi
Copy link

Hey guys is there any movement on this?

@akbashev
Copy link
Contributor Author

akbashev commented Feb 18, 2025

@zastrozzi Hi! 👋 There are currently some really weird issues with tests that need to be tackled before we can merge everything.
I will try again to check, but probably will take some time.

@zastrozzi
Copy link

Hey no worries! If I have some time I'll see if I can help too. Are the testing problems cited elsewhere in an issue/PR?

@akbashev
Copy link
Contributor Author

Hey no worries! If I have some time I'll see if I can help too. Are the testing problems cited elsewhere in an issue/PR?

There is this issue, but it's really strange one, will try to ping and check once more.

# Conflicts:
#	Sources/DistributedCluster/Cluster/DiscoveryShell.swift
#	Sources/MultiNodeTestKitRunner/boot+MultiNodeTestKitRunner+Exec.swift
@ktoso
Copy link
Member

ktoso commented May 1, 2025

we don't do API breakage, we could remove that, we're pre-1.0

@akbashev
Copy link
Contributor Author

akbashev commented May 1, 2025

we don't do API breakage, we could remove that, we're pre-1.0

Hm, can you elaborate a bit more? It's not really breaking anything, but you mean you don't wanna add something new to pre-1.0 and 1.0?

@ktoso
Copy link
Member

ktoso commented May 1, 2025

The Pr validation triggered api compatibility checking, so I was saying we can disable that basically :)

@akbashev
Copy link
Contributor Author

akbashev commented May 1, 2025

The Pr validation triggered api compatibility checking, so I was saying we can disable that basically :)

ah, ok, was confused a bit. 🙂

@ktoso ktoso added the semver/none No version bump required. label Sep 10, 2025
@ktoso ktoso merged commit 6c9aa15 into apple:main Sep 11, 2025
34 of 39 checks passed
@akbashev akbashev deleted the clusterd-poc branch September 17, 2025 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver/none No version bump required.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants