If //tools/bazel points to bazelisk, infinite fork happens about bazelisk HOT 3 CLOSED

Sorry for that, @kellycampbell! I'll see that we fix this quickly.

Can you describe your setup in more detail, so that I can reproduce this on my machine?

• What is //tools/bazel exactly - a shell script that somehow executes Bazelisk (if yes, how) or Bazelisk itself?
• Are you using the Python version of Bazelisk or the Go version?

from bazelisk.

I believe we're using the Go version.

Here's our //tools/bazel:

#!/bin/bash

set -eu

BAZELISK_VERSION=0.0.4
BAZELISK_DIR="$(dirname "${BASH_SOURCE[0]}")/bazelisk"

if [ "$(uname -s)" == "Darwin" ]; then
    BAZELISK="${BAZELISK_DIR}/bazelisk-${BAZELISK_VERSION}-darwin-amd64"
elif [ "$(uname -s)" == "Linux" ]; then
    BAZELISK="${BAZELISK_DIR}/bazelisk-${BAZELISK_VERSION}-linux-x86_64"
fi

exec -a "$0" "${BAZELISK}" "$@"

This makes it so our devs only need to install a bazel script or recent version of bazel that executes tools/bazel if it exists. Then the bazelisk binary is run and the real version of bazel we want is downloaded and run via the .bazelversion file.

from bazelisk.

Thanks! I'll look into this and will get back to you tomorrow :)

from bazelisk.