-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Bazel crashes fetching http_archive dependency #14682
Comments
Can you provide the crash log please? |
WARNING: Download from https://github.com/buchgr/rules_jmh/zipball/6ccf8d7b270083982e5c143935704b9f3f18b256 failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException Checksum was f88fe443f17ae00bf759f4b5f2614dfc4bfddf9c558c2f3f470ffc51fcf96e85 but wanted dbb7d7e5ec6e932eddd41b910691231ffd7b428dff1ef9a24e4a9a59c1a1762d |
and this is our rules_dependency
|
This is not a crash. It's simply saying there was a checksum mismatch:
See relevant discussion at bazel-contrib/SIG-rules-authors#11 (comment) |
thank you. I don't see any activity on this project https://github.com/buchgr/rules_jmh |
GitHub had a temporary change today that caused all non-stable archives to have different checksums. The error log you provided indicates that the download was successful, but the checksum was different. (Whether a project is active or not has no bearing on the accessibility of its archives.) In any case, this isn't a Bazel bug. Please go to e.g. slack.bazel.build to discuss this. |
My google account does not end with google.com. Can you send me an invite [email protected] ? |
I realize its not a bazel bug. I'm asking if bazel provides a way to guard against this? and what makes this a non-stable archive? |
Bazel cannot guard against this, since you can point |
Description of the problem / feature request:
Bazel build crashes fetching http_archive rules dependency if its not accessible. What the best way to protect against this?
Feature requests: what underlying problem are you trying to solve with this feature?
Perhaps cache the dependency in bazel cache?
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
This is only reproducible if an http_archive dependency goes away. it happened today intermittently for https://github.com/buchgr/rules_jmh/zipball/6ccf8d7b270083982e5c143935704b9f3f18b256
What operating system are you running Bazel on?
ubuntu 18.04.1
What's the output of
bazel info release
?release 4.0.0
The text was updated successfully, but these errors were encountered: