-
Notifications
You must be signed in to change notification settings - Fork 4
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
No actual build is done #35
Comments
Does it work with Is your vshaxe version up-to-date (1.11.0)? Also check the Haxe output channel for potential errors: https://github.com/vshaxe/vshaxe/wiki/Troubleshooting#completion-doesnt-work-at-all |
It works with setting the configuration flag to false. My vs-haxe is up to date The server doesn't seem to react to the build step if I launch the build task with the flag to true. |
Can you check the Haxe output channel? You should see some output like this:
The port should match what's added by
And finally, when the build finished:
|
Btw, what Haxe version are you running? |
I'm running 3.4.7. The server doesn't even react when the task launches even though it listens on port 6000 |
What does the output channel's output look like if you enable verbose mode? "haxe.displayServer": {
"arguments": ["-v"]
} This is pretty strange.. I wonder if you're having some Windows Firewall issue where ports are blocked or something... Perhaps try turning that off temporarily to see if it helps? |
It seems to get the build command but skips everything for some reason (I turned back the enable compilation flag). Edit: here I edited a variable PlayState so I could see the difference. |
That's not the build command, that's a request to get diagnostics information from the Haxe server. You can tell by this at the end of the arguments list:
But yeah, even without verbose mode you should see I wonder, does the following work for you?
|
Hm, so that's working then... Just a wild guess, but this is interesting: https://stackoverflow.com/a/21230911/2631715 - vshaxe doesn't explicitly specify localhost, so that might be the issue.
While for the
Could you give the following a shot?
|
Sorry, I can't try this on the computer where the issue is located now. If I don't forget, I'll give you feed back next Monday. Thanks for your support and have a nice weekend! |
This might fix some firewall issues, see openfl/lime-vscode-extension#35.
Thanks! For now I've committed that change, it seems more correct either way: vshaxe/haxe-language-server@085e571 |
Any luck with the manually applied patch? |
Hello. Yeah, it works with the applied patch. I also suspect a conflict with this computer's firewall policies or another program that already uses the port. Thanks for the patch and the support! |
Nice, thanks for confirming! :) We might want to release the next version a bit sooner then to avoid others running into this. |
The fix for this was released with vshaxe 1.12.0. Your output looks good actually. |
But it does not raise the server, when I run |
I'm not sure what the problem could be right now, but it must be different from what was originally reported in this issue. As mentioned earlier here, you can just turn off the compilation server if you need a workaround. |
Hello. I'm currently using this extension (using the version on the extension stroe. Everything works minus one specific step in the process: no build is actually done in both tasks.
The
lime test neko -debug --connect 6000
doesn't build at all. If there is an error in the code, it won't even be notified. I don't know what it is trying to connect to but what it only does is launching the last built version (or crash due to lacking .objs file -precisely ApplicationMain.n- on a clean project folder)I have to manually do
lime test neko
(with or without-debug
) in the console (lime is in PATH, so no issues here).I mostly noted the issue on Windows but I'll give a try on linux again later. The
project.xml
file is the same as HXFlixel's, with flixel-addons haxelib option uncommented. I wonder if it's a misconfiguration from my part or just an issue within the extension.Have a nice day.
The text was updated successfully, but these errors were encountered: