Environment information
Details
$ biome rage
CLI:
Version: 2.4.11
Color support: true
Platform:
CPU Architecture: x86_64
OS: linux
Environment:
BIOME_LOG_PATH: unset
BIOME_LOG_PREFIX_NAME: unset
BIOME_LOG_LEVEL: unset
BIOME_LOG_KIND: unset
BIOME_CONFIG_PATH: unset
BIOME_THREADS: unset
BIOME_WATCHER_KIND: unset
BIOME_WATCHER_POLLING_INTERVAL: unset
NO_COLOR: unset
TERM: xterm-256color
JS_RUNTIME_VERSION: unset
JS_RUNTIME_NAME: unset
NODE_PACKAGE_MANAGER: unset
Biome Configuration:
Status: Loaded successfully
Path: biome.json
Formatter enabled: true
Linter enabled: true
Assist enabled: true
VCS enabled: false
HTML full support enabled: unset
Workspace:
Open Documents: 0
What happened?
This is a follow up to #9357. I'm now able to see the file, but it's not clear why I am getting this error. The error is flaky and not consistent. I am only able to reproduce in CI, but not locally which makes this difficult to provide a reproduction.
/home/repo/biome.json internalError/fs INTERNAL ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
× The file /home/repo/biome.json does not exist in the workspace.
! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.
/home/repo/project/dir/biome.json internalError/fs INTERNAL ━━━━━━━━━━━━━━━━━━━
× The file /home/repo/project/dir/biome.json does not exist in the workspace.
! This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.
configuration ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
× Biome exited because the configuration resulted in errors. Please fix them.
Expected result
I don't know if this is an error in my set up, or if this is a bug in biome; so, a more verbose error would probably be most helpful. The file exists, why is it not in the workspace? It's interesting that the error is always about biome.jsons.
Code of Conduct
Environment information
Details
What happened?
This is a follow up to #9357. I'm now able to see the file, but it's not clear why I am getting this error. The error is flaky and not consistent. I am only able to reproduce in CI, but not locally which makes this difficult to provide a reproduction.
Expected result
I don't know if this is an error in my set up, or if this is a bug in biome; so, a more verbose error would probably be most helpful. The file exists, why is it not in the workspace? It's interesting that the error is always about biome.jsons.
Code of Conduct