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.

• parpulse-client

  • Failed to verify create's content against its repository

    Verified 4 out of 8 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from the commit 7bdb4bb54a97d674b0ae060f8dd78de20604c7f5, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Number of [[bin]] inconsistent; published=0; orig=1; ed=Set(E2021).

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.
    • src/
      • client.rs does not match the repository.
      • lib.rs does not match the repository.

    Looked for the crate in storage-client/. Fetched https://github.com/cmu-db/15721-s24-cache1.git 540db28b7f9fdae61dce0928f50c57b33be3f2a8.

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

  • Dependency arrow 50.0.0 is significantly outdated

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

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

    arrow versions

  • Dependency parquet 50.0.0 is significantly outdated

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

    parquet versions

  • Imprecise dependency requirement anyhow = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as anyhow = "1.0.97". 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.

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    anyhow versions

  • Dependency istziio-client 0.1.9 is slightly outdated

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

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

    istziio-client versions

  • Missing categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["client", "parpulse-client", "parpulse", "service"] (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.