Readit NewsAlso, for what it's worth, Jenkins changed their terminology to use "agent" instead of slave in 2020 [0]. These efforts might seem futile in isolation, but they add up over time.
[0] https://www.jenkins.io/blog/2020/06/18/terminology-update/
Overall, my experience has been positive. When it works, it's great. A pattern I've been following is to have a single fixture that returns a simulation of the system under a standard configuration, for example N replicas of an atomic register, so that each test looks like: 1. Modify the simulation with something like`turmoil::hold("client", "replica-1")`. 2. Submit a request to the server. 3. Make an assertion about either the response, or the state of the simulation once the request has been made. For example, if only some replicas are faulty, the request should succeed, but if too many replicas are faulty, the request / simulation should time-out.
One of the things I have found difficut is that when a test fails, it can be hard to tell if my code is wrong, or if I am using Turmoil incorrectly. I've had to do some deep-dives into the source in order to fully understand what happens, as the behavior sometimes doesn't line-up with my understanding of the documentation.
In theoretical distributed computing, The Space Complexity of Concencus From Swap [0] solves a problem that has been open for a couple decades, and won Best Paper at PODC 2022.
In quantum complexity theory, MIP^* = RE [1] was really big deal when it was published in 2020. It got a (relative) ton of press coverage, and there are lots of articles and blog post available that give a high-level of the result and techniques used. I like this one [2] from Quanta Magazine.
[0] https://dl.acm.org/doi/abs/10.1145/3519270.3538420
[1] https://arxiv.org/abs/2001.04383
[2] https://www.quantamagazine.org/landmark-computer-science-pro...
I think the point they are making is that cis and trans don't work in this sort of class analysis, as the two groups are in themselves too diverse. They have to be further divided into subgroups for this to make any sense.
For example, take the most controversial subset of the transgendered: transwomen, i.e. males who identify as women. Then compare to actual female women ("cis women") - it is obvious that this maps onto the existing feminist analysis of sex class, with males being the dominant class and females the oppressed class.
Which is what makes it so problematic when these males try to impose themselves upon the spaces of actual female women, as they're engaging in male dominance behaviour that wouldn't be considered acceptable by any other man. But because we have this false cis-trans oppression hierarchy being presented to defend this, it pulls the wool over many people's eyes to what is really happening.
It is so easy to put pressure, shame, and negativity onto yourself, to a degree that you never would for anyone else. It has been very helpful at times to ask "What would I say to a good friend who was in the same situation as me?". Almost always, it is a complete 180 from the aweful things I would tell myself. Knowing that I have the ability to be just as compassionate to myself as I strive to be towards others, has been huge.
Shuttle's approach is to be randomized, instead of exhaustive like loom. However, the scheduler does still give probabilistic guarantees about finding bugs. I found that shuttle was faster and scaled to more complicated test scenarios.
Similar to the article, shuttle also lets you save the random seed if a particular schedule causes the test suite to fail. Being able to quickly reproduce failing tests is really important and enables you write explicit test cases for bugs that were previously caught and fixed [3].
[0] https://github.com/kaymanb/todc/tree/main/todc-mem [1] https://github.com/tokio-rs/loom [2] https://github.com/awslabs/shuttle [3] https://github.com/kaymanb/todc/blob/0e2874a70ec8beed8fae773...