We keep seeing issues where async_dispatcher_send is called from
a thread which means we call the callback function on the other
side in the thread as well which usually leads to a crash or end up
trying to unsafely inject a task into the loop from the wrong thread.
Since this is happening in core integrations as well, it seems worth the
trade off to check these at run time for the next year.
Type of change
[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[x] Code quality improvements to existing code or addition of tests
Additional information
This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:
Checklist
[x] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
Proposed change
We keep seeing issues where
async_dispatcher_send
is called from a thread which means we call the callback function on the other side in the thread as well which usually leads to a crash or end up trying to unsafely inject a task into the loop from the wrong thread.Since this is happening in core integrations as well, it seems worth the trade off to check these at run time for the next year.
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: