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.

• jopemachine-raft

  • Dependency fail 0.4 is a bit outdated

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

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

    fail versions

  • Dependency protobuf 2 is a bit outdated

    Consider upgrading to 3.7.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.

    protobuf versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Failed to verify create's content against its repository

    Verified 47 out of 63 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
    • warning: Could not discover crate's location in its repository (via tags).

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.
    • benches/suites/
      • progress.rs does not match the repository.
      • raft.rs does not match the repository.
      • raw_node.rs does not match the repository.
    • main.rs does not match the repository.
    • main.rs does not match the repository.
    • src/
      • lib.rs does not match the repository.
      • logger.rs exists, but elsewhere in the repo.
      • raft.rs does not match the repository.
      • raw_node.rs does not match the repository.
      • config.rs does not match the repository.
      • storage.rs does not match the repository.
      • read_only.rs does not match the repository.
      • log_unstable.rs does not match the repository.
      • formatter.rs exists, but elsewhere in the repo.
      • raft_log.rs does not match the repository.

    Fetched https://github.com/tikv/raft-rs.git 25b66769cde500e8d67e2383a52f1b1a9f4a1acf.

    Checked on 2024-10-04

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement bytes = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as bytes = "1.10.0". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with -Z minimal-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.

    bytes versions

  • Optional dependency 'fail' 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 'fail', 'slog-term', 'slog-envlogger', 'slog-stdlog' may have been unintentional.

    Crate features

• raftify

  • Dependency built 0.5 is significantly outdated

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

    built versions

  • Dependency tonic 0.9.2 is significantly outdated

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

    tonic versions

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency bincode 1.3 is slightly outdated

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

    bincode versions

  • Dependency config 0.14.0 is outdated

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

    config versions

  • Dependency heed 0.20.5 is a bit outdated

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

    heed versions

  • Dependency prost 0.11 is outdated

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

    prost versions

  • Dependency rocksdb 0.22.0 is outdated

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

    rocksdb versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Dependency tonic-build 0.9.2 is outdated

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

    tonic-build versions

  • Failed to verify create's content against its repository

    Verified 46 out of 47 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: There is no matching git tag containing version '0.1.82'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

    Files in the crates.io crate compared to the repository:

    • README.md does not match the repository.

    Looked for the crate in raftify/. Fetched https://github.com/lablup/raftify.git ff578122be24fb5eda46b90f1eefcd4fb448d544.

    Checked on 2024-10-19

    Forum thread

  • Imprecise dependency requirement slog = 2

    Cargo does not always pick latest versions of dependencies! Specify the version as slog = "2.7.0". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    slog versions

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["algorithms"] 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

  • Optional dependency 'heed' 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 'heed', 'heed-traits', 'rocksdb' may have been unintentional.

    Crate features

• jopemachine-raft, raftify, raftify_cli

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

• raftify_cli

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Dependency built 0.5 is significantly outdated

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

    built versions

  • Dependency const_format 0.1.0 is significantly outdated

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

    const_format versions

  • Locked dependency version raftify =0.1.82

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    raftify versions

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

  • Dependency tonic-build 0.9.2 is outdated

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

    tonic-build versions

  • Imprecise dependency requirement slog = 2

    Cargo does not always pick latest versions of dependencies! Specify the version as slog = "2.7.0". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    slog versions

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["command-line-tool", "raftify", "cli"] (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.

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