These are chat archives for atomix/atomix
We are no longer monitoring this channel, please join Slack! https://join.slack.com/t/atomixio/shared_invite/enQtNDgzNjA5MjMyMDUxLTVmMThjZDcxZDE3ZmU4ZGYwZTc2MGJiYjVjMjFkOWMyNmVjYTc5YjExYTZiOWFjODlkYmE2MjNjYzZhNjU2MjY
<dependency> <groupId>io.atomix</groupId> <artifactId>atomix</artifactId> <version>2.1.0-SNAPSHOT</version> </dependency> <dependency> <groupId>io.atomix</groupId> <artifactId>atomix-raft</artifactId> <version>2.1.0-SNAPSHOT</version> </dependency>
CompletableFutureordering issue wherein futures are sometimes being completed in reverse order again. Have to fix that before merging all the changes, then should be able to do the version bump.
Futures.orderedFuturemethod is replaced by the
client.connect().thenCompose(v -> client.execute(…))when
client.connect()returns a future that multiple callers then call
thenComposeon, and those callbacks are called out of order. The problem seems to just be that the ordered futures are being obscured by more futures
CompletableFuturecallbacks has been a major PITA. We don’t want to allocate queues for every single future. Atomix creates futures like crazy. Although I guess allocating a linked list isn’t really a big deal so maybe should just generalize it to all the futures.