Couldn't start client wurstLanguageServer

[sethmachine]

Edit: Running VSCode as admin makes the error go away. This should be written in the instructions. However, same funny set of exceptions/warnings, these probably need to be addressed.

initializing workspace
initialization done!
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.eclipse.lsp4j.jsonrpc.json.adapters.CollectionTypeAdapterFactory (file:/C:/Users/sethmachine/.wurst/org.eclipse.lsp4j.jsonrpc-0.2.0.jar) to constructor java.util.Collections$EmptyList()
WARNING: Please consider reporting this to the maintainers of org.eclipse.lsp4j.jsonrpc.json.adapters.CollectionTypeAdapterFactory
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

I get this message in VSCode when I opened Hello.wurst in the tutorial. How do I fix it?

 

[Frotty]

If it's being fixed by running as admin, it's likely a permission problem. This can depend on project location, antivir programs, etc.
Running as admin isn't generally required.

 

[sethmachine]

Assuming anyone else ran on a clean Windows 10, they'd probably hit the same problem? Should at least be in documentation that running as admin may fix these issues.

 

[HappyTauren]

Nobody has reported this problem before, and I have used VSCode on a clean windows 10, as well as while changing a lot of privilege options, and I still didn't manage to break it like this.

Just from the log, it's obvious that this is very unlikely to be problem with Wurst language in any way, so you should post on VSCode's, or even windows 10's issues, since the issue really lies somewhere in those areas.

 

[sethmachine]

I've hit multiple problems on two different OS'es (macOS and Windows 10). I'm just saying the WurstSetup.jar and instructions are not perfect, otherwise I wouldn't have run into any issues. Anyone who didn't have a background in programming and ran into my problems would probably give up.

I wonder also if WurstSetup wasn't meant for Java 9, because I see a few warnings/exceptions in the stack traces. It should be stated clearly in the instructions what versions of Java are supported/tested.

 

[Frotty]

All HT said is, that these problems aren't under our control and that most people don't experience them.
It's up to the user to make sure they place their project files in locations that their OS permits programs to read/write to.
This depends completely on your machine and setup, so the most the app could do, is show an error instead of crashing.
But since we have no idea that this error even happens and why (since we don't get it), we also can't add that error dialog.
The "warnings" you posted don't contain any wurst information, just LSP. (we need wurstlog here)

So while this report is nice and we are thankful for it, it is also missing *extensive* information on why *you in particular* get this problem (just like your last thread, where you still didn't answer).

WurstScript • Setup Guide states that Java 8 is required, not 9, and this still stands. I have added a sentence about update level though.

 

[HappyTauren]

As DSG said in another thread, Program Files folder requires administrative privileges for the necessary freedom of read/write. Are you keeping any of this in program files?