| 5 Feb 2025 |
 @hexa:lossy.network | some of them run into this backtrace | 21:43:32 |
| @hexa:lossy.network | homeassistant-test-hassio> File "/build/source/homeassistant/components/hassio/coordinator.py", line 530, in _update_addon_info
homeassistant-test-hassio> info_dict = info.to_dict()
homeassistant-test-hassio> File "/nix/store/4nj4l3scr96gcx4jirb3kfv24c4ay1z7-python3-3.13.1/lib/python3.13/unittest/mock.py", line 1167, in __call__
homeassistant-test-hassio> return self._mock_call(*args, **kwargs)
homeassistant-test-hassio> File "/nix/store/4nj4l3scr96gcx4jirb3kfv24c4ay1z7-python3-3.13.1/lib/python3.13/unittest/mock.py", line 1171, in _mock_call
homeassistant-test-hassio> return self._execute_mock_call(*args, **kwargs)
homeassistant-test-hassio> RuntimeWarning: Enable tracemalloc to get the object allocation traceback
| 21:43:35 |
 dotlambda | In reply to @hexa:lossy.network
some of them run into this backtrace E.g. which component? | 23:48:31 |
| @hexa:lossy.network | e.g. hassio 😛 | 23:48:43 |
| @hexa:lossy.network | or nmbs | 23:49:17 |
| 6 Feb 2025 |
| dotlambda | In reply to @hexa:lossy.network
e.g. hassio 😛 fixture 'setup_integration' not found makes sense cause there is no such fixture in the hassio tests. It must be getting it from a different component but we run them in isolation | 00:06:24 |
| @hexa:lossy.network | huh, ok | 00:06:42 |
| dotlambda | It should have been setup_backup_integration instead | 00:19:03 |
| dotlambda | Anything else? | 00:19:08 |
| @hexa:lossy.network | posting a nixpkgs-review any minute now | 00:19:36 |
| @hexa:lossy.network | qtwebengine was taking its sweet time | 00:19:45 |
| @hexa:lossy.network | everything has been built and yet I'm still waiting for it to complete | 00:41:21 |
| dotlambda | I'm scared: https://github.com/home-assistant/core/pull/137495 ;-) | 00:43:45 |
| @hexa:lossy.network | it is there 😄 | 00:45:28 |
| @hexa:lossy.network | i wish you all the best | 00:46:06 |
| dotlambda | That llama stuff is so annoying. It always pollutes nixpkgs-review reports. | 00:50:48 |
| @hexa:lossy.network | pinning async-timeout to 4.0.3 | 00:51:15 |
| @hexa:lossy.network |
TypeError: 'Timeout' object does not support the context manager protocol
| 00:51:32 |
| @hexa:lossy.network | if you're seeing this error | 00:51:35 |
| @hexa:lossy.network | -with async_timeout.timeout(self.request_timeout):
+async with async_timeout.timeout(self.request_timeout):
| 00:51:52 |
| @hexa:lossy.network | one second thought … that rebuilds the world | 00:55:38 |
| @hexa:lossy.network | might want to revert on staging-next instead | 00:55:53 |
| @hexa:lossy.network | well, let's give it a shot | 00:56:55 |
| dotlambda | aiomqtt has paho-mqtt_2 in its dependencies. I wonder why the duplicate in the closure isn't detected | 01:16:37 |
| dotlambda | Can we move to paho-mqtt v2 globally put pin v1 for HA? | 01:17:15 |
| dotlambda | Otterwise we should revert the aiomqtt bump | 01:17:44 |
| dotlambda | * Otterwise we should revert the aiomqtt bump or mark the package broken conditionally | 01:18:07 |
| dotlambda | But putting a versioned attribute in the dependencies of a Python module is a bad idea | 01:18:28 |
| @hexa:lossy.network | that was probably me though | 01:20:25 |
| @hexa:lossy.network | and I do know better | 01:20:32 |
