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

Remote connections don't work when opening the "root" of a (network?) drive #62

Closed
sjsf opened this issue Nov 24, 2017 · 1 comment
Closed
Labels

Comments

@sjsf
Copy link

sjsf commented Nov 24, 2017

I think I at least could track down the problem on my side a little of what I first thought was related to #57:

Whenever I open the "root" of the samba share directly as a folder (no matter whether it's as file://10.20.0.15/smarthome or mapped to a network drive like file://o:, then it simply does nothing. As soon as I open a subfolder as the "workspace" in VSCode (i.e. 'file://10.20.0.15/smarthome/conf' or 'file://o:/conf'), then everything works nicely - rest calls go out, items/things are displayed and it starts the LSP connection.

(Windows 10, VSCode 1.18.1, openHAB extension linked from the comment in #57).

@kubawolanin
Copy link
Collaborator

@SJKA
Hey Simon!
Thanks for reporting the defect with so many details! This led me to a solution really quick.
I was expecting the workspace root to be indeed a 'conf' folder by checking items and rules folders existence immediatelly after the root! 🙈

The fix is on the way!
Thanks again.

kubawolanin added a commit to kubawolanin/openhab-vscode that referenced this issue Nov 25, 2017
Closes openhab#62

Also added new release notes

Signed-off-by: Kuba Wolanin <hi@kubawolanin.com>
kubawolanin added a commit that referenced this issue Nov 25, 2017
Closes #62

Also added new release notes

Signed-off-by: Kuba Wolanin <hi@kubawolanin.com>
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

2 participants