Issue 48 demonstrates that we don't check delta status from within
binary incr calls. I've written tests for both incr and decr to show
the problem, but I don't have a way to report the error.
Currently, I'm using einval, but that's just kind of wrong since
that's more to do with the input
As part of my work i been doing some testings working with the key-
value database TokyoTyrant using your own MemcachedClient. I found one
critical issue that caused the client to work improperly.
The second parameter sent in the response from TokyoTyrant is 0
representing successful request
On Jun 21, 8:05 am, obp oha...@gmail.com wrote:
As part of my work i been doing some testings working with the key-
value database TokyoTyrant using your own MemcachedClient.
Are you referring to the spymemcached java client?
I found one
critical issue that caused the client to work
memcached-1.2.8
# make test
t/lruok 4/149Out of memory during request for 569364
bytes, total sbrk() is 536471552 bytes!
WHOA! Somehow you got a different number of results than tests ran!
This should never happen! Please contact the author immediately!
What it means? Can I
Great bug report from Mat
-- Forwarded message --
From: Mat Hostetter mhostet...@tilera.com
Date: Tue, Jun 2, 2009 at 11:01 AM
Subject: fencepost buglets in memcached-1.2.8
To: b...@danga.com
In items.c, these arrays allow indices up to but not including LARGEST_ID:
