Closed angeltonio closed 4 years ago
I have the same issue. Currently running on WSL1. Started happening after upgrading VSCode...
EDIT: Just rolled back to version 1.6.5 and it works. I guess this has something to do with the latest version 1.7.x
I have the same issue. Currently running on WSL1. Started happening after upgrading VSCode...
EDIT: Just rolled back to version 1.6.5 and it works. I guess this has something to do with the latest version 1.7.x
Same here too. vsocde on windows to a docker ha instance.
Confirmed and reproducible on my end as well.
Fixed in #411
This is also happening to me, running as [x] Hassio Add-on [x] Visual Studio Online
Version is 1.12.0 VSCode version is 2.9.0
@whizkid79 That cannot be the exact same issue, as the code that caused this issue isn't fixed but replaced entirely.
Could you raise a new issue and provide as many details as possible? Preferably, with a re-production scenario.
Thanks 👍
EDIT: For some reason, uninstalling and reinstalling the extension resolved my issue.
Started seeing this recently; trimmed my configuration.yaml down to the min, and still getting it. Anyone else?
v1.21.0
Version: 1.60.2 (user setup) Commit: 7f6ab5485bbc008386c4386d08766667e155244e Date: 2021-09-22T12:00:31.514Z Electron: 13.1.8 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.19043
version | core-2021.9.7 |
---|---|
installation_type | Home Assistant Container |
dev | false |
hassio | false |
docker | true |
user | root |
virtualenv | false |
python_version | 3.9.7 |
os_name | Linux |
os_version | 5.10.28-Unraid |
arch | x86_64 |
timezone | America/Los_Angeles |
Extension runs in:
I'm running VS Code on:
I'm accessing my files:
But the connection is established correctly, I can reload the scripts normally.