Thomas

I've taken a quick look. ```sh ❯ git switch -d 76c708fc979c1bfb65b4db300c654be08f096874 ❯ USE_BAZEL_VERSION=98d376faeb206f14838156ce4cb305ddbfce08fa bazel test //... --toolchain_resolution_debug ... INFO: ToolchainResolution: Type //toolchains/docker:toolchain_type: target platform @io_bazel_rules_docker//platforms:image_transition: Rejected toolchain @docker_config//:toolchain; mismatching values:...

I'm confused. The linked commit (https://github.com/bazelbuild/bazel/commit/98d376faeb206f14838156ce4cb305ddbfce08fa) is from January 2021, over a year ago. Has it only recently been merged? If not, what has now caused this problem? Whilst debugging...

Is this related? https://github.com/tweag/rules_haskell/issues/1657 It seems to be the same error message.

I think some tests would be a good idea. Would you be able to offer some guidance on where it would be appropriate to add said tests?

Sounds great, thanks! I have some pretty good ideas on how to tackle this and I think the implementation could be quite nice. I was thinking about the generator a...

I've made a prototype implementation and it looks pretty good so far. It has shown some weirdness with the format of the lockfile, but has been easy to work with...

Yep, of course. So here's an excerpt from the JSON lockfile (represented as [CUE](https://cuelang.org/) for brevity): ```cue "sha2 0.10.2": common_attrs: deps: selects: { "cfg(any(target_arch = \"aarch64\", target_arch = \"x86_64\", target_arch...

I completely overlooked the `conditions` in the lockfile, thanks! I think that will work fine. Is there a reference which explains the format of the lockfile? Something which isn't source...

So, I got it all working! :) Just need to clean some stuff up. Hopefully will open a PR for this within the next few days.

If you're interested, this is the dev branch: https://github.com/bazelbuild/rules_rust/compare/main...uhthomas:1287. There are a few more things to do, but it's possible to build and run the cargo-bazel binary with these changes...