VSCode 1.78, 1.79: Fatal error: exception Failure("Couldn't connect on 127.0.0.1:6000")

[djaonline]

VSCode 1.78, 1.79: Fatal error: exception Failure("Couldn't connect on 127.0.0.1:6000")

[RblSb]

Minimized project for reproducing this will be nice

[theJenix]

Not sure if it's related, but I'm having all sorts of issues with VSCode 1.78.2 and Haxe 4.2.5 that seem to center around communications between various processes.

With the extension host:

2023-05-23 13:05:09.657 [error] [nadako.vshaxe] provider FAILED
2023-05-23 13:05:09.671 [error] Error: Error: No completion point was found
	at handleResponse (/Users/jesse/.vscode/extensions/nadako.vshaxe-2.28.0/bin/index.js:1:173251)
	at processMessageQueue (/Users/jesse/.vscode/extensions/nadako.vshaxe-2.28.0/bin/index.js:1:169324)
	at Immediate.<anonymous> (/Users/jesse/.vscode/extensions/nadako.vshaxe-2.28.0/bin/index.js:1:169088)
	at process.processImmediate (node:internal/timers:466:21)

With the Haxe compilation server:

Haxe connected!
Listening on port 6000
Client connected
Client disconnected
Done.
Client connected
Client disconnected

When the client is disconnected, I cannot run any build tasks. I don't think I'm doing anything special except editing my file when this happens, and if I downgrade to VSCode 1.76, everything works like a charm.

[djaonline]

@RblSb Yes, please https://github.com/djaonline/haxe-hello-world

[RblSb]

Cannot repro on 4.0.5/4.2.5 and different vshaxe versions on latest vscode. This can be platform specific vscode problem, or something else is different in environment. We probably should make some verbose mode for debugging this.
I only can get this error in Kha, when i use watch mode. But it only happens on first compilation, and then recompiles normally.
Comes from this exception:
https://github.com/HaxeFoundation/haxe/blob/baee98f4be27d8c4b63620535e1d20284d831cab/src/compiler/server.ml#L542
Maybe there is different error types tho, so we can show more specific error messages.

[djaonline]

Vscode 1.78 updated to Electron 22. Possible the problem is here.

[djaonline]

@AlexHaxe vscode 1.79: same issue. How can I help to fix the issue or figure out what's wrong here?

[AlexHaxe]

well, key to fixing things is a reproducible sample. you've provided a sample, however it fails to reproduce on RblSb and my systems. since it's also a very basic sample that "should" just work, an issue like yours should affect everyone and there would be more reports of it. so chances are it is a problem with your local configuration / setup.

• try disabling extensions and see if it starts working.
• install an insider build of VSCode, they use separate configuration / extensions folders; install only vshaxe extension and try to run your project
• make sure there is no antivirus or firewall at play, interfering with Haxe / VSCode operations
  -try reproducing with a different user login or on a separate machine (if available), or try booting a from Linux Live DVD and see if it works

[djaonline]

By the way if I run haxe server manually haxe -v --wait 6000 it starts work correctly.

[kLabz]

Sounds like your vscode is using a wrong haxe executable, possibly because of a misconfiguration you haven't shared.

[djaonline]

@kLabz I use for that porpose your project https://github.com/kLabz/haxe-manager (very nice tool, thank you :) )
Here its path: /home/djaonline/tools/haxe-manager/
Env variables:

export MY_TOOLS=$HOME/tools
export HAXE_STD_PATH=$MY_TOOLS/haxe-manager/std
export HAXELIB_PATH=$MY_TOOLS/haxe-manager/haxelibs
export NEKOPATH=/usr/lib/neko
export LD_LIBRARY_PATH=/usr/lib/neko
export PATH=$PATH:$MY_TOOLS/haxe-manager/bin

[AlexHaxe]

can you confirm that localhost points to ::1 in your hosts file? and if you let it point to 127.0.0.1 will it fix your issue?

[djaonline]

@AlexHaxe The current host file record is ::1 localhost.localdomain localhost ip6-localhost. Changing it to ::1 localhost.localdomain 127.0.0.1 solves the issue.

[AlexHaxe]

closed by #605

[AlexHaxe]

vshaxe version 2.30.0 was just released. it should solve your issue.