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.

• rclrs

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Crate tarball has been published from the commit f29144bfad5188aa98a75acdec4df166283f2376, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Could not discover crate's location in its repository (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • warning: There is no matching git tag containing version '0.4.1'.
    • 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:

    • build.rs not found.
    • package.xml not found.
    • README.md does not match the repository.
    • CHANGELOG.rst not found.
    • vendor_interfaces.py not found.
    • Cargo.toml.orig does not match the repository.
    • src/
      • client.rs not found.
      • rcl_bindings.rs not found.
      • time_source.rs not found.
      • node.rs not found.
      • subscription.rs not found.
      • rcl_wrapper.h not found.
      • context.rs not found.
      • qos.rs not found.
      • parameter.rs not found.
      • error.rs not found.
      • lib.rs not found.
      • wait.rs not found.
      • clock.rs not found.
      • time.rs not found.
      • dynamic_message.rs not found.
      • executor.rs not found.
      • service.rs not found.
      • publisher.rs not found.
      • arguments.rs not found.
    • error.rs not found.
    • src/node/
      • graph.rs not found.
      • builder.rs not found.
    • src/parameter/
      • service.rs not found.
      • value.rs not found.
      • override_map.rs not found.
    • loaned_message.rs not found.
    • src/subscription/
      • readonly_loaned_message.rs not found.
      • callback.rs not found.
      • message_info.rs not found.
    • mod.rs not found.
    • src/vendor/builtin_interfaces/
      • mod.rs not found.
      • msg.rs not found.
    • src/vendor/rcl_interfaces/
      • mod.rs not found.
      • srv.rs not found.
      • msg.rs not found.
    • src/vendor/rosgraph_msgs/
      • mod.rs not found.
      • msg.rs not found.
    • src/wait/
      • exclusivity_guard.rs not found.
      • guard_condition.rs not found.

    Fetched https://github.com/bresilla/rclrs.git 1c4a84d3d10fee244daceaeba8390f1429b51987.

    Checked on 2024-08-04

    This check is experimental.

    Forum thread

  • 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 bindgen 0.66.1 is significantly outdated

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

    bindgen versions

  • Dependency ament_rs 0.2 is slightly outdated

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

    ament_rs versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["science::robotics"] 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 = ["ros", "client", "applications", "framework", "robot"] (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 'libloading' 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 'libloading', 'ament_rs' may have been unintentional.

    Crate features

• rosidl_runtime_rs

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

  • Imprecise dependency requirement serde = 1

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

    serde versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["ros", "message", "robotics", "generation", "framework"] (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.

• cargo-ament-build

  • Dependency pico-args 0.4 is significantly outdated

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

    pico-args 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.

    anyhow versions

  • Dependency cargo-manifest 0.2 is outdated

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

    cargo-manifest versions

• whip-up

  • Dependency syn 1.0.16 is significantly outdated

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

    syn versions

  • Dependency clap 2.33.0 is outdated

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

    clap versions

  • Latest stable release is old

    It's been over 4 years. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["strong-typing", "build-system", "whip", "file"] (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.

No issues found in: statistics_msgs shape_msgs lifecycle_msgs std_srvs stereo_msgs diagnostic_msgs rosgraph_msgs rcl_interfaces nav_msgs action_msgs sensor_msgs lanelet_msgs geometry_msgs unique_identifier_msgs std_msgs builtin_interfaces

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