🐛 v3 prerelease: Biome won't start

biomejs / biome-vscode

Biome extension for Visual Studio Code and VSCodium

https://marketplace.visualstudio.com/items?itemName=biomejs.biome

Apache License 2.0

207 stars 25 forks source link

🐛 v3 prerelease: Biome won't start #331

Closed ffMathy closed 3 weeks ago

ffMathy commented 3 weeks ago

VS Code version

1.92.2

Extension version

v2024.8.301002 (pre-release)

Biome version

0.3.3

Operating system

[ ] Windows
[X] macOS
[X] Linux

Description

Biome won't start.

Steps to reproduce

Not sure about steps to reproduce yet, but I am running inside a DevContainer. The DevContainer is running a linux image, and the host is on Mac M1.

Expected behavior

I expected Biome to start up and work.

Does this issue occur when using the CLI directly?

Not sure / Not applicable

Link to a minimal reproduction

No response

Logs

I do not see the "Biome Trace" category. I only see "Biome" there.

It shows this:

2024-09-06 08:11:57.971 [info] Biome extension activated
2024-09-06 08:11:58.918 [error] Failed to start Biome extension

Jagget commented 3 weeks ago

https://github.com/biomejs/biome-vscode/issues/329 ? Same thing.

ffMathy commented 3 weeks ago

How is it the same thing? I'm receiving different things in my output window, right?

Jagget commented 3 weeks ago

There's more than 1 Biome log.

ffMathy commented 3 weeks ago

It's weird. I only see one. Called Biome. Perhaps it even fails before it gets to create these categories?

nhedger commented 3 weeks ago

The extension spawns one session per project and one global session. The global session is named Biome LSP and the project sessions have the path of the project as a suffix

ffMathy commented 3 weeks ago

Not for me. Very weird. It seems it crashes before this?

nhedger commented 3 weeks ago

There was an issue where the extension attempted to create a global session before creating a project session. If that failed for some reason, the rest wouldn't work. I believe https://github.com/biomejs/biome-vscode/commit/899efe17d31f7dc9866d9bb8ace13b7d64d03318 fixes that. Would you mind trying the latest pre-release (v2024.9.91939)?

I'll close in the meantime, but feel free to circle back if it does not fix the issue.