Skip to content
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

The refact-lsp sometimes dies 💀 #136

Open
Equanox opened this issue Sep 25, 2024 · 2 comments
Open

The refact-lsp sometimes dies 💀 #136

Equanox opened this issue Sep 25, 2024 · 2 comments

Comments

@Equanox
Copy link

Equanox commented Sep 25, 2024

I'm on ubuntu using vscode. Since today refact.ai stopped working as it does not use my custom configured endpoint (settings/Adress URL). It uses 127.0.0.1:9095 instead.

The picture below shows the refact.ai plugin release date + the error message.

The version of the plugin is v5.0.100
VSCode version is 1.93.1

image

@olegklimov
Copy link
Contributor

Probably 105 from yesterday, not 100, that's a pre-release for experimentation. Thanks for testing!!! If you want trouble-free experience, use the stable version. What you are seeing is probably dead refact-lsp process (that's what it is connecting to via 127.0.0.1:9095). Good commands to investigate more:

ps aux | grep refact.lsp

tail -n 1000 -f ~/.cache/refact/logs/rustbinary.2024-09-26

(current date)

@olegklimov olegklimov changed the title vs-code plugin uses wrong adress The refact-lsp sometimes dies 💀 Sep 30, 2024
@Equanox
Copy link
Author

Equanox commented Oct 9, 2024

Thx for the response. I'm using a stable version.

It seems like the error message is confusing. When i checked the logs it was clear that the server was not reachable on the configured address.

2024-10-09T07:11:02.678127Z  INFO refact_lsp::caps:318: fetching caps from http://XXXXXXX:5000/refact-caps
2024-10-09T07:11:08.932042Z ERROR refact_lsp::global_context:187: caps fetch failed: "error sending request for url (http://XXXXXXX:5000/refact-caps): connection error: Connection reset by peer (os error 104)"

It seems the popup shows an invalid ip address but under the hood the correct one is used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants