coyote VS tlaplus-graph-explorer

Microsoft has a library/tool called Coyote* that helps with testing distributed systems; you can write tests/specifications, Coyote will systematically explore nondeterminism in your system and check if your tests still pass. If there's a failure, it'll show the sequence of events that led to the failing test.

I started a project to implement Raft with a KV-store on top, similar to the article, meaning to use Coyote to test it; I didn't get that far before losing interest, though. It's reassuring to read that it took Phil several months to write the code in the post, it's good to know that this is a decidedly nontrivial problem.

* https://github.com/microsoft/coyote

Something like coyote by MS?

If you're looking for similar concurrency testing in the dotnet world, checkout Coyote:

https://microsoft.github.io/coyote/

https://innovation.microsoft.com/en-us/exploring-project-coy...

Visualizations do help a lot when model checkers and concurrency schedule exploration tools like Coyote find bugs. Coyote include the ability to visualize the traces if you express your concurrency using actors (see https://microsoft.github.io/coyote/#concepts/actors/state-ma...)

It also allows you to implement your own "logger" through which you can emit enough information to construct some cool visualizations. I had a lot of fun working on visualizing an implementation of Paxos using Coyote (then P#) (screenshot at https://ibb.co/TTk2hYb)

The closest I can think of is https://github.com/microsoft/coyote

Hi,

> wonder whether there will be an update to map those children to the names of the actions taken in the spec

This can be done by, for example, adding a variable to the spec with the label of the transition, lets say a variable named label. Then in the tool you can parse the state string (variable value in function updateChilds, https://github.com/afonsonf/tlaplus-graph-explorer/blob/main...), and then use the label when creating the radio button.

The label can be obtained from the variable value in updateChilds with something like: label = parseVars(value).get("label").

> You write the visualizations in D3 I guess?

The visualization I think can be written with any javascript library, at least I tried to make it able to do so. In the second example I wrote the visualization with svg.js.