[Windows] bazel.exe crash on paths with Cyrillic characters
See original GitHub issueDescription of the problem / feature request / question:
Application bazel.exe or bazel-0.5.4-without-jdk-windows-x86_64.exe crash at startup even without parameter
If possible, provide a minimal example to reproduce the problem:
Just run exe-file
Environment info
-
Operating System: Microsoft Windows [Version 10.0.15063]
-
Bazel version (output of
bazel info release
): 0.5.4
Have you found anything relevant by searching the web?
No
Anything else, information or logs or outputs that would be helpful?
Full dump bazel.zip
Issue Analytics
- State:
- Created 6 years ago
- Comments:35 (20 by maintainers)
Top Results From Across the Web
Writing Rules on Windows - Bazel
This page focuses on writing Windows-compatible rules, common problems of writing portable rules, and some solutions. Paths. Problems: Length limit: maximum ...
Read more >Cyrillic characters appear as garbage text in the output ...
Bug: The output window shows garbage text instead of the cyrillic characters. Seems like an encoding problem. The output is English, which seems...
Read more >Mingw-w64 toolchain for Bazel (Ubuntu 20.04.1 )
the executable 'Hello-world.exe' is created succesfully. Any suggestion on what is going wrong? Below, my toolchain BUILD file package( ...
Read more >Obscure build failure on Windows after Bazel commit ...
Here the problem appears to be that Bazel tries to build intermediary DLLs, which doesn't work well on Windows because DLLs don't export...
Read more >Bug listing with status UNCONFIRMED as at 2022/12/12 00 ...
Microsoft ® SQL Server® ODBC Driver 1.0 for Linux" status:UNCONFIRMED ... doesn't work for russian letters" status:UNCONFIRMED resolution: severity:normal ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Acknowledging that this is a problem, I’m still dropping the priority to P3. Reason being that the rest of Bazel doesn’t work well with non-ASCII paths anyway (labels for example don’t support non-ASCII paths), and the Windows team doesn’t have capacity to fix the rest of Bazel. I’m sad to say that I don’t realistically see fixing this any time in the next few months.
Thanks for issue status