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.

• roci

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit 01beea75884fff5c89ba37946d298956848810bd, 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: Cargo.toml parse error: Cargo.toml.orig workspace error: can't load root workspace.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: Can't find workspace in /libs/roci/...
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.
    • error: Dependencies don't match: 'impeller' uses workspace inheritance, but the root workspace is not available.
    • error: Dependencies don't match: 'nox' uses workspace inheritance, but the root workspace is not available.
    • error: Dependencies don't match: 'roci-macros' uses workspace inheritance, but the root workspace is not available.
    • error: Manifest properties don't match: package.version.

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

    • Cargo.toml.orig does not match the repository.

    Looked for the crate in libs/roci/. Fetched https://github.com/elodin-sys/elodin.git 3ae70b203cf02c93e0e19aca084dddbcbbe98fee.

    Checked on 2024-08-25

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement fastrand = 2

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

    fastrand versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["simulation"] 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 = ["aerospace", "flight", "ecs", "physics-simulation", "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.

  • Optional dependency 'serde' 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 'serde', 'fastrand', 'tokio-stream', 'tokio-util' may have been unintentional.

    Crate features

• noxla

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: can't load root workspace.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: Can't find workspace in //...
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.
    • error: Manifest properties don't match: package.version.
      • If you have a monorepo, you can use git tags in format cratename/v0.4.0

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

    • build.rs exists, but elsewhere in the repo.
    • README.md not found.
    • LICENSE exists, but elsewhere in the repo.
    • Cargo.toml not found.
    • src/
      • client.rs exists, but elsewhere in the repo.
      • hlo_module.rs exists, but elsewhere in the repo.
      • shape.rs exists, but elsewhere in the repo.
      • tests.rs exists, but elsewhere in the repo.
      • literal.rs exists, but elsewhere in the repo.
      • buffer.rs exists, but elsewhere in the repo.
      • sys.rs exists, but elsewhere in the repo.
      • native_type.rs exists, but elsewhere in the repo.
      • computation.rs exists, but elsewhere in the repo.
      • op.rs exists, but elsewhere in the repo.
      • element_type.rs exists, but elsewhere in the repo.
      • error.rs exists, but elsewhere in the repo.
      • executable.rs exists, but elsewhere in the repo.
      • lib.rs exists, but elsewhere in the repo.
      • builder.rs exists, but elsewhere in the repo.
    • handle_pool.h exists, but elsewhere in the repo.
    • vendor/jaxlib/
      • handle_pool.h exists, but elsewhere in the repo.
      • kernel_helpers.h exists, but elsewhere in the repo.
    • vendor/jaxlib/cpu/
      • lapack_kernels_using_lapack.cc exists, but elsewhere in the repo.
      • cpu_kernels.cc exists, but elsewhere in the repo.
      • lapack_kernels.cc exists, but elsewhere in the repo.
      • lapack_kernels.h exists, but elsewhere in the repo.
    • vendor/jaxlib/gpu/
      • cholesky_update_kernel.cu.cc exists, but elsewhere in the repo.
      • gpu_kernels.cc exists, but elsewhere in the repo.
      • cholesky_update_kernel.h exists, but elsewhere in the repo.
      • triton.pb.cc exists, but elsewhere in the repo.
      • rnn_kernels.cc exists, but elsewhere in the repo.
      • prng.cc exists, but elsewhere in the repo.
      • triton_kernels.h exists, but elsewhere in the repo.
      • solver_kernels.h exists, but elsewhere in the repo.
      • triton.pb.h exists, but elsewhere in the repo.
      • lu_pivot_kernels.cu exists, but elsewhere in the repo.
      • rnn_kernels.h exists, but elsewhere in the repo.
      • solver.cc exists, but elsewhere in the repo.
      • prng_kernels.cc exists, but elsewhere in the repo.
      • sparse.cc exists, but elsewhere in the repo.
      • blas_kernels.cc exists, but elsewhere in the repo.
      • gpu_kernel_helpers.cc exists, but elsewhere in the repo.
      • triton.proto exists, but elsewhere in the repo.
      • linalg.cc exists, but elsewhere in the repo.
      • sparse_kernels.h exists, but elsewhere in the repo.
      • prng_kernels.cu exists, but elsewhere in the repo.
    • ffi_api.h exists, but elsewhere in the repo.
    • vendor/xla/ffi/api/
      • c_api.h exists, but elsewhere in the repo.
      • ffi.h exists, but elsewhere in the repo.

    Fetched https://github.com/elodin-sys/elodin.git db9d911791030bbe792c5864c27ed83763360d1c.

    Checked on 2024-08-25

    Forum thread

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

    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.

    thiserror versions

  • 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 lapack-src 0.10 is outdated

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

    lapack-src versions

  • Dependency lapack-sys 0.14.0 is a bit outdated

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

    lapack-sys versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Dependency ureq 2.9.7 is a bit outdated

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

    ureq versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["linear-algebra", "machine-learning", "bindings", "xla", "compiler"] (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.

• impeller

  • Dependency arrow 52.0 is significantly outdated

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

    arrow versions

  • Dependency hashbrown 0.14.3 is significantly outdated

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

    hashbrown versions

  • Dependency bevy 0.14 is outdated

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

    bevy versions

  • Dependency big_space 0.7.0 is outdated

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

    big_space versions

  • Dependency polars 0.41 is outdated

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

    polars versions

  • Dependency polars-arrow 0.41 is outdated

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

    polars-arrow versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit 7145ddabf65f353c06b256f142d383148c5730dd, 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: Cargo.toml parse error: Cargo.toml.orig workspace error: can't load root workspace.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: Can't find workspace in /libs/impeller/...
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.
    • error: Dependencies don't match: 'nox' uses workspace inheritance, but the root workspace is not available.
    • error: Manifest properties don't match: package.version.

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

    • Cargo.toml.orig does not match the repository.
    • src/
      • polars.rs does not match the repository.
      • ser_de.rs does not match the repository.

    Looked for the crate in libs/impeller/. Fetched https://github.com/elodin-sys/elodin.git 3ae70b203cf02c93e0e19aca084dddbcbbe98fee.

    Checked on 2024-08-25

    Forum thread

  • Imprecise dependency requirement fastrand = 2

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

    fastrand versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["ecs", "physics-simulation", "protocols", "systems", "aerospace"] (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 'big_space' 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 'big_space', 'futures', 'fastrand', 'polars-arrow', 'nalgebra', 'arrow', 'tracing', 'tokio-util' may have been unintentional.

    Crate features

• nox

  • Dependency itertools 0.12.0 is significantly outdated

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

    itertools versions

  • Dependency pyo3 0.21.0 is significantly outdated

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

    pyo3 versions

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

    Detecting docs.rs

  • Dependency dyn-stack 0.10.0 is outdated

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

    dyn-stack versions

  • Dependency faer 0.19.1 is outdated

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

    faer versions

  • Dependency fn-traits 0.1.2 is slightly outdated

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

    fn-traits versions

  • Dependency lapack-src 0.10 is outdated

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

    lapack-src versions

  • Dependency numpy 0.21.0 is outdated

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

    numpy versions

  • Dependency simba 0.8.1 is outdated

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

    simba versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit 20fd871bc6ab91be7f858cbde70dc2bff6a6e423, 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: Cargo.toml parse error: Cargo.toml.orig workspace error: can't load root workspace.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: Can't find workspace in /libs/nox/...
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.
    • error: Dependencies don't match: 'xla' uses workspace inheritance, but the root workspace is not available.
    • error: Manifest properties don't match: package.version.

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

    • Cargo.toml.orig does not match the repository.

    Looked for the crate in libs/nox/. Fetched https://github.com/elodin-sys/elodin.git 031041325e6bde1884244141d136ce9d5b7d2cd8.

    Checked on 2024-08-25

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["tensor", "physics-simulation", "compile", "aerospace", "xla"] (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 'numpy' 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 'numpy', 'lapack-src', 'pyo3' may have been unintentional.

    Crate features

• roci, impeller, nox, roci-macros, aleph, stellarator, s10

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• roci, impeller, nox, roci-macros

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/elodin\-sys/elodin\.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.

• roci-macros

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit 01beea75884fff5c89ba37946d298956848810bd, 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: Cargo.toml parse error: Cargo.toml.orig workspace error: can't load root workspace.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: Can't find workspace in /libs/roci/macros/...
    • error: Manifest properties don't match: package.version.

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

    • Cargo.toml.orig does not match the repository.

    Looked for the crate in libs/roci/macros/. Fetched https://github.com/elodin-sys/elodin.git 3ae70b203cf02c93e0e19aca084dddbcbbe98fee.

    Checked on 2024-08-25

    Forum thread

  • Dependency convert_case 0.6.0 is a bit outdated

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

    convert_case versions

• aleph, stellarator, s10, elodin

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

• elodin

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

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