-
-
Notifications
You must be signed in to change notification settings - Fork 282
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
Bug
Unable to compile - fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
#2426
Comments
Bug
Unable to compile Bug
Unable to compile - fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Have you tried cleaning the build files? |
Yes it appears to give the same error Clean ns-panel.yaml external_components: [source /data/packages/566b10a3/esphome/nspanel_esphome_core.yaml:40]
|
same here with ESPHome 2024.12.x had to downgrade ESPHome to 2024.11.3 Looks like the config syntax has to be changed, please check and update the config example here, thanks! |
The tag |
Same error for me ESP Home has had update since the last time i tried to complile as well to 2024.12.1 Clean ns-panel.yaml external_components: [source /data/packages/566b10a3/esphome/nspanel_esphome_core.yaml:40]
|
Could you please try forcing an earlier version of this project? |
Same error when trying clean build for me with ref: v4.3.11 |
May I ask for another test? |
Ok my apologies, it does compile successfully with ref: v4.3.11 I did try using ref: v4.3.12 and it still has error on that one. Lee |
Ok, good to know you can use the system with v4.3.11. But I still have no idea why v4.3.12 is failing. 😬 |
Thank you for your support, I will install to the ns-panel 👍 |
Hi, I'm having exactly the same issue - trying to use 4.3.11 isn't helping in my case either. Any guidance would be greatly appreciated! The error I'm getting is exactly the same. Let me know if there are any logs which would be helpful to attach. |
Could you please share your yaml and the logs for when you are trying |
YAML:
Logs:
If I swap the ref out for any other version it throws the same error. I'm starting to suspect it's somethign weird going on with ESPHome, rather than with the NSPanel project specifically, at this point, as it seems like it just really does not want to do the git operation properly. I've tried clearing the build files, with no luck, and I've tried swapping the device running HA out for an 8GB pi rather than the original 4GB one just in case it was running out of memory during compilation. |
To further add to this: I'm able to successfully compile it if I do it from the ESPHome CLI running on my main PC, so it appears to be isolated to either the ESPHome HA addon, or my specific installation of it, rather than a general issue? |
I've just fully uninstalled ESPHome and reinstalled it, and after some messing around to get it to start installing from scratch again, it seems to be behaving now - but only with 4.3.11. 4.3.12 was still refusing, although I think this was because something was still lingering from the previous install as it was happening far too fast for it to actually be trying to pull the git repo. Unfortunately I don't know what about the fresh install fixed it - I'm happy to help in any way I can if you still want to try to pin down exactly what was causing it though. |
Jak jsi to prosím vyresil ja odinstaloval doplnek ESPhome a vysledek stejny : INFO ESPHome 2025.1.0-dev external_components: [source /data/packages/4c136fb8/esphome/nspanel_esphome_core.yaml:40]
|
uz to zacalo fungovat zniceho nic |
TFT Version
No response
Firmware Version
No response
Blueprint Version
No response
Panel Model
None
What is the bug?
Hi im unable to compile is this an external issue or local?
INFO ESPHome 2024.11.3
INFO Reading configuration /config/esphome/ns-panel.yaml...
Failed config
external_components: [source /data/packages/566b10a3/esphome/nspanel_esphome_core.yaml:40]
Steps to Reproduce
No response
Your Panel's YAML
No response
ESPHome Logs
No response
Home Assistant Logs
No response
The text was updated successfully, but these errors were encountered: