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

Bazelisk fails with TLS handshake timeout on WSL2 #476

Open
andreas-0815-qwertz opened this issue Jun 26, 2023 · 2 comments
Open

Bazelisk fails with TLS handshake timeout on WSL2 #476

andreas-0815-qwertz opened this issue Jun 26, 2023 · 2 comments
Labels
P2 We'll consider working on this in future. (Assignee optional) type:bug Something isn't working

Comments

@andreas-0815-qwertz
Copy link

Whenever I run bazel through bazelisk (I tried 1.16.0 and 1.17.0), I get the following error:

2023/06/26 15:03:56 could not resolve the version 'latest' to an actual version number: unable to determine latest version: could not list Bazel versions in GCS bucket: could not list GCS objects at https://www.googleapis.com/storage/v1/b/bazel/o?delimiter=/: could not fetch https://www.googleapis.com/storage/v1/b/bazel/o?delimiter=/: Get "https://www.googleapis.com/storage/v1/b/bazel/o?delimiter=/": net/http: TLS handshake timeout

even, if I just try to execute bazel clean.

I am on WSL2 on a Windows machine, which accesses the web through a ZScaler proxy. As wget https://www.googleapis.com/storage/v1/b/bazel/o?delimiter=/ just works fine without any issues, I do not think it is a general proxy issue.

I am rather suspecting a certificate issue. While my system has the necessary root certificate for ZScaler middleman in /etc/ssl/cert (as witnessed by the wget-command), I doubt whether bazelisk uses this certificate. But I am not enough of a golang programmer to really know.

@andreas-0815-qwertz
Copy link
Author

Btw., creating a .bazelversion works around this issue for me.

@andreas-0815-qwertz
Copy link
Author

Forgot to mention that setting BAZELISK_BASE_URL does not help here, as listDirectoriesInReleaseBucket does not seem to use it.

@fweikert fweikert added type:bug Something isn't working P2 We'll consider working on this in future. (Assignee optional) labels Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants