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.

• uzers

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["os::unix-apis"] 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 = ["user-group", "user-id", "group-id", "user-name", "user-interface"] (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 'log' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'log' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.65, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• lrzcc-test

  • Missing categories

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

    List of available categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["name", "future", "claiming"] (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.

• wikijs

  • Dependency clap-verbosity-flag 2.0 is outdated

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

    clap-verbosity-flag versions

  • Dependency colored 2.0 is a bit outdated

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

    colored versions

  • Dependency fuser 0.14 is outdated

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

    fuser versions

  • Dependency graphql_client 0.13 is outdated

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

    graphql_client versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency tabled 0.15 is outdated

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

    tabled versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Missing keywords

    Help users find your crates. Add keywords = ["api-bindings", "wiki", "graphql", "graphql-client", "js"] (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 'fuser' 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 'fuser', 'log', 'libc', 'clap', 'clap-verbosity-flag', 'colored', 'stderrlog', 'tabled', 'tempfile', 'chrono' may have been unintentional.

    Crate features

• lrzcc-cli

  • 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 tabled 0.17 is outdated

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

    tabled versions

  • Missing keywords

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

• lrzcc-api

  • 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 strum 0.26 is outdated

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

    strum versions

  • Imprecise dependency requirement actix-web = 4

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

    actix-web versions

  • Missing keywords

    Help users find your crates. Add keywords = ["api-server", "cloud", "compute", "lrz", "applications"] (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.

• lrzcc

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

    anyhow versions

  • Missing keywords

    Help users find your crates. Add keywords = ["cloud", "api-bindings", "compute", "lrz", "client"] (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.

• lrzcc-lib

  • Missing categories

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

    List of available categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["name", "future", "claiming"] (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.

• jzon

  • 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 = ["encoding"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["json", "json-parser", "parse-json"] (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.

• ansiterm

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["terminal-text", "ansi-colors", "terminal-colors", "text-style", "text-formatting"] (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.

• lrzcc-wire

  • Dependency tabled 0.17 is outdated

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

    tabled versions

  • Missing keywords

    Help users find your crates. Add keywords = ["cloud", "compute", "api", "lrz", "communication"] (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.