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
Hello everyone,
This is a similar issue to #523, but we are using the expected commands.
We are currently encountering a strange issue with Dynomite returning (nil) when trying to delete an existing key from the Redis Server.
During the debug, we have tried with only 1 redis server in the configuration but also two of them, and we see the same behaviour.
The very strange thing is that the key get's deleted, but the return is not what is expected (1, instead of nil).
The behavior has been observed both via dynomite cli and the external tool we are using to connect to dynomite's port.
Could this be something because of configuration files or some network issue, etc?
What could I provide to further assist with this issue, as we are not able to change the code that is looking and expecting the return to be 1.
The text was updated successfully, but these errors were encountered:
Hello everyone,
This is a similar issue to #523, but we are using the expected commands.
We are currently encountering a strange issue with Dynomite returning
(nil)
when trying to delete an existing key from the Redis Server.During the debug, we have tried with only 1 redis server in the configuration but also two of them, and we see the same behaviour.
The very strange thing is that the key get's deleted, but the return is not what is expected (1, instead of nil).
The behavior has been observed both via
dynomite cli
and theexternal tool
we are using to connect to dynomite's port.Could this be something because of configuration files or some network issue, etc?
What could I provide to further assist with this issue, as we are not able to change the code that is looking and expecting the return to be 1.
The text was updated successfully, but these errors were encountered: