-
Notifications
You must be signed in to change notification settings - Fork 3
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
RefactorEx couldn't create connection to the server #9
Comments
I am running in a directory with a mix.exs file. elixir 1.17.3-otp-27 ~/.config/mise/config.toml 1.17.3-otp-27 |
Hey man, I've tried my best but couldn't reproduce the issue with the exact setup as yours. A few other people are having startup related problems on Elixir 1.17 as well but I still don't know how to solve it. I'll keep working on possible solutions |
here is what I got right after installing it:
Versions:
|
I had this error after installing the extension (in Cursor), but the issue went away after I restarted the editor.
I'm using ASDF. |
[Info - 12:29:29 AM] Client is waiting server
[Info - 12:29:29 AM]
[Error - 12:29:30 AM] Server not started: Error: Command failed: export MIX_ENV=prod && cd /Users/donaldwilson/.vscode/extensions/gp-pereira.refatorex-0.1.24/refactorex && elixir --sname undefined -S mix run --no-halt -e "Application.ensure_all_started(:refactorex)" -- --port 64221
could not compile dependency :jason, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile jason --force", update it with "mix deps.update jason" or clean it with "mix deps.clean jason"
** (Mix) Could not find a Mix.Project, please ensure you are running Mix in a directory with a mix.exs file
[Info - 12:29:30 AM] Server started on port 64221
[Error - 12:30:01 AM] Refactorex client: couldn't create connection to server.
Error: Client could not connect to the server.
at Socket. (/Users/donaldwilson/.vscode/extensions/gp-pereira.refatorex-0.1.24/src/extension.ts:132:13)
at Socket.emit (node:events:519:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
The text was updated successfully, but these errors were encountered: