Kyle Kingsbury

Hmmm. This still feels like a bug in knossos, but now that I'm not on my phone and can read properly, I notice that your invoke and complete ops have...

Hi @siyopao. This error message means that process 6's completion didn't have a matching prior invocation. If you look at process 6's operations in that history, they are: ``` {:type...

On 01/05/2016 11:30 AM, Balint Pato wrote: > Hi, > > Every now and then, the execution of knossos after jepsen tests throws the > exception below I copied the...

Ohhhh hang on, haha, there's another closely related error in knossos.model.memo where precomputed states don't cover reachable states, but that's not the error you hit. Yeah, I agree, we should,...

@gaodq There are a lot of assertions in Knossos, and without the actual error message and trace it's hard for me to say. I've made some improvements to error handling...

Yeah, I don't see why not. You might have to muck around a bit with the exception and signal handlers but this shouldn't be too hard.On Jul 16, 2020 10:09,...

Maybe worth mentioning that the usual entry point for repl/library calls to Jepsen is jepsen.core/run!--but if that doesn't meet your needs I understand!On Jul 16, 2020 10:33, [email protected] wrote:Yeah, I...

I think arbitrary objects should be fine, you'll just pay some extra penalties for comparisons over bigints. Might be worth remapping those process ids to small numbers just for your...

Yeah, this is probably a codox markdown thing--I'm usually looking at the source rather than the online docs. You're welcome to fix it if you like!

I don't recall this bug in particular, but since this version of Jepsen is fairly old, it might be worth trying a newer one.