-
-
Notifications
You must be signed in to change notification settings - Fork 32k
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
Unable to use custom component after upgrade to 2024.12.0 #132398
Comments
searching through the archive of HA Core bugs I've found that similar issue was mentioned couple of times in the past. But both times it didn't come to resolution. |
@cdce8p Do you have ideas? |
Unless I am wrong, it does not look like related to restrictions in the package_contrains (like possibly one of previous mentionings of similar issue). |
Could it be something like apparmor or something issue? |
OK, further info. I think it all boils down to this.
But after that I am lost. EPERM happens when either PROT_EXEC and file belongs to no-exec FS (not our case) or when file is sealed (not our case also). Huge pages case of EPERM even less applicable. |
Aha! Maybe it
EDIT: |
Although, there is another issue with QUESTDB pops up after that :) |
Aha, on older core, very possible, it was using prebuilt wheel. questdb-2.0.0-cp312-cp312-musllinux_1_1_x86_64.whl |
So, results:
|
@antst I was able to build |
I also was able to build 2.0.3. But only after remounting /tmp without noexec. QSS component currently depends on 1.2 (it was available as prebuilt wheels), but I already made PR which makes it compatible with 2.0.3 |
It could be added to https://github.com/home-assistant/wheels-custom-integrations to build the musl wheels for it automatically. Just saw there is an open PR for it already: home-assistant/wheels-custom-integrations#705 It just needs approval. |
I see the discussion here, however, this discussion is about a custom integration, which is not supported by the Home Assistant project. I'm going to close this issue for that reason, as it is not actionable on our end. ../Frenck |
Actually, I still lack clarity on one question. If later is valid, then there is still general issue unrelated to particular component. (mount options of /tmp) |
The problem
Custom component which depends on
['questdb>=1.2,<2.0']
can not be used, because installation of questdb package fails with strange error. Here I provide log from manual attempt to install it, automatic installation during startup of core hits the same issue. With manual I just can produce more verbose log.I confirmed that library is present when attempt to load happens, and this file has next permissions
I am really out of ideas why this happens. Google search didn't help either. With 2024.11.x it has zero issues.
What version of Home Assistant Core has the issue?
core-2024.12.0
What was the last working version of Home Assistant Core?
2024.11.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: