-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
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
Client fails for command: stats cachedump <slab> <itemcount> #103
Labels
Comments
Switching out the keys |
I don't think just moving to an ordered dict will work because for the 'stats cachedump' call you can have two args which are identical. |
Confirmed this is still a reproducible issue. |
jogo
added a commit
to jogo/pymemcache
that referenced
this issue
Mar 24, 2017
Stats cachedump has a different input and output format compared to most stats commands. Previously this would fail with a cryptic error. Fixes issue pinterest#103
jogo
added a commit
to jogo/pymemcache
that referenced
this issue
Mar 25, 2017
Stats cachedump has a different input and output format compared to most stats commands. Previously this would fail with a cryptic error. Fixes issue pinterest#103
jogo
added a commit
to jogo/pymemcache
that referenced
this issue
Mar 29, 2017
Stats cachedump has a different input and output format compared to most stats commands. Previously this would fail with a cryptic error. Fixes issue pinterest#103
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This line: https://github.com/pinterest/pymemcache/blob/master/pymemcache/client/base.py#L664
causes the 'stats cachedump 0 0' to turn into 'stats cachedump 0' or worse 'stats 0 cachedump' depending on the dict ordering.
Further, if you hack around that, the client doesn't know how to deal with the lines returned which start with 'ITEM '
The text was updated successfully, but these errors were encountered: