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
Fix stalls in config flow of APCUPSD #108931
Fix stalls in config flow of APCUPSD #108931
Conversation
@@ -52,9 +52,8 @@ async def async_step_user( | |||
|
|||
# Test the connection to the host and get the current status for serial number. | |||
coordinator = APCUPSdCoordinator(self.hass, host, port) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually we don't create coordinators in config flows.
In a future PR it would be nice to replace this with await aioapcaccess.request_status(host, port)
and trap the exceptions instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, will do!
await coordinator.async_request_refresh() | ||
await self.hass.async_block_till_done() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will wait for everything, not just the integration so it will likely never finish once startup has completed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, that makes sense now! Thanks for the explanations!
Updated the PR description!
Proposed change
This PR fixes the stalls in config flow of APCUPSD integration, where we were mistakenly calling
hass.async_block_till_done()
after requesting initial coordinator refresh.hass.async_block_till_done()
waits for everything in HASS, not just the the integration itself (and it is usually only used in test code). Therefore, this call will probably never return once HASS startup finishes. We were unable to reproduce this since we were testing on new installations, but users with existing installations have reported such an issue when they were adding an apcupsd integration (see #108221).Credit goes to @dom42 who was able to reproduce this locally and found the culprit.
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: