-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Client cannot connect to server #192
Comments
That would be almost impossible to triage, I think. It seems you have a process that stops socket connections in your laptop
|
I switched to dprint for formatting as it has a working (on my work machine) VS Code extension, plus it has plugins for CSS and potentially more than Biome offers. I am still using Biome for linting as I really like the lints, and it promotes a much more modern style out of the box vs prettier, where it's probably possible to opt-in to the same kinds of rules, but you have to know about them, while Biome has great rules enabled by default. So we're running Biome via CLI only at this point, which is a shame, but it's still providing a lot of value. It may not be a priority for you @ematipico but there could be a lot of potential "enterprise users" like me that have restricted work machines that will try Biome and give up quickly due to things like the above. Other Rust tools like dprint and oxlint do have working plugins on my machine so I guess they aren't using socket files. |
Don't worry @maurice, I'm NOT dismissing your use case. I was commenting on something about the logs. It's my first time seeing one, and I tried to venture a guess. |
While I am on my work machine, unlike original poster, I am not behind corporate firewall or anything like that. There is no usage restrictions on my system. Also, while the extension is not able to detect the biome on node_modules, on windows, On my personal linux machine, it has no issues detecting it. |
I'm using a personal desktop with Windows 11 (in wsl) also experience this. Seems like biome server will crash when the code is invalid TypeScript. And it fail to start when the invalid TypeScript is still there. After I fix the TypeScript syntax error (and save the files), then I can start the biome server again. |
@Abhinav1217, @unional I don't think your issues are the same as discussed here. If you're still experiencing the issue, please open a new issue with a minimal reproduction repo. |
I still experience the crash on a daily basis. But it's hard to create a repo as this occurs on a large private repo I work on. I'm gradually migrating my OSS projects to biome but didn't get much time lately. |
I will close this issue because the upcoming v3 takes a different approach that doesn't use sockets. Feel free to try the latest nightly version to confirm that it solves this issue. |
@nhedger Can you please advice us what should we do for now? |
VS Code version
1.88.0
Extension version
2.2.2
Biome version
1.6.4
Operating system
Description
Unfortunately I can't provide the actual log or screenshot because this is happening on my work machine, and copy + pasting anything to the public internet is forbidden.
So here I'm manually re-typing what I see in the "Biome" process OUTPUT tab:
The restart, failure cycle continues a bit then sometimes it seems to give up after 5 attempts.
Steps to reproduce
This is probably not going to be universally reproducible; I expect it's some corporate firewall/spyware on my work machine that is causing the issue.
However I've not done anything unusual (AFAIK), simply adding biome to my project's NPM dependencies, creating the config file, then installing extension.
Expected behavior
Extension should not error and provide linting errors as I type and format/fix on save
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Logs
The text was updated successfully, but these errors were encountered: