Skip to content
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

LSP/Incorrect path (UNC) #112

Open
tmrobert8 opened this issue Oct 24, 2018 · 6 comments
Open

LSP/Incorrect path (UNC) #112

tmrobert8 opened this issue Oct 24, 2018 · 6 comments
Labels

Comments

@tmrobert8
Copy link

tmrobert8 commented Oct 24, 2018

I'm not sure if something changed in 2.4 (using snapshot) or in the .40 version (which I upgraded to at the same time as switching to the snapshot)..

I have openHAB 2.4 running on a machine called 'pitanuc' in the directory "C:\openhab2". I have visual code installed on a DIFFERENT machine and am accessing 'conf' directory on 'pitanuc' using an UNC path: '\\pitanuc\openhab2\conf'

Everything seem to be working well (REST, etc) EXCEPT for LSP. I know there are errors in one of my rules file. However, the error is never highlighted (like it use to be). If I look at the 'problems' tab, I can see the error is listed (The method or field xxxx is undefined). However - if I double click on the error, rather than taking me to the line - I get a message "Unable to open 'xxx.rules': file not found (file:///c:/openhab2/conf/rules/xxx.rules)"

So something along the way (LSP I'm assuming) is getting the local path on 'pitanuc' ("c:\openhab2\conf\rules\xxx.rules") and is using that path directly rather than looking for the same file on my editor path ("\\pitanuc\openhav2\conf\rules\xxx.rules").

I know I'm not really suppose to be using VScode on a different box - but it's very convenient to do it that way (I have a development box and a production box) and up until 2.4/.40 combo - it worked great.

Hoping you might have a solution for me...

Thanks,
Tim

@MHerbst
Copy link

MHerbst commented Dec 2, 2018

AFAIK there have been some changes regarding UNC pathes in the mean time. But with 2.4 M6 (and probably also M7) UNC pathes don't work on Windows (see eclipse-archived/smarthome#6611). You can try to assign a drive letter to your UNC path and it will probably work.

@cherub-i
Copy link

I have the same problem and I cannot resolve it by using drive letters:

Example from "Problems"-pane:
image

When trying to open the file via double-clicking the problem statement:
image

The file which should have been opened (after opening it from the folder tree):
image

@Beluk
Copy link

Beluk commented Dec 31, 2019

I have the same error Running OpenHAB 2.5 Release. Is there any workaround available?

@lsiepel
Copy link

lsiepel commented Jan 1, 2020

I think #184 is somehow related.

@Pabl0z
Copy link

Pabl0z commented Feb 11, 2020

Same error here, Running OpenHAB 2.5.1-2 Release on Pi, while Visual Studio Code 1.42.0 is running on Mac osx. Is there any solution available?
openhab

@Confectrician
Copy link
Collaborator

No sorry. I am happy for any input here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants