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
vscode not working (again, see #443) #511
Comments
Logs with trace level
|
Curious case, could you for example use the SSH add-on, cd into the config folder and run stuff like...
|
yes. this only affects vscode |
As per the issue in #443, I've managed to get it working (so far) by removing the add-on, restarting ha a couple times and then re-installing the add-on. |
Please post the results? |
Perhaps misread your question. I'm running HA blue so not sure how to access specific docker instances or if that's even possible. when running the ssh addon there are no exposed docker commands |
Don't need to go into the container, /config is a shared folder. |
Without the Even if there was, doubt it would have anything to do with the issue as the add-on has been working without any issues for a while, suddenly breaks, reinstalling fixes it. All the while the file system has remained unchanged. |
FWIW: find does not have an -ls option |
I have the same problem as @dogmatic69 running 2022.10.5 on HA OS on RPi4: From VSCode log:
|
@tjorim Output from the suggested commands:
|
I'm having this issue too, for a few days now, VS Code struggles to open files and cannot write. Happy to provide logs, and to help debug the issue. [core-ssh config]$ ls -la
total 1984
drwxr-xr-x 17 1000 root 4096 Nov 4 10:24 .
drwxr-xr-x 1 root root 4096 Nov 4 10:33 ..
-rw-r--r-- 1 1000 root 9 Nov 4 09:47 .HA_VERSION
drwxr-xr-x 2 1000 root 4096 Feb 18 2022 .cloud
drwx------ 8 1000 root 4096 Feb 18 2022 .git
-rw-r--r-- 1 1000 root 63 Feb 18 2022 .gitignore
-rw-r--r-- 1 1000 root 1164 Apr 8 2022 .google.token
drwxr-xr-x 2 root root 4096 Aug 29 07:23 .shortumations
-rw-r--r-- 1 1000 root 1553 May 25 11:14 .sonoff.json
drwxr-xr-x 4 1000 root 12288 Nov 4 10:41 .storage
drwx------ 2 1000 root 4096 Feb 18 2022 .vscode
drwx------ 2 1000 root 4096 Feb 18 2022 automation
-rw-r--r-- 1 root root 43446 Nov 4 09:53 automations.yaml
-rw-r--r-- 1 1000 root 189 Oct 15 17:18 binary_sensors.yaml
drwxr-xr-x 4 1000 root 4096 Feb 18 2022 blueprints
-rw-r--r-- 1 1000 root 2864 Oct 29 19:32 configuration.yaml
drwx------ 10 1000 root 4096 Nov 2 12:37 custom_components
-rw-r--r-- 1 1000 root 1919 Jul 8 10:09 customize.yaml
drwxr-xr-x 2 1000 root 4096 Feb 18 2022 deps
drwxr-xr-x 3 root root 4096 Jul 25 16:25 esphome
-rw-r--r-- 1 1000 root 1953 Sep 7 19:29 google_calendars.yaml
-rw-r--r-- 1 1000 root 795 Oct 26 15:49 groups.yaml
-rw-r--r-- 1 root root 406543 Nov 4 10:43 home-assistant.log
-rw-r--r-- 1 root root 0 Nov 4 09:47 home-assistant.log.fault
-rw-r--r-- 1 1000 root 196608 Feb 18 2022 home-assistant_v2.db
drwx------ 5 1000 root 4096 Sep 22 10:56 image
-rw-r--r-- 1 1000 root 0 Feb 18 2022 known_devices.yaml
-rw-r--r-- 1 root root 426 Aug 11 11:40 mqtt.yaml
-rw-r--r-- 1 1000 root 316 Feb 18 2022 notify.yaml
drwxr-xr-x 2 root root 4096 Nov 2 11:32 python_scripts
-rw-r--r-- 1 root root 22728 Oct 9 18:39 scenes.yaml
-rw-r--r-- 1 root root 8920 Oct 17 16:28 scripts.yaml
-rw-r--r-- 1 1000 root 174 Feb 18 2022 secrets.yaml
-rw-r--r-- 1 1000 root 4043 Nov 4 10:19 sensors.yaml
-rw-r--r-- 1 root root 11446 Oct 27 13:52 templates.yaml
drwx------ 4 1000 root 4096 Nov 4 10:17 themes
drwxr-xr-x 2 1000 root 12288 Jul 24 14:28 tts
-rw-r--r-- 1 1000 root 12288 Feb 18 2022 webostv.conf
drwx------ 3 1000 root 4096 Feb 18 2022 www
-rw-r--r-- 1 1000 root 684032 Nov 4 09:46 zigbee.db
-rw-r--r-- 1 1000 root 32768 Nov 4 10:43 zigbee.db-shm
-rw-r--r-- 1 1000 root 461472 Nov 4 10:43 zigbee.db-wal
[core-ssh config]$ find . -maxdepth 1 -type l
[core-ssh config]$
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
Uninstalling, removing all files and then reinstalling fixed this for me. But that doesn't seem like a good fix! |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
FWIW: Uninstalling and reinstalling the addon solved my issues too. |
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
Problem/Motivation
This is follow on from #443. However I don't recall doing any updates before this happend. Almost as if it just suddenly stopped working. Given it's identical symptoms to last time I'm going to say it's not related to any updates and probably something triggers it and the "error" get's cached some how which keeps it "broken".
vscode loads and then immediately stops working. not possible to open any files or modify any content
This is almost certainly something within the instance, cached or something, as it immediately done the same thing on all machines I've got available for testing. eg: both windows / linux, completely different browser sessions etc.
The page is also now very slow to load, often it will "crash" completely with browser errors saying the page crashed.
The rest of HA is working perfectly fine.
As a side note, if I am quick enough just after the page loads I can change to open a new folder, eg
/
and then everything works fine again. This can be any folder besides/config
, eg/config/<something>
will work just fine. As soon as I open/config
again everything stops working.Expected behavior
it should be possible to open and modify files
Actual behavior
In the console, there are constant reconnections.
console: (these errors repeat multiple times per second)
add-on logs:
Steps to reproduce
Not really sure how to reproduce this, but before it started and things were working kinda well it started to be glitchy almost like high memmory usage. Eventually it stalled and now does not work.
Proposed changes
No idea :/
The text was updated successfully, but these errors were encountered: