-
-
Notifications
You must be signed in to change notification settings - Fork 16.2k
bazel-watcher: 0.5.0 -> 0.9.0 #51723
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
Conversation
49be769
to
fb366a5
Compare
cc @kalbasit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm on vacation until the 26th with limited internet and no laptop. The code looks great, but I'd love to make sure it runs before approving. /cc @Mic92 if he's available to review.
@GrahamcOfBorg build bazel-watcher |
I got locally:
|
I got
I think the |
Sorry was on vacation too. Will take a look. |
Seems like the binaries include the output path in them, and
|
why is this a fixed-input derivation anyway? |
The whole derivation isn't fixed output, but the dependencies Bazel will download are. Unfortunately some of the dependencies it downloads also end up building native code. |
You just gave me an idea though. |
fb366a5
to
52c0fbb
Compare
52c0fbb
to
6c30139
Compare
Done, change it to delete the gazelle binary tools since they can be rebuilt during the build, because it doesn't require accessing the network. |
cool, let me give it another try! Thank you @uri-canva for working on this! |
Motivation for this change
Upgrade
bazel-watcher
so that it can be built with newer versions of Bazel.Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)