Closed eloots closed 4 years ago
The problem here is that the most recent version of akka-persistence-jdbc (3.5.3) has akka 2.5.23 in dependencies.
Adding an explicit dependency on akka-persistence-query 2.6.1 should fix this, and should be safe since we promise binary compatibility.
@raboof thanks!
@raboof is such kind of issue can be considered as a warning or an error? Log says it's warning level.
I agree it would be better to log this at ERROR level, as by default the actor system will not complete its startup when incompatibilities are found.
Verified #140 with lab 60 and 101 so this should cover both configurations
@agolubev I verified that the fix works! Thanks! (cc: @raboof) Closing issue
@agolubev PR #130 breaks existing exercises. E.g. running exercise 60. Building runs fine (
universal:packageBin
). However, running the exercise on a node produces the following error:I did a short investigation and it seems that the problem is caused by some incompatibilities in the code you added in the
common
project. When the code that was added incommon
is removed, the exercise is rebuilt and run, the exercise runs fine. It seems that some incompatibilities exist between the current dependencies and the ones that you added.Can you please fix asap? Also, it is vital to check that existing exercises continue to function when applying changes. Please run tests on a cluster that allows testing this.