- Rust 99.9%
| .github/workflows | Allow warnings in CI | |
| fuzz | Fix decoding, improve module docs | |
| meadowcap | Bump meadowcap version | |
| willow25 | Double fix | |
| willow25_macros | Fix all the things | |
| willow_data_model | ComponentsNotRelatedError derive and implement traits | |
| .gitignore | Add successor + prefix successor fns for paths + fuzz testing | |
| Cargo.lock | Bump version | |
| Cargo.toml | Port read capabilities to willow25 | |
| LICENSE-APACHE | Update metadata | |
| LICENSE-MIT | Update metadata | |
| README.md | Update usage instructions for fuzz/run_all.sh | |
| rust-toolchain.toml | chore: add CI for windows, android, and 32bit cross compile | |
willow-rs
Protocols for synchronisable data stores. The best parts? Fine-grained permissions, a keen approach to privacy, destructive edits, and a dainty bandwidth and memory footprint.
A Rust implementation of various parts of the Willow specifications. The readmes for the individual crates in this workspace contain more information.
Fuzz tests
This repository has many fuzz tests. To use cargo fuzz commands, you must
first make fuzz the working directory so that the nightly compiler (on which
cargo-fuzz relies) is used for compiling the tests.
cd fuzz
cargo fuzz run <test_name_here>
There is also a command for running all the fuzz tests sequentially:
cd fuzz
./run_all.sh <time per test case in seconds> [infinite]
Specify the infinite flag if you want to keep looping through all test cases.
Without it, every test case is run once and then the script terminates.
This project was funded through the NGI0 Core Fund, a fund established by NLnet with financial support from the European Commission's Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 101092990.