🐛 error access vscode extensions #20

wcastand · 2023-09-15T16:11:32Z

Environment information

biome rage return :

Rage discovered this running server using an incompatible version of Biome.

Server:
  Version:                      1.1.2

yarn v3 on a monorepo.

What happened?

update vscode extension got an error:

Biome client: couldn't create connection to server.

/node_modules/.bin/biome: Permission denied

Discord asked me to run this command and it fixed the issue:

chmod +x ./node_modules/.bin/biome

been asked to reference this issue: rome/tools#3800

Expected result

update the vscode extension and it works

Code of Conduct

I agree to follow Biome's Code of Conduct

The text was updated successfully, but these errors were encountered:

nhedger · 2023-09-15T16:15:24Z

Could you provide a repository that reproduces this issue? This would help a lot.

wcastand · 2023-09-15T16:16:28Z

sorry but at work so not really the time, plus no idea why it happened so can't really reproduce. i just update my vscode extensions :/ someone on discord asked me to report the issue so here i am but not sure i will be a great help. :/

Conaclos · 2023-09-15T16:23:52Z

Which OS do you use?

Vivalldi · 2023-09-15T16:23:59Z

Same thing here. It's failing on macOS for me

Here's a rage I took before applying permission change

CLI:
  Version:                      1.2.0
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v18.14.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "yarn/3.6.1"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 true

Workspace:
  Open Documents:               0

Discovering running Biome servers...

Server:
  Status:                       stopped

Incompatible Biome Server: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

i Rage discovered this running server using an incompatible version of Biome.

Server:
  Version:                      1.1.0

Incompatible Biome Server: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

i Rage discovered this running server using an incompatible version of Biome.

Server:
  Version:                      1.1.2

Conaclos · 2023-09-15T16:25:13Z

I have no issue with npm on linux. Maybe a yarn-specific issue?

nhedger · 2023-09-15T16:31:09Z

I just tested with Yarn 3 on macOS with Biome 1.2.0 and had no issues.

wcastand · 2023-09-15T16:34:17Z

my biome rage is kind of a nightmare
https://gist.github.com/wcastand/dd2e74cdd59d350243cd8a444a1aa517

nhedger · 2023-09-15T16:39:13Z

Could you please:

Delete your node_modules folder
Reinstall your modules by running yarn
Run the following command ls -la node_modules/.bin/biome and paste the output here

Vivalldi · 2023-09-15T16:44:27Z

I've been able to reproduce by doing the following

Delete node_modules
Install biome vscode extension 1.2.2
Install biome at 1.1.2
Open a ts file to trigger biome extension

Perform double update
5. Install biome @ 1.2.0
6. Install latest biome vscode extension
7. Reload vscode window (focus ts file if you need)
8. Get Biome client: couldn't create connection to server. error

Output of ls -la

lrwxr-xr-x  1 cosgrove  staff  27 Sep 15 12:36 node_modules/.bin/biome -> ../@biomejs/biome/bin/biome

Rage

CLI:
  Version:                      1.2.0
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v18.14.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "yarn/3.6.1"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 true

Workspace:
  Open Documents:               0

Discovering running Biome servers...

Running Biome Server: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

i The client isn't connected to any server but rage discovered this running Biome server.

Server:
  Version:                      1.2.0
  Name:                         biome_lsp
  CPU Architecture:             aarch64
  OS:                           macos

Workspace:
  Open Documents:               0

Other Active Server Workspaces:

Workspace:
  Open Documents:               0
  Client Name:                  Visual Studio Code
  Client Version:               1.82.2

Biome Server Log:

! Please review the content of the log file before sharing it publicly as it may contain sensitive information:
  * Path names that may reveal your name, a project name, or the name of your employer.
  * Source code

###### last few lines below #####
├─2041630ms ERROR tower_lsp::transport failed to encode message: failed to encode response: Socket is not connected (os error 57)
├─┐biome_lsp::server::initialize{capabilities=ClientCapabilities { workspace: None, text_document: None, window: None, general: None, experimental: None }, client_info=ClientInfo { name: "biome_service", version: Some("1.2.0") }}
│ ├─0ms INFO biome_lsp::server Starting Biome Language Server...
├─┘
├─┐biome_lsp::server::biome/rage{params=RageParams}
├─┘
├─2046625ms ERROR tower_lsp::transport failed to encode message: failed to encode response: Socket is not connected (os error 57)

Incompatible Biome Server: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

i Rage discovered this running server using an incompatible version of Biome.

Server:
  Version:                      1.1.0

Incompatible Biome Server: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

i Rage discovered this running server using an incompatible version of Biome.

Server:
  Version:                      1.1.2

quantizor · 2023-09-15T16:54:38Z

This just popped up after upgrading to 1.2

Error - 12:51:43 PM] Biome client: couldn't create connection to server.
Error: Command "/Users/esj/code/frontend-v2/node_modules/.bin/biome __print_socket" exited with code 126
Output:
/bin/sh: /Users/esj/code/frontend-v2/node_modules/.bin/biome: Permission denied

	at getSocket (/Users/esj/.vscode/extensions/biomejs.biome-1.4.0-darwin-arm64/out/main.js:19600:11)

ℹ Rage discovered this running server using an incompatible version of Biome.

Server:
  Version:                      1.1.2

yarn.lock

"@biomejs/biome@npm:^1.2.0":
  version: 1.2.0
  resolution: "@biomejs/biome@npm:1.2.0"
  dependencies:
    "@biomejs/cli-darwin-arm64": 1.2.0
    "@biomejs/cli-darwin-x64": 1.2.0
    "@biomejs/cli-linux-arm64": 1.2.0
    "@biomejs/cli-linux-x64": 1.2.0
    "@biomejs/cli-win32-arm64": 1.2.0
    "@biomejs/cli-win32-x64": 1.2.0
  dependenciesMeta:
    "@biomejs/cli-darwin-arm64":
      optional: true
    "@biomejs/cli-darwin-x64":
      optional: true
    "@biomejs/cli-linux-arm64":
      optional: true
    "@biomejs/cli-linux-x64":
      optional: true
    "@biomejs/cli-win32-arm64":
      optional: true
    "@biomejs/cli-win32-x64":
      optional: true
  bin:
    biome: bin/biome
  checksum: 952f9faa1e8b814807829e0e46b8fe77382abf5d73659c8825c28971367ce062f75ffec66dcdd75aa706cdd01abc146b013d665a69373bab961ca33e6df327d2
  languageName: node
  linkType: hard

"@biomejs/cli-darwin-arm64@npm:1.2.0":
  version: 1.2.0
  resolution: "@biomejs/cli-darwin-arm64@npm:1.2.0"
  conditions: os=darwin & cpu=arm64
  languageName: node
  linkType: hard

"@biomejs/cli-darwin-x64@npm:1.2.0":
  version: 1.2.0
  resolution: "@biomejs/cli-darwin-x64@npm:1.2.0"
  conditions: os=darwin & cpu=x64
  languageName: node
  linkType: hard

"@biomejs/cli-linux-arm64@npm:1.2.0":
  version: 1.2.0
  resolution: "@biomejs/cli-linux-arm64@npm:1.2.0"
  conditions: os=linux & cpu=arm64
  languageName: node
  linkType: hard

"@biomejs/cli-linux-x64@npm:1.2.0":
  version: 1.2.0
  resolution: "@biomejs/cli-linux-x64@npm:1.2.0"
  conditions: os=linux & cpu=x64
  languageName: node
  linkType: hard

"@biomejs/cli-win32-arm64@npm:1.2.0":
  version: 1.2.0
  resolution: "@biomejs/cli-win32-arm64@npm:1.2.0"
  conditions: os=win32 & cpu=arm64
  languageName: node
  linkType: hard

"@biomejs/cli-win32-x64@npm:1.2.0":
  version: 1.2.0
  resolution: "@biomejs/cli-win32-x64@npm:1.2.0"
  conditions: os=win32 & cpu=x64
  languageName: node
  linkType: hard

How could an old version be hanging around after upgrade?

Even weirder:

yarn biome version
CLI:        1.2.0
Server:     not connected

Starting and stopping via yarn biome stop && yarn biome start did not fix the apparently running older version of the server.

After clearing out node_modules and reinstalling, the error goes away. So it looks like there might be an issue around disposal of prior versions.

harrytran998 · 2023-09-17T07:17:19Z

Same issue here, hope your team can fix this!

/bin/sh: project_path/node_modules/.bin/biome: Permission denied
at getSocket (/Users/.vscode/extensions/biomejs.biome-1.4.2-darwin-x64/out/main.js:19600:11)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
	at async createMessageTransports (/Users/.vscode/extensions/biomejs.biome-1.4.2-darwin-x64/out/main.js:19615:16)
	at async LanguageClient2.createConnection (/Users/.vscode/extensions/biomejs.biome-1.4.2-darwin-x64/out/main.js:15576:28)
	at async LanguageClient2.start (/Users/.vscode/extensions/biomejs.biome-1.4.2-darwin-x64/out/main.js:15152:30)
	at async activate (/Users/.vscode/extensions/biomejs.biome-1.4.2-darwin-x64/out/main.js:19421:3)
	at async E.n (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:107:6206)
	at async E.m (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:107:6169)
	at async E.l (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:107:5626)
[cli-stderr] finish

nhedger · 2023-10-06T18:50:11Z

Hey 👋, this issue may be fixed in the latest nightly version.

Could you try it and tell us if you're still experiencing the issue?

Here's the command to install the nightly version

code --install-extension [email protected]

After your tests, you can revert to the current stable version with the following command.

code --install-extension [email protected]

ematipico · 2023-11-26T15:42:01Z

It's been 2 months since the last message, I assume the bug is fixed.

If anybody happens to arrive here, please open a new issue.

nhedger mentioned this issue Oct 6, 2023

fix(vscode): biome resolution biomejs/biome#492

Merged

12 tasks

nhedger transferred this issue from biomejs/biome Nov 26, 2023

ematipico closed this as completed Nov 26, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

🐛 error access vscode extensions #20

🐛 error access vscode extensions #20

wcastand commented Sep 15, 2023 •

edited

Loading

nhedger commented Sep 15, 2023

wcastand commented Sep 15, 2023 •

edited

Loading

Conaclos commented Sep 15, 2023

Vivalldi commented Sep 15, 2023 •

edited

Loading

Conaclos commented Sep 15, 2023

nhedger commented Sep 15, 2023

wcastand commented Sep 15, 2023 •

edited

Loading

nhedger commented Sep 15, 2023

Vivalldi commented Sep 15, 2023 •

edited

Loading

quantizor commented Sep 15, 2023 •

edited

Loading

harrytran998 commented Sep 17, 2023

nhedger commented Oct 6, 2023

ematipico commented Nov 26, 2023

🐛 error access vscode extensions #20

🐛 error access vscode extensions #20

Comments

wcastand commented Sep 15, 2023 • edited Loading

Environment information

What happened?

Expected result

Code of Conduct

nhedger commented Sep 15, 2023

wcastand commented Sep 15, 2023 • edited Loading

Conaclos commented Sep 15, 2023

Vivalldi commented Sep 15, 2023 • edited Loading

Conaclos commented Sep 15, 2023

nhedger commented Sep 15, 2023

wcastand commented Sep 15, 2023 • edited Loading

nhedger commented Sep 15, 2023

Vivalldi commented Sep 15, 2023 • edited Loading

quantizor commented Sep 15, 2023 • edited Loading

harrytran998 commented Sep 17, 2023

nhedger commented Oct 6, 2023

ematipico commented Nov 26, 2023

wcastand commented Sep 15, 2023 •

edited

Loading

wcastand commented Sep 15, 2023 •

edited

Loading

Vivalldi commented Sep 15, 2023 •

edited

Loading

wcastand commented Sep 15, 2023 •

edited

Loading

Vivalldi commented Sep 15, 2023 •

edited

Loading

quantizor commented Sep 15, 2023 •

edited

Loading