|3 months ago||19 days ago|
|GNU General Public License v3.0 or later||MIT License|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Implementing a distributed key-value store on top of implementing Raft in Go
5 projects | news.ycombinator.com | 25 May 2023
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.
What's the best way to test parallel jobs?
2 projects | /r/ExperiencedDevs | 18 Apr 2023
Something like coyote by MS?
Using Java's Project Loom to build more reliable distributed systems
4 projects | news.ycombinator.com | 9 May 2022
If you're looking for similar concurrency testing in the dotnet world, checkout Coyote:
Coyote: .NET library tool help ensure that your code is free of concurrency bugs
2 projects | news.ycombinator.com | 1 Feb 2022
TLA+ Graph Explorer
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)
Finding threading issues in code quickly
2 projects | /r/csharp | 24 Dec 2020
The closest I can think of is https://github.com/microsoft/coyote
TLA+ Graph Explorer
> 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?
What are some alternatives?
Appccelerate - State Machine - A .net library that lets you build state machines (hierarchical, async with fluent definition syntax and reporting capabilities).
Automatonymous - A state machine library for .Net - 100% code - No doodleware
P - The P programming language.
lucene-grep - Grep-like utility based on Lucene Monitor compiled with GraalVM native-image
loom - https://openjdk.org/projects/loom
NSubstitute - A friendly substitute for .NET mocking libraries.
React - The library for web and native user interfaces.
30-seconds-of-code - Short code snippets for all your development needs
BlockHound - Java agent to detect blocking calls from non-blocking threads.