All features except syntax highlighting do not work #73
Comments
|
@dylanbob |
|
Hi @dhuebner. I Can launch it directly from the terminal indeed, with not output: I can then see it in processes : also, I will see it as well after opening a YANG file in VSC: I don't see any output in the "Problems", "Output" or "Debug console" VSC views. I found these logs while searching with ctrlp+p: Hope it helps... |
|
@dylanbob
Does it work for you on Windows? Maybe it is a WSL problem? |
|
I cannot trigger anything :( apart from syntax highlighting, nothing seems to work. I cannot test simply on Windows either because technical corporate policies prevent java from running on my computer. I never had an issue regarding vscode extensions on WSL, but the problem might still be related to it I guess. |
|
@dylanbob |
|
Hi @dylanbob Dennis asked me to perform the tests. If you are able to use vscode under Windows you can also as @dhuebner suggested use it to connect to a WSL instance. But I also tested vscode running directly in Ubuntu and both scenarios work out of the box. # uname -a
Linux Defiant 5.15.90.1-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
# java --version
openjdk 11.0.18 2023-01-17
OpenJDK Runtime Environment (build 11.0.18+10-post-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build 11.0.18+10-post-Ubuntu-0ubuntu122.04, mixed mode, sharing) |
|
Thank both of you for your efforts. I just updated my kernel to get the same as you, and I am already using the exact same java version. I upgraded ubuntu to v22. vscode in running in WSL correctly. I also updated vs code to 1.77.0. But... still the exact same behaviour, and nothing new in logs :-(
|
|
@dylanbob |
|
Bingo! I managed to make it work with a simple file in a seperate folder, and opening only this folder. So this might be a memory problem like you said. I don't really know how Windows manages the WSL memory allocation... |
|
@dylanbob regarding WSL config options this is what you are looking for: |
|
Hi. There was a 8GB RAM limit configured by default for WSL, as documented and as I could see with the So I am not sure if that's actually a memory limit issue, or rather some bug making the extension or the language server unable to handle large directories ? Could you try with these ? Nokia SR-OS Yang models |
|
hi @dhuebner. I understand that you are sharing your software freely without support and therefore owe me nothing. Hovewer, just so you do not forget about my issue, I must ask you again if you would please test that your plugin functions correctly with the provided YANG files. Thanks |
|
@dylanbob |
|
@dylanbob Long story short, one need much more time to find a solution to speed up the Type resolution and also make the scoping faster. What I also missing is a user feedback that indicates the server is currently running, at least a Log would be helpful here. I will look into some low hanging fruits to speed up the workspace build. Also making it configurable, so one can disable the initial workspace indexing could help. |
|
@dhuebner I do not understand how the whole thing works exactly but let suggest something too: maybe one other way to speed up the process would be to only process modules and submodules in opened files? (+ linked files targeted by imports and includes) |
Hello and thank you for this vs code extension for the yang language server.
Having installed your extension on WSL Ubuntu (see details on versions below), I can see the syntax highlighting (NB: I have disabled all other YANG extensions and reloaded VS code), but I cannot see any other feature.
FYI I cannot use your extension directly on Windows because some corporate computer policy is blocking Java.
Do you have any idea what might be the cause?
Software versions:
The text was updated successfully, but these errors were encountered: