Crates.io | chik |
lib.rs | chik |
version | 0.10.0 |
source | src |
created_at | 2023-07-25 00:55:21.87413 |
updated_at | 2024-07-11 09:09:44.799349 |
description | A meta-crate that exports all of the Chik crates in the workspace. |
homepage | https://github.com/Chik-Network/chik_rs |
repository | https://github.com/Chik-Network/chik_rs |
max_upload_size | |
id | 925075 |
size | 6,358,021 |
A collection of Rust crates for working with the Chik blockchain. There are also Python bindings in the form of a wheel.
To run the unit tests for the whole workspace:
cargo test --workspace
Some slow tests are only enabled in optimized builds, so it may also be a good idea to run the tests in release mode:
cargo test --workspace --release
You may need a Python virtual environment activated for the tests to link properly, due to the pyo3
dependency in wheel
.
You can setup a virtual environment with the following command:
python3 -m venv venv
Activate the virtual env:
. ./venv/bin/activate
The wheel
crate is a single Python wheel that exports bindings to various functionality in the repository, mostly from chik-consensus
and chik-protocol
.
It's built with maturin
, so you need to have activated a python virtual environment for the build to work.
The bindings are tested with pytest
. Before you run them, install the following dependencies:
pip install pytest maturin typing-extensions chik-blockchain==2.1.2
And build the Python wheel:
maturin develop -m wheel/Cargo.toml
Finally, you can run the Python binding tests:
pytest tests
Note that these tests can take several minutes to complete.
To run benchmarks for a specific crate before you make changes:
cargo bench -- --save-baseline before
After you apply the changes, finish the benchmark:
cargo bench -- --save-baseline after
critcmp after before
You can also run all the benchmarks by including --workspace
.
Note that you must include the flag before the --
, for example:
cargo bench --workspace -- --save-baseline before
This repository has a pre-commit configuration, which is hooked into git by running:
pre-commit install --hook-type pre-commit --hook-type pre-push
It runs Prettier and then cargo fmt
on all crates on every commit. When you push, it runs cargo clippy
, cargo test
, and cargo build
.
To run all checks explicitly (without pushing), run:
pre-commit run --all --hook-stage pre-push
Fuzzers can't be run or listed for the whole workspace, but only for individual crates. There is a tool to generate a fuzzing corpus from a blockchain database.
It's run like this:
cd crates/chik-tools
cargo run --release --bin gen-corpus -- --help
The following crates have fuzzers:
To list and run fuzzers:
cargo fuzz list
cargo fuzz run <name-of-fuzzer>
Make sure you have cargo-workspaces
installed:
cargo install cargo-workspaces
To bump the versions of all relevant crates:
cargo ws version --all --no-git-commit
Select "minor update" if there has not been any incompatible API changes, otherwise "major update".