Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Builds spewing logs of the form "Rule indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "..."" #466

Open
rdelfin opened this issue Jan 25, 2022 · 0 comments

Comments

@rdelfin
Copy link

rdelfin commented Jan 25, 2022

I've been using cargo raze for some time in my repo. However, I've noticed that if I clear my cache and build from scratch I get a barrage of errors in the form:

DEBUG: Rule 'raze__ibverbs__0_4_2' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1615914885 +0000"
DEBUG: Repository raze__ibverbs__0_4_2 instantiated at:
  /home/rdelfin/code/WayveCode/WORKSPACE:565:25: in <toplevel>
  /home/rdelfin/code/WayveCode/3rdparty/rust/cargo/crates.bzl:933:10: in raze_fetch_remote_crates
  /home/rdelfin/.cache/bazel/_bazel_rdelfin/8ad2193c8c01fcec09f2187a53fcd3c9/external/bazel_tools/tools/build_defs/repo/utils.bzl:233:18: in maybe
Repository rule new_git_repository defined at:
  /home/rdelfin/.cache/bazel/_bazel_rdelfin/8ad2193c8c01fcec09f2187a53fcd3c9/external/bazel_tools/tools/build_defs/repo/git.bzl:186:37: in <toplevel>

It seems like Cargo raze is not adding an expected field to make the new_git_repository rules be in canonical form. Is cargo raze capable of generating these fields?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant