-
Notifications
You must be signed in to change notification settings - Fork 61
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
Erroneous "Opening file that is not part of the project" message #115
Comments
It is probably something with the search paths on windows and different drives. You can build vhdl ls locally and debug it to see if you can solve the problem. The code that loads the configuration file and creates the search paths is here: https://github.com/VHDL-LS/rust_hdl/blob/master/vhdl_lang/src/config.rs |
Closed due to lack of activity |
I'm encountering this exact issue as well, and it appears someone on the vscode extension issues tracker is as well. I don't have rust experience, but have a little bit with C, so I tried to take a look at this, but there seems to be no build/debug instructions. I could figure out how to build, but not how to debug it. |
@Matt-D-Smith you can use |
Some initial finding, within LibraryConfig() there is a fn as_abspath(). The file_path input to that is of format like ordinary windows file path for a network drive \\sshfs.r\user@domain\mnt\drive\projects\test\test1.vhd the code runs as_abspath(&file_path), and puts abs_path in result \\?\UNC\sshfs.r\user@domain\mnt\drive\projects\test\test1.vhd Seems to be an inconsistency somewhere in using this format file path and the original format file path, which is causing I have seen this issue cause VHDL_LS to think there is a duplicate entity of same name when only one entity of that name exists in the project. |
@Matt-D-Smith could you try the https://github.com/VHDL-LS/rust_hdl/tree/file_path branch? I made a quick hack there to test a hypothesis on how this problem can be fixed. |
Building that branch, I no longer see the "Opening file that is not part of the project" warning with either the workspace file path being the network file path format \\server\share\folder or the network mapped drive format Z:\folder. Seems like that worked! |
I'm using VHDL LS from inside vscode running on Windows. When I open a project that is located on my local disk drive (C:), everything works fine. However, if I take the same project and move it to a NAS drive on our network, LS no longer recognizes the VHDL files as belonging to a project.
Maybe network latency is causing something weird to happen?
While investigating, I found a similar bug report for a different extension with a detailed explanation, may or may not be related. https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/290#note_475873929
I'll attach the project I am testing with. It also contains the logs that are produced in vscode with verbose trace running (one for project being locally stored and one for when it is on a NAS drive).
vhdl_ls_mre.zip
The text was updated successfully, but these errors were encountered: