Skip to content

Latest commit

 

History

History
164 lines (100 loc) · 4.83 KB

README.md

File metadata and controls

164 lines (100 loc) · 4.83 KB
Raw

Rust Digger

  • Analyze Rust Crates, help evaluation and suggest improvements

  • Fetch list of Crates

  • Process the data

  • Generate static HTML pages

Contribution

Please send small pull-requests and make sure each PR changes one thing.

If you would like to implement a feature, but first you need to refactor the code, please send the PR to refactor the code and only once I accepted that send the change to implement the feature. This might sound frustrating, but I am not very good at code reviews so if I get a long PR that changes several things that don't have to be changed at once, then I might not understand it and I might not accept it. That would be a lot more frustrating to both of us.

Please either set up the pre-commit hooks as described below or run cargo fmt, cargo clippy, and cargo test manually before committing code.

Local development environment

git clone https://github.com/szabgab/rust-digger.git
cd rust-digger

Optionally install pre-commit and then run pre-commit install to configure it on this project.

Download the data from static.crates.io

cargo run --bin rust-digger-download-db-dump

Clone 15 repositories of the crates that were release in the last 10 days:

cargo run --bin rust-digger-clone -- --recent 10 --limit 15

Collect data from 15 repositories (VCSs) we cloned. (You can use any number there)

cargo run --bin rust-digger-vcs -- --limit 10

Download some of the released crates from Crates.io

cargo run --bin rust-digger-download-crates -- --limit 10

Generate the static html pages for 10 crates.

cargo run --bin rust-digger-html -- --limit 10

To run a local web server to serve the static files install ruststatic using:

cargo install rustatic

and then run:

rustatic --nice --indexfile index.html --path _site/

Deployment on Ubuntu-based server

Based on https://www.rust-lang.org/tools/install

sudo apt install pkg-config
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
cargo build --release

There is a cron-job that runs all.sh once a day. (As long as we use the dumped data from Crates.io, there is no point in running more frequently.)

Processing steps

Fetching data from crates.io

Discussed here: https://crates.io/data-access

As of 2024.03.26

  1. The git repository https://github.com/rust-lang/crates.io-index does not contain the meta data, such as the github URL
  2. The https://static.crates.io/db-dump.tar.gz is 305 Mb It unzipped to a timestamped folder called YYYY-MM-DD-020046 which is 1.1 Gb and contains CSV dumps of a PostgreSQL database.

The fetching and unzipping is done by the rust-digger-download binary.

For each crate (or for each new crate if we start working incrementally) check if it refers to a repo. For each repo maintain a file called repo-details/github/repo-name.json in this repo we keep all the information we collected about the repository. When generating the HTML files we consult these files. These files are also updated by the stand-alone processes listed below. The files are mapped with the Details struct.

Cloning repositories

  • git pull takes 0.3 sec when it does not need to copy any files.
  • There are 123,216 crates
  • Assuming all of them will have git repositories and most of them won't change we'll need 123,000 * 0.3 = 41,000 sec to update all the repos = that is 683 minutes = 11.5 hours.

If we fail to clone the repository we add this information to the repo-details file of the repository.

Analyzing repositories

  • Some information is easy and fast to collect. (e.g. checking if there are YAML files in .github/workflows to check if GitHub Actions is configured)

  • TODO: if there are more than one crates in the repo, should we analyze and report the crates separately?

Docker

docker build -t rust-test . docker run --rm -it -v$(pwd):/crate --workdir /crate --user tester rust-test

cargo fmt

  • Running cargo fmt --check -- --color=never and capturing the STDOUT and the exit code. We save them together with the current sha of the repository git rev-parse HEAD and the date of processing. (We might also want to save the version of rustfmt cargo fmt --version and the version of rustc rustc --version)
cargo run --bin fmt -- --limit 10

cargo fix

cargo test

Collect test coverage report

rustup toolchain install nightly
rustup default nightly

cargo install rustfilt
cargo clean

RUSTFLAGS="-C instrument-coverage" cargo build
RUSTFLAGS="-C instrument-coverage" cargo test --tests
llvm-profdata merge -sparse *.profraw -o x.profdata


cargo install cargo-tarpaulin
cargo tarpaulin --workspace --out html --out json

Related Sites