Kyle Kingsbury

> But in general, what RavenDB offers and what you are expecting are different. Crucially, RavenDB does not attempt to provide transactional semantics over the entire session, rather it provide...

Thanks for offering this Nezteb. Why don't you maintain this yourself, and we can add a link to it in the Maelstrom README? My experience with the Jepsen Dockerfile has...

Right, so I think this is a shortcoming in Elle's rw-register checker, which does pretty much all its inference through *external* reads and writes--IIRC, my rationale was that internal anomalies...

Naw, that's more like a garbage read, which is also something the rw-register workload should detect, but doesn't, because I am lazy and my entire life has been consumed with...

That's probably best understood as a checker bug--I'll bet you that part of the checker is trying to find e.g. the time between the first and last successful ops, and...

Both, I suppose! Checker only cares about completion ops and actually ignores invocations altogether. Someone with lots of free time (presently, not me, haha) ought to add a pass to...

Ah, I'm not really qualified to speak on this--perhaps @benbjohnson might?

This may actually be a bug (er, sort of, but it's certainly not consistent with lww-kv) in seq-kv! I was sprinting to write these challenges and didn't have time to...

HA! There *was* a bug of sorts. seq-kv was doing something legal but v frustrating where reads and other re-orderable operations would converge on the *next to latest* state, but...

Not exactly: there's both a probabilistic and a deterministic way to use seq-kv here. My thinking in designing this challenge was that folks would have this exact kind of "aha!"...