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.

• wtinylfu

  • Failed to verify create's content against its repository

    Verified 9 out of 12 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from the commit d80fe0f5f97087a4f04d2a8a7c87d026a4944c8b, 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.
    • warning: Repository fetch error: cannot fetch a specific object from the remote repository; class=Invalid (3).

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

    • Cargo.toml.orig does not match the repository.
    • src/
      • lib.rs does not match the repository.
      • slru.rs does not match the repository.

    Fetched https://git.sr.ht/~asyncth/wtinylfu 8f46314121682f30da1f4e3808c414e859dfd274.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

  • Dependency bloomfilter 1 is a bit outdated

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

    bloomfilter versions

  • Dependency lru 0.12 is a bit outdated

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

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

    lru versions

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