You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operation completes its promise with the result of redisCommand.decodeReply (in completeSuccess and tryCompleteSuccess).
However, if the deserializer throws an exception, it never completes the promise (and I think the thrown exception might cause other issues too).
This is possible with custom ByteStringDeserializer or RedisReplyDeserializer that throws in certain scenarios. It's even possible if you try to get something holding an unexpected value, for instance, set("key", "value") followed by get[Double]("key"). The ActorSystem ends up dumping something like java.lang.NumberFormatException: For input string: "value", but the Future returned by get never completes.
Thanks a lot for your report! Would you mind filing a patch with your suggested change (and if possible, a testcase or an instruction to reproduce the issue)?
Operation
completes its promise with the result ofredisCommand.decodeReply
(incompleteSuccess
andtryCompleteSuccess
).However, if the deserializer throws an exception, it never completes the promise (and I think the thrown exception might cause other issues too).
This is possible with custom
ByteStringDeserializer
orRedisReplyDeserializer
that throws in certain scenarios. It's even possible if you try to get something holding an unexpected value, for instance,set("key", "value")
followed byget[Double]("key")
. The ActorSystem ends up dumping something likejava.lang.NumberFormatException: For input string: "value"
, but theFuture
returned byget
never completes.Maybe it should be changed to something like:
The text was updated successfully, but these errors were encountered: