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.

• cfavml

  • Dependency blas-src 0.8 is outdated

    Upgrade to 0.11.1 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.

    blas-src versions

  • Dependency ndarray 0.15.6 is outdated

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

    ndarray versions

  • Dependency rand_chacha 0.3.1 is outdated

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

    rand_chacha versions

  • Dependency simsimd 5.0.1 is outdated

    Upgrade to 6.4.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.

    simsimd versions

• cfavml, datacake-node, datacake-eventual-consistency

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

• datacake-chitchat-fork

  • 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

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/lnx\-search/chitchat\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • 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.

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["fork", "github", "datacake", "own", "com-quickwit-oss-chitchat"] (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.

• rewrk

  • 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 clap 2 is outdated

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

    clap versions

  • Dependency colored 2 is a bit outdated

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

    colored versions

  • Dependency http 0.2 is outdated

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

    http versions

  • Dependency hyper 0.14 is outdated

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

    hyper 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 tower 0.4 is outdated

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

    tower versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["benchmark", "http-request", "framework", "connection", "server"] (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.

• datacake-rpc

  • Dependency http 0.2.8 is outdated

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

    http versions

  • Dependency hyper 0.14.23 is outdated

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

    hyper versions

  • Dependency turmoil 0.4.0 is outdated

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

    turmoil versions

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'asyncronous', which isn't a category we recognize

    lib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.

    List of available categories

  • Optional dependency 'async-stream' 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 'async-stream', 'turmoil' may have been unintentional.

    Crate features

• datacake-rpc, datacake-node, datacake-eventual-consistency, rewrk, datacake-sqlite, rewrk-core

  • 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

• datacake-crdt

  • Dependency thiserror 1.0.33 is a bit outdated

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

    thiserror versions

• datacake-crdt, datacake-rpc, datacake-node, datacake-eventual-consistency

  • Dependency rkyv 0.7.42 is a bit outdated

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

    rkyv versions

• datacake-rpc, datacake-node, datacake-eventual-consistency, datacake-sqlite, datacake-lmdb, rewrk-core

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• datacake-lmdb

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Dependency flume 0.10 is outdated

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

    flume versions

  • Dependency heed 0.20.0-alpha.0 is a bit outdated

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

    heed versions

• datacake-node, datacake-eventual-consistency, puppet, datacake-sqlite, rewrk-core

  • Dependency flume 0.10.14 is outdated

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

    flume versions

• puppet

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing categories

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

    List of available categories

• datacake-eventual-consistency

  • Dependency itertools 0.10.3 is outdated

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

    itertools versions

• rewrk-core

  • Dependency http 0.2 is outdated

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

    http versions

  • Dependency hyper 0.14 is outdated

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

    hyper versions

  • Dependency tower 0.4 is outdated

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

    tower versions

• datacake-sqlite

  • Dependency rusqlite 0.28.0 is outdated

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

    rusqlite versions

• puppet-derive

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

  • Dependency darling 0.14.2 is significantly outdated

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

    darling versions

No issues found in: datacake datacake-cluster datacake-rocks

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