Skip to content

apply https://github.com/bazelbuild/rules_rust/pull/2116#3843

Closed
walter-zeromatter wants to merge 3 commits intobazelbuild:mainfrom
walter-zeromatter:user/wgray/fix-windows-path
Closed

apply https://github.com/bazelbuild/rules_rust/pull/2116#3843
walter-zeromatter wants to merge 3 commits intobazelbuild:mainfrom
walter-zeromatter:user/wgray/fix-windows-path

Conversation

@walter-zeromatter
Copy link

I'm reopening this fix rebased on main to try and get it merged in since this is blocking our migration to use bazel with our codebase

@google-cla
Copy link

google-cla bot commented Feb 4, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

walter-zeromatter and others added 2 commits February 5, 2026 17:27
- Use find_action_by_mnemonic for Rustdoc actions instead of assuming
  actions[0], since symlink actions now precede Rustdoc on Windows
- Deduplicate symlink deps by using only transitive_crates (which
  already includes direct_crates) to avoid conflicting actions

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@dzbarsky
Copy link
Contributor

dzbarsky commented Feb 8, 2026

I think hermeticbuild@f2f5b3d is a better approach as it avoids adding extra actions to the build graph and doesn't add additional depset flattening.

@walter-zeromatter
Copy link
Author

agreed, closing this in favor of that PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants