Description of the bug:

If you work in a folder that has Japanese characters in it, running "bazel build" will fail (even "bazel info release" fails). Here's what happens when I try it on my Mint 21 install -

/tmp/ワーク:$ bazel build //...
Starting local Bazel server and connecting to it...
ERROR: Client cwd '/tmp/ワーク' is not inside workspace '/tmp/???'
/tmp/ワーク:$ 

That's an English installation of Mint 21. On Windows, I have a JP VM. i.e. the OS is in Japanese. I get a slightly different error -

C:\tmp\ウェブ>bazel build //...
FATAL: changing directory into c:\tmp\ウェブ failed: (error: 123): t@CAfBNgA܂̓{[ x̍\Ԉ��Ă܂B


C:\tmp\ウェブ>

The contents of the BUILD and WORKSPACE file don't matter (as far as I can tell).

Which category does this issue belong to?

Core

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

On Linux, you could type -

mkdir /tmp/ワーク
cd /tmp/ワーク
touch BUILD
touch WORKSPACE
bazel build //...

Which operating system are you running Bazel on?

Mint 21, Rocky 9 and Windows 10

What is the output of bazel info release?

/tmp/ワーク:$ bazel info release ERROR: Client cwd '/tmp/ワーク' is not inside workspace '/tmp/???'

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

I just installed release versions

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

I posted a question here - https://stackoverflow.com/questions/79047697/bazel-build-not-working-in-a-folder-with-non-ascii-japanese-characters
I found a similar issue reported here - #2550

Any other information, logs, or outputs that you want to share?

Since I can't get the "bazel info release" output, I can tell you that it's 7.1.0 on Linux and 7.3.2 on Windows. That's what --version shows. Same if I run bazel info release in an ASCII folder.