Lib.rs

Issues found

Based on crates you own that have been published to crates.io. The best way to monitor these issues is to subscribe to the atom feed in your RSS reader.

• noir-compute

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["…"] to the Cargo.toml.

    Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.

    List of available categories

  • Dependency itertools 0.12.1 is significantly outdated

    Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    itertools versions

  • Dependency serde_yaml 0.9.32 has issues

    It may not be actively developed any more. Consider changing the dependency.

    serde_yaml crate

  • Dependency dashmap 5.5.3 is a bit outdated

    Consider upgrading to 6.1.0 to get all the fixes and improvements.

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    dashmap versions

  • Dependency quick_cache 0.4.1 is outdated

    Upgrade to 0.6.9 to get all the fixes, and avoid causing duplicate dependencies in projects.

    quick_cache versions

  • Dependency thiserror 1.0.58 is a bit outdated

    Consider upgrading to 2.0.11 to get all the fixes and improvements.

    thiserror versions

  • Missing keywords

    Help users find your crates. Add keywords = ["data-processing", "stream-processing", "operator", "distributed", "dataflow"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

  • Optional dependency 'futures' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'futures', 'sha2', 'crossbeam-channel', 'tokio', 'whoami', 'base64', 'ssh2', 'shell-escape' may have been unintentional.

    Crate features

• renoir

  • Dependency arrow 53.4.0 is a bit outdated

    Consider upgrading to 54.0.0 to get all the fixes and improvements.

    arrow versions

  • Dependency parquet 53.4.0 is outdated

    Consider upgrading to 54.0.0 to get all the fixes and improvements.

    parquet versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["concurrency"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["operator", "stream-processing", "data-processing", "block", "dataflow"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

  • Optional dependency 'sha2' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'sha2', 'whoami', 'shell-escape', 'base64', 'ssh2' may have been unintentional.

    Crate features

• micrometer

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::profiling"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["low-overhead", "profiling", "multi-threading", "applications", "events"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• radon

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
status = "deprecated" to their Cargo.toml.