Closed brentvukmer closed 1 year ago
Ah, yes, sorry, this is a bad error message I still haven't had time to clean up. Is it possible that there are operations in the history where the completion's transaction (:value
) is different than the :value
of the invocation?
That was it! Thanks very much.
I'm working through the Maelstrom Guide. For better or worse I decided to implement each exercise in Go rather than just use the Ruby code supplied in docs. I'm currently implementing the logic from Chapter 5 'Database As Value'.
I'm invoking maelstrom with these arguments:
./maelstrom test -w txn-list-append --bin "${GOPATH}/bin/datomic" --time-limit 10 --node-count 2 --rate 100 --log-stderr
I'm running into an error in
results.edn
that I'm not sure how to troubleshoot:java.lang.IllegalArgumentException: No matching clause: [:ok :invoke]
My first thought was that that indicated there was an
:invoke
without a corresponding:ok
. I found one missing:ok
for each node -- with a:net :timeout
instead. That seems to match the behavior described in the Database As Value section.Any suggestions for how to troubleshoot this?