You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When BAZELISK_BASE_URL is set and bazelisk fails to download Bazel from that URL, it would either throw an HTTPError or exit with 22. It should instead fallback to the default releases.bazel.build url
The text was updated successfully, but these errors were encountered:
I think the problem here is people use BAZELISK_BASE_URL because they forked the official repository and probably made some custom changes. Falling back to the official download is not what we expected.
The assumption is wrong. In one project we maintain a version internally with our tweaks and we keep the internal version align with the main public version (e.g. 6.0.0).
Even if we do not align the version strictly, I think it's still reasonable people map their internal version to an arbitrary public version (e.g. internal 4.0.0 -> public 6.0.0). It's wrong to assume 404 will definitely happen.
When BAZELISK_BASE_URL is set and bazelisk fails to download Bazel from that URL, it would either throw an HTTPError or exit with 22. It should instead fallback to the default releases.bazel.build url
The text was updated successfully, but these errors were encountered: