-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
not starting correctly with yamlint #15
Comments
it may be a memory problem, i asigning the VM 2GB, and when open this addon it goes to 90% , and next it hangs the machine . So reboot and uninstall is the only cure for now . |
@gnkarn Sorry I'm lost on what you are doing here. Please share the config you are trying to startup. Why are you trying to install yamllint? Since it is installed already! (pre-built, shipped with the add-on). |
I'm having the same problem. I did the following:
My config is:
It included "password", but every time I save and return to the screen it is gone. |
@michaelblight your report is not related at all. Password methods has changed in the last release. Please login using your username password from Home Assistant. The password option on the add-on has been removed. @gnkarn Are you getting back on my question? Or can this be closed? |
just installing as per the docs, config : { , as i say , this could be that VSC is taking too much memory from the Virtual Machine, and resources are not enough . You can close this , i will continue to use VSC , from the main computer for now , thanks a ton . |
That is just an example which as a big note right next to it: DO NOT USE. |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Problem/Motivation
i gave it a new try , starting first with no addon , it worked .
then installing with the addons , and i got the logs detailed below .
hope this helps .
thanks .
Expected behavior
Actual behavior
The text was updated successfully, but these errors were encountered: