swift-distributed-actors icon indicating copy to clipboard operation
swift-distributed-actors copied to clipboard

Peer-to-peer cluster implementation for Swift Distributed Actors

Results 181 swift-distributed-actors issues
Sort by recently updated
recently updated
newest added

This replaces our previous "bunch of shell scripts" integration tests. Resolves https://github.com/apple/swift-distributed-actors/issues/900 I actually found a bug while doing this so will solve https://github.com/apple/swift-distributed-actors/issues/1054 while doing this. Ignore the ad-hoc...

We used to use protobuf for it, which how clashes with our DA serialization infra... We probably should give up on mixing proto and codable for now... Reproducer: ```swift distributed...

kind/bug
2 - pick next
3 - in progress
t:serialization

We weakened the actors holding it only via a `weak` yet should investigate more what could hold it more than necessary. See https://github.com/apple/swift-distributed-actors/pull/565 and https://github.com/apple/swift-distributed-actors/pull/322

help wanted
2 - pick next
memory leak
t:actor

Had some issues with running them and all the Xcode setups etc. Will reenable but for now disabled so we have green unit-test CI to continue the primary porting work...

bug 🐞
3 - in progress
t:tests

Commit hash: 811d2e88a12db8477a0edde6311c1299102314d3 Context: Application crashes with fatal error when I subscribe to receptionist updates. For example doing: ```swift for await testActor in await app.cluster.receptionist.listing(of: .testActor) { debugPrint("TestActor added", testActor)...

bug 🐞
t:receptionist

Once we have everything moved to remote calls, after https://github.com/apple/swift-distributed-actors/pull/956 we should continue to move towards removal of behaviors in the call-paths. Eventually removing the need to spawn behavior actors...

1 - triaged
3 - in progress
s:medium
t:actor

For development we popped over to `main` right now, switch over before release.

1 - triaged
t:build

Normally "not an issue" since there is 1 system per application, however we must not willingly cause leaks even if people did something weird like spawning and stopping tens of...

kind/bug
1 - triaged
2 - pick next
memory leak

Sigh, it's back; `ERROR: Cannot schedule tasks on an EventLoop that has already shut down. This will be upgraded to a forced crash in future SwiftNIO versions.` So hard and...

kind/bug
1 - triaged
2 - pick next

Eventually resolves https://github.com/apple/swift-distributed-actors/issues/1040 Very WIP, need to switch over to another task for now.