| 24 Nov 2024 |
 @hexa:lossy.network | except upstream doesn't pin to a version <2 while home-assistant does | 22:42:01 |
| @hexa:lossy.network | https://github.com/Leggin/dirigera/blob/main/pyproject.toml#L25 | 22:42:01 |
 @qbit:tapenet.org | dang | 22:35:10 |
| @hexa:lossy.network | qbit: https://github.com/NixOS/nixpkgs/pull/350542 | 23:30:48 |
| @hexa:lossy.network | the author claimed it built on x86_64-linux 🙂 | 23:32:15 |
| 25 Nov 2024 |
| @hexa:lossy.network | lol, my home-assistant behaved oddly, so I checked the journal and surely | 01:09:56 |
| @hexa:lossy.network | Nov 25 01:09:29 meduna hass[312719]: Traceback (most recent call last):
Nov 25 01:09:29 meduna hass[312719]: File "/nix/store/901c80rlps5q05bnjk1sj4zaz5k736nc-python3-3.12.7/lib/python3.12/asyncio/selector_events.py", line 178, in _accept_connection
Nov 25 01:09:29 meduna hass[312719]: File "/nix/store/901c80rlps5q05bnjk1sj4zaz5k736nc-python3-3.12.7/lib/python3.12/socket.py", line 295, in accept
Nov 25 01:09:29 meduna hass[312719]: OSError: [Errno 24] Too many open files
Nov 25 01:09:29 meduna hass[312719]: 2024-11-25 01:09:29.847 ERROR (MainThread) [homeassistant] Error doing job: socket.accept() out of system resource (None)
| 01:10:00 |
| @hexa:lossy.network | I ran out of file descriptsors | 01:10:07 |
| @hexa:lossy.network | * I ran out of file descript0ors | 01:10:09 |
| @hexa:lossy.network | * I ran out of file descriptors | 01:10:11 |
| @hexa:lossy.network | 1004 of which are sockets | 01:10:57 |
| @hexa:lossy.network | between a random source port (hass) and 127.0.0.1:10400 | 01:11:30 |
| @hexa:lossy.network | which is wyoming-openwakeword | 01:11:44 |
| @hexa:lossy.network | which has similarly run out of fds 😄 | 01:11:53 |
| @hexa:lossy.network | all sockets were in established state | 01:13:41 |
 uep | If i've told you once, i've told you a thousand (and four) times, waaake upppp! | 01:14:05 |
| @hexa:lossy.network | ah, and now my co2 value has jumped from 800 to 1400 ppm 🙂 | 01:14:18 |
 spacekitteh | does anyone here run an OpenThread Border Router? | 01:17:57 |
| spacekitteh | (on nixos) | 01:18:27 |
| @hexa:lossy.network | is that like python-matter-server? | 01:19:17 |
| spacekitteh | sorta | 01:19:32 |
| spacekitteh | if you wanna use python-matter-server, then OTBR is a dependency to get running AFAIK | 01:19:49 |
| spacekitteh | or rather, if you want to use matter-over-thread | 01:20:43 |
| spacekitteh | * (if you want to use matter-over-thread) | 01:20:50 |
| @hexa:lossy.network | and you want to run thread for something else? | 01:21:23 |
| spacekitteh | yeah i have a bunch of thread devices | 01:21:37 |
| @hexa:lossy.network | I don't think we have any other openthread border router | 01:21:41 |
| @hexa:lossy.network | * I don't think we have any other openthread border router packaged up | 01:21:48 |
| spacekitteh | matter-server isn't a thread border router, is it? | 01:22:00 |
| @hexa:lossy.network | https://github.com/home-assistant-libs/python-matter-server 🤷 | 01:22:11 |
