Client behavior when decoding a response failed

[Yury-Fridlyand]

I use a pop-ish command to pop an element from a collection and it fails, because the element cannot be represented as a string. I don't receive a popped element, but it is removed from the data set. Second pop will never return it, so that element unrecoverably lost.
See example on node client:

GLIDE clients should provide a better error experience in such cases. The documentation should be also updated to notify users to be extra cautious if there a change to receive a binary data as a response, while deleting this data on server side (getdel, all pop commands).

[GumpacG]

There is also the case where a user decodes using GlideString.toString(), the resulting GlideString that is not convertible to String. The result of GlideString.toString() is a String value "Value not convertible to string: byte[]" instead of throwing an error. Once a decision on a resolution has been made, please update the test

valkey-glide/java/integTest/src/test/java/glide/SharedCommandTests.java

Line 1022 in 13a2a86

"Value not convertible to string: byte[] 13",

.