Comments (4)
Hi @LegNeato. Thanks for reaching out! For that to work we need two things:
- the ability to return to an earlier state (for nondeterminism)
- the ability to pass inputs back into each actor
Both could be satisfied by a coroutine library providing the ability to clone a coroutine's state and resume a coroutine from that clone without impacting the original. I looked into that a year or two ago and didn't find any good candidates, but it might just have been a miss on my side, or perhaps someone has fulfilled those requirements in the meantime. Please let me know if you have any ideas/leads.
Alternatively a more invasive change could enable the ergonomic improvement you are suggesting. Stateright is a "stateful model checker" meaning it must be able to access the entire system state (i.e. no system state can be hidden), enabling the checker to know if a state has already been visited. There is a different technique called stateless model checking that does not require access to the internal state, but it comes with some trade-offs:
- debugging can be a bit more complex since not all state is necessarily visible
- the model checker must replay history for every nondeterministic "branch point," which could be more expensive (although this performance cost could be offset by state space reduction like DPOR as suggested in #7).
I'm on board with the idea; just short on time to implement at the moment. If you'd like to implement or if you have alternative proposals I would very much appreciate it, and we can talk through more details here.
from stateright.
BTW one other difference is that with stateless checking you cannot assert properties on the global state of the system. Instead you would have to embed assertions in each actor or in a test harness that validates the externally observable behaviors (such as linearizability as assessed by a particular client).
from stateright.
Makes sense, thank you for the reply! Let me dwell on this a bit.
from stateright.
Experimental prototype: https://crates.io/crates/fibril_verifier
from stateright.
Related Issues (20)
- Question about stateright states HOT 2
- Name threads when spawning for checking HOT 1
- Handle panics during checking HOT 1
- Add ability to save and load checker state HOT 4
- Go code implementation of stateright project HOT 1
- Spawning actors with a reliable network HOT 2
- Report depth in ReportData
- Enable limiting the depth traversed by the checker
- Named timers
- Quicker detection of done state in reporter
- Question: Is it possible to share the outputs / states HOT 2
- Simulation checker
- Remove the `actions` argument from `Model::actions` and return the actions HOT 3
- `smoke_test_states` fails on the master branch. HOT 3
- `DGraph::with_path` should take the ownership of `self` to avoid cloning.
- Enable `cargo clippy` in CI
- Heterogenous Actors HOT 3
- Tag your releases HOT 2
- Simulation checker HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from stateright.