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
Following build from source documentation, I tried to install all necessary dependencies and build ray, somehow on github codespace I cannot access bazel binary after a successful installation.
bazel --version does output expected version after installation
while it cannot be located in my shell env
Platform information
@SaSikun ➜ /workspaces/ray (master) $ uname -a
Linux codespaces-b37228 6.5.0-1025-azure #26~22.04.1-Ubuntu SMP Thu Jul 11 22:33:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
@SaSikun ➜ /workspaces/ray (master) $ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
Versions / Dependencies
N/A
Reproduction script
ci/env/install-bazel.sh
Issue Severity
Low: It annoys or frustrates me.
The text was updated successfully, but these errors were encountered:
SaSikun
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Dec 28, 2024
I think our setup script doesn't handle default executable installation path for github codespace, for example appending /home/codespace/bin/bazel to your PATH should work.
On fixing the script, add one line at the end export PATH=$PATH:$(which bazel) should work
dentiny
removed
the
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
label
Dec 28, 2024
What happened + What you expected to happen
Following build from source documentation, I tried to install all necessary dependencies and build ray, somehow on github codespace I cannot access
bazel
binary after a successful installation.bazel --version
does output expected version after installationPlatform information
Versions / Dependencies
N/A
Reproduction script
ci/env/install-bazel.sh
Issue Severity
Low: It annoys or frustrates me.
The text was updated successfully, but these errors were encountered: