-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
Detected blocking call to dsmr_parser #118919
Comments
I have the same issue. |
2024.5.5 isn't capable of detecting this problem so it's still there but blissfully unaware |
This is fixed upstream ndokter/dsmr_parser#157 Needs a library bump |
Hey there @RobBie1221, @frenck, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) dsmr documentation |
I think this is fixed upstream but the lib needs to be bumped |
Looks like there some tests that will need to be adjusted
Sadly I don't have the ability to test this one so it will need to wait for someone who can do the changes |
Still receiving this error with latest core update (yesterday). Detected blocking call to open with args ('/config/.ps4-games.0CFE45D4C804_639d.json',) inside the event loop by integration 'ps4' at homeassistant/components/ps4/init.py, line 176: games = load_json_object(g_file) (offender: /usr/src/homeassistant/homeassistant/util/json.py, line 74: with open(filename, mode="rb") as fdesc:), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+ps4%22 For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#open Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 727, in _async_add_entity await entity.async_device_update(warning=False) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1300, in async_device_update await self.async_update() File "/usr/src/homeassistant/homeassistant/components/ps4/media_player.py", line 160, in async_update self._parse_status() File "/usr/src/homeassistant/homeassistant/components/ps4/media_player.py", line 166, in _parse_status self._games = load_games(self.hass, cast(str, self.unique_id)) File "/usr/src/homeassistant/homeassistant/components/ps4/init.py", line 176, in load_games games = load_json_object(g_file) Bob. |
@OhioSpyderman please open a new issue. Your issue is on the ps4 integration. |
The problem
After updating to HA 2024.6.0, I get 597 times the warning:
Detected blocking call to open with args ('/usr/local/lib/python3.12/site-packages/pytz/zoneinfo/Universal', 'rb') in /usr/local/lib/python3.12/site-packages/pytz/init.py, line 108: return open(filename, 'rb') inside the event loop Traceback
What version of Home Assistant Core has the issue?
core-2024.6.0
What was the last working version of Home Assistant Core?
core-2024.5.5
What type of installation are you running?
Home Assistant OS
Integration causing the issue
May be dsmr_parser ????
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?
Additional information
No response
The text was updated successfully, but these errors were encountered: