Common crates in Cargo workspace recompiled due to different features

• abstreet

  56 7,303 8.9 Rust

  Transportation planning and traffic simulation software for creating cities friendlier to walking, biking, and public transit

  

I solved the problem by https://github.com/a-b-street/abstreet/commit/889c500eb1ea5ea9c1ae722759d7dcca99383e25 and https://github.com/a-b-street/abstreet/commit/60352747bf1af6e0d55022537f5af06b0ae0e1cb. Another thread here describes the process. Feel free to reach out if you hit similar issues and can't figure out how to workaround.

• cargo-feature-analyst

  1 45 0.0 Rust

  cargo-feature-analyst is a tool written in rust to analyse the feature usage in your rust project.

I've actually posted about this before and found a solution there: figuring out which transitive dependencies have different features enabled between the two binaries. Sadly, the tools that worked a year ago don't anymore. cargo-feature-analyst seemingly needs to handle Cargo.lock version 3, and this cargo tree PR has deviated too far from the recent repo anymore. I've tried some workflows trying to diff cargo tree -e features between the two binaries, but haven't found the issue yet.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• cargo-tree

  1 537 0.0 Rust

I've actually posted about this before and found a solution there: figuring out which transitive dependencies have different features enabled between the two binaries. Sadly, the tools that worked a year ago don't anymore. cargo-feature-analyst seemingly needs to handle Cargo.lock version 3, and this cargo tree PR has deviated too far from the recent repo anymore. I've tried some workflows trying to diff cargo tree -e features between the two binaries, but haven't found the issue yet.

Suggest a related project