jason-ha
commented
1 month ago Just experienced again - this time directly using Windows VS Code (newer VSCode version too).
Full VS Code about:
Version: 1.91.1 (system setup)
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:06:49.809Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22631Log (partial):
[Info - 9:50:25 AM] Server initialized with PID: 14964
Reloading biome executable.
Biome binary found at d:\ff\FluidFramework\node_modules\.pnpm\@biomejs+cli-win32-x64@1.7.3\node_modules\@biomejs\cli-win32-x64\biome.exe
Copying binary to temporary folder: file:///c%3A/Users/username/AppData/Roaming/Code/User/workspaceStorage/85974bf9b18f42b60c268d05e426b998/biomejs.biome/biome.exe
Executing Biome from: c:\Users\username\AppData\Roaming\Code\User\workspaceStorage\85974bf9b18f42b60c268d05e426b998\biomejs.biome\biome.exe
[cli-stdout] data 29
[cli-stderr] end
[cli] exit 0
[cli-stdout] end
[cli-stderr] end
[cli-stdout] end
Connecting to "\\.\pipe\biome-service-1.7.3" ...
[cli-stderr] finish
[cli-stdout] finish
[cli-stderr] finish
[cli-stdout] finish
[Error - 9:50:37 AM] Biome client: couldn't create connection to server.
Error: connect ENOENT \\.\pipe\biome-service-1.7.3
at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)
Reloading client failed: Error: Could not connect to the Biome server at "\\.\pipe\biome-service-1.7.3": connect ENOENT \\.\pipe\biome-service-1.7.3
[cli-stdout] close
[cli-stderr] close
[cli] close 0
[cli-stdout] close
[cli] close 0
[cli-stderr] close
Reloading biome executable.
Biome binary found at d:\ff\FluidFramework\node_modules\.pnpm\@biomejs+cli-win32-x64@1.7.3\node_modules\@biomejs\cli-win32-x64\biome.exe
Copying binary to temporary folder: file:///c%3A/Users/username/AppData/Roaming/Code/User/workspaceStorage/85974bf9b18f42b60c268d05e426b998/biomejs.biome/biome.exe
Executing Biome from: c:\Users\username\AppData\Roaming\Code\User\workspaceStorage\85974bf9b18f42b60c268d05e426b998\biomejs.biome\biome.exe
[cli-stdout] data 29
[cli] exit 0
Connecting to "\\.\pipe\biome-service-1.7.3" ...
[Info - 9:50:58 AM] Server initialized with PID: 22648
Reloading biome executable.
Biome binary found at d:\ff\FluidFramework\node_modules\.pnpm\@biomejs+cli-win32-x64@1.7.3\node_modules\@biomejs\cli-win32-x64\biome.exe
Copying binary to temporary folder: file:///c%3A/Users/username/AppData/Roaming/Code/User/workspaceStorage/85974bf9b18f42b60c268d05e426b998/biomejs.biome/biome.exe
Executing Biome from: c:\Users\username\AppData\Roaming\Code\User\workspaceStorage\85974bf9b18f42b60c268d05e426b998\biomejs.biome\biome.exe
[cli-stderr] end
[cli-stdout] end
[cli-stderr] finish
[cli-stdout] finish
[cli-stdout] close
[cli] close 0
[cli-stderr] close
[cli-stdout] data 29
[cli] exit 0
Connecting to "\\.\pipe\biome-service-1.7.3" ...
[Info - 9:51:06 AM] Server initialized with PID: 23316
Sec-ant
nhedger
VS Code version
1.90.2
Extension version
2.3.0
Biome version
1.7.3
Operating system
Description
While using VS Code error pop-ups regularly appear about Biome not connecting to server. Most observable when switching back to VS Code window. I feel like I have seen this across all places I use Biome VS Code extension, but now that I am trying to capture instances of errors, I only see it on Linux (Ubuntu WSL on Windows 11).
Full VS Code about:
Steps to reproduce
Biome related vscode settings:
Expected behavior
No error pop-up just refocusing on VS Code
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Logs