Philipp Wollermann

@mhmyesman Could you explain what you mean with "Still not fixed in official releases"? It seems to work for me with Bazelisk 1.10.1 installed from Homebrew on my MacBook Pro...

IIUC this is a feature request that for Bazel versions before 4.1.0 (the first version that had Darwin arm64 binaries) you'd like Bazelisk to download the x86_64 version even on...

@aMiss-aWry There is no arm64 version of Bazel 4.0.0 for macOS, which is why that one fails to download. Bazel 5.0.0 is a major release that contains incompatible changes, so...

Huh... that failure on Windows is strange: > compilepkg: could not create directory for _empty.go: mkdir C:\b\2hhx3mgx\execroot\__main__\bazel-out\x64_windows-fastbuild\bin\platforms\github_com_bazelbuild_bazelisk_platforms: Cannot create a file when that file already exists. I don't immediately have...

The problem was that the flag is a startup flag, but Bazelisk doesn't understand that (granted, there's also no way to know that from looking at the issue), so it...

Nice idea and probably easier to implement than https://github.com/bazelbuild/bazelisk/pull/17. :)

@rayhoffmann-ANSYS Thanks for letting me know. We had false positives with Chrome’s malicious binary checking in the past and I had to escalate them with the team to get them...

I checked https://github.com/bazelbuild/bazelisk/releases/download/v1.6.1/bazelisk-windows-amd64.exe with virustotal.com and it came back all green (nothing detected). I’d assume a false positive, but would still like to resolve this. Any details about your virus...

@freddd Which version was the file that comes back red? Do you still have it? Oh, now I get it - if you upload the file it's red, but if...

OK, I figured it out. Apparently Go binaries that are built for Windows often result in false positives: - https://golang.org/doc/faq#virus - https://groups.google.com/g/golang-nuts/c/Au1FbtTZzbk Especially when you use `LDFLAGS="-s -w"`, which I...