TestServer w/ ets memory backend (2i, $keys, bin index, range search) about riak-ruby-client HOT 7 CLOSED

This gist shows the difference between the test backend in the client vs master of the memory backend in riak_kv. I think you can see that the differences there are minor and related to packaging. The key-folding logic is unaffected.

If indeed the test backend is broken, this means KV's memory backend is broken as well.

from riak-ruby-client.

Confirmed that in 1.2, this difference exists between eleveldb and memory backends. What would you like to do - close here; open in riak_kv?

from riak-ruby-client.

Yes. Ideally some detailed information about how to reproduce would help, too.

from riak-ruby-client.

i could drill this down into direct http api calls; but this gist should be enough?

from riak-ruby-client.

moved to riak_kv; when that is fixed - i'll try to put together a PR to update the backwards compatible ruby test server.

from riak-ruby-client.

@randysecrist Yes, that gist works, and reproduces the issue for me.

from riak-ruby-client.

@randysecrist Closing this since we have issues on both riak_kv and riak_test.

from riak-ruby-client.