Closed mccoey01 closed 1 year ago
Pinging @elastic/kibana-operations (Team:Operations)
The cause of this error was the \ in the file:///home/mccoey01/.cache/bazel/_bazel_DS%5Cmccoey01/ directory.
"DS\mccoey01" is my username, and looks like that path is the result of bazel using ${whoami} in building up the cache directory. I was able to edit the .bazelrc file, and change bazel to override that directory using startup --output_user_root=~/.cache/bazel/mccoey01_user_dir
Now I am able to get beyond that point, but it's failing with another error, for [bazel] SystemError [ERR_SYSTEM_ERROR]: [BABEL]: A system error occurred: uv_os_homedir returned ENOENT (no such file or directory) (While processing: /home/mccoey01/.cache/bazel/mccoey01_user_dir/683ff3c4abc2a3e72223dec2b452aa88/sandbox/linux-sandbox/15/execroot/kibana/node_modules/@babel/preset-env/lib/index.js)
/home/mccoey01/.cache/bazel/mccoey01_user_dir/683ff3c4abc2a3e72223dec2b452aa88 - and it is writing other things to that directory, but there is no 'sandbox' directory in that path
@mccoey01 are you still experiencing this issue? Using the Amazon Linux 2 image from six days ago, I was able to setup and run Kibana from source without any extra configuration.
Closing due to inactivity and unable to reproduce. If this is still an issue feel free to reopen.
Kibana version: 8.5.0
Elasticsearch version: 8.5.0
Server OS version: Amazon Linux 2
Browser version: N/A
Browser OS version: N/A
Original install method (e.g. download page, yum, from source, etc.): From source
Describe the bug: Cloned the kibana repository and attempted to 'yarn kbn bootstrap' but it fails to complete on an error validating the re2 node module
Steps to reproduce:
Expected behavior: Ability to build Kibana from source (as-is, without any changes)
Screenshots (if relevant): N/A
Errors in browser console (if relevant): N/A
Provide logs and/or server output (if relevant):
Any additional context: Seems very similar to #139598; I am able to consistently reproduce the problem. I've tried force-install, clean, reset. It fails on v8.4.1 and v8.5.0 tags. It can't find re2, so it tried to download it. I think it downloads, but then it tries to validate the download, and I guess that fails - because then it starts building locally. And the local build fails. I am able to reach the URL, https://us-central1-elastic-kibana-184716.cloudfunctions.net/kibana-ci-proxy-cache/node-re2/uhop/node-re2/releases/download/1.17.4/linux-x64-93.br, and the .br file downloads. I do see an re2 directory in home/mccoey01/Development/kibana/node_modules/