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
Logbook component broken after 72f336a (bisected) #29845
Comments
@springstan, mind rechecking your PR ? |
@clapbr sure I will take a look at it as soon as possible |
I can confirm that 72f336a caused this issue. However, only this line: |
It appears the loading of logbook is broken again. I was able to make a reproducible test case by doing a clean checkout of dev branch (84e1b3d), and then doing a clean venv (Python 3.7) install. I deleted everything from my config directory, then created configuration.yaml with just these lines:
Then running a config check I get:
After digging a bit I discovered that PIL is from the package named Pillow. That package is not getting installed. However if I run:
then it will now be installed & the config check succeeds. It also succeeds if I start again and just have |
@pnbruckner however installing |
We should move the imports for |
Home Assistant release with the issue: 0.104.0.dev0 (git)
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Integration:
Description of problem:
Logbook doesn't load on current dev branch.
Since logs doesn't say much I bisected the culprit: 72f336a
Since the changes are rather small and look completely unrelated I tested reverting only the commit locally in a clean venv+clean config and logbook loaded normally with no other errors.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: