-
Notifications
You must be signed in to change notification settings - Fork 779
[LSP] Connection to LSP fails with internal error if smb network path is used #6611
Comments
When using
Versus when using
@SJKA Do you have any ideas? I'm not sure if I introduced this with my fix. Full TRACE log... Using drive letter (works).
Using SMB network path (doesn't work).
|
So in the IDE, at this point in the code I can see this when a drive letter is used (i.e. c:\Users\mark_000...)
And this when a UNC path is used (i.e. \\localhost\Users\mark_000...)
Not sure where to go with this next... |
If I understand the implementation correctly the code gets the pathes from the client and tries to translate it the path that is local to the LSP. Therefore it tries to parse and understand the complete path. But this does not work in all situations: Maybe the solution of this is quite simple but I am not sure whether I am missing something: Example: The LSP client now passes the following UNC path to the LSP From this path only the filename, its extension and the directory where it is store are needed, so extract them from the path: Now concat the extracted file information with the configuration folder: |
I was confused why LSP had stopped working after a new windows install. I was just opening the openhab-config directly over the network with vscode i.e. open folder \openhabian\openhab2-config. And I got the |
My environment:
If I open an openHAB config file from a SMB share by using a SMB network path (e.g.
\\raspi\openhab\conf
) VSCode issues an "Internal error".The message returned from the LSP contains this error message and call stack:
The problem can be bypassed by assigning a drive letter to the path and open the config folder via the drive letter.
The text was updated successfully, but these errors were encountered: