We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://github.com/dustin/gomemcached/blob/master/client/mc.go#L389
Why is this done? It appears to ignore the expiry value passed in and reset it to 0.
In our system, this leads to updated keys never expiring. The fix is easy, but wondering why this was done in the first place?
The text was updated successfully, but these errors were encountered:
It's a bit unclear. It seemed that every path was wrong, but that one probably looks more wrong than resetting it to the supplied value.
Sorry, something went wrong.
No branches or pull requests
https://github.com/dustin/gomemcached/blob/master/client/mc.go#L389
Why is this done? It appears to ignore the expiry value passed in and reset it to 0.
In our system, this leads to updated keys never expiring. The fix is easy, but wondering why this was done in the first place?
The text was updated successfully, but these errors were encountered: