Closed sageserpent-open closed 5 years ago
The Redis-based world implementation was cutover to use futures API to talk to Redis rather than a reactive API, as it made migration from Lettuce v4 to v5 simpler (and that turned out to be surprisingly more difficult than at first imagined anyway).
There is another branch 'backToReactiveStreamsLettuceAgain' that has work in progress to reinstate a reactive Redis API in the implementation. Most of the tests pass, so this could be finished off later as a separate cleanup task.
Merged work done so far. Need to think about whether to upgrade Kryo, as the latest version of Chill references an older version of Kryo.
Having started on forcing Chill to pick up Kryo version #5, I'm concerned about binary API incompatibilities occurring at runtime based on what I've seen so far. I'll wait until Chill is upgraded by pick up a new Kryo version, so for now, this task is done.
This is motivated primarily by Kryo and Lettuce, these have had major version changes; it's time to upgrade while the migration is still feasible without causing too much pain.