| 12 Dec 2024 |
 spacekitteh | wait, where does it decompress the soruce code ~900 times? | 23:41:37 |
| spacekitteh | # extract translations from pypi sdist
prePatch = ''
tar --extract --gzip --file $sdist --strip-components 1 --wildcards "**/translations"
'';
is that what's being talked about?
| 23:42:25 |
 @hexa:lossy.network | Sourcing python-remove-tests-dir-hook
Sourcing python-catch-conflicts-hook.sh
Sourcing python-remove-bin-bytecode-hook.sh
Sourcing python-imports-check-hook.sh
Using pythonImportsCheckPhase
Sourcing python-namespaces-hook
Sourcing pytest-check-hook
Using pytestCheckPhase
Running phase: unpackPhase
unpacking source archive /nix/store/c6fqqhisfzjxb9zi6lrpby3pzs6hbndw-source <------------
source root is source
setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/tests/util/yaml/test_secrets.py
Running phase: patchPhase
| 23:42:40 |
| @hexa:lossy.network | that is like stdenv.mkDerivation logic | 23:42:57 |
| @hexa:lossy.network | I don't touch anything before patchPhase really | 23:43:16 |
| spacekitteh | right but i mean, which packages is causing it | 23:43:21 |
| @hexa:lossy.network | maybe it is trivial-builders? | 23:44:10 |
| @hexa:lossy.network | no it is not | 23:44:19 |
| spacekitteh | no no, i mean, what top level package | 23:44:22 |
| spacekitteh | is it the actual home-assistant package? | 23:44:31 |
| @hexa:lossy.network | e.g. home-assistant-component-tests.folder_watcher | 23:44:33 |
| spacekitteh | ah | 23:44:39 |
| @hexa:lossy.network | because they are effectively home-assistant.overridePythonAttrs {} | 23:45:01 |
| @hexa:lossy.network | to get the same environment as home-assistant but only run the tests | 23:45:15 |
| spacekitteh | i'm surprised fetchFromGithub doesn't automatically create a derivation tbh | 23:47:52 |
| @hexa:lossy.network | all sources are fixed output derivations | 23:51:50 |
| spacekitteh | sorry, i mean it doesn't create the derivation for the decompressed src, rather than the compressed src | 23:52:48 |
| 13 Dec 2024 |
| spacekitteh | hmmm. whenever i try to use the homeassistant mobile app to connect to HA behind an nginx reverse proxy, it seems to cause a hang in nginx with zstd compression | 03:37:16 |
| 14 Dec 2024 |
| spacekitteh | in my HA home settings, is there a way to read the lat/long of my home via a sops-nix file? | 03:26:16 |
| spacekitteh | oh of course there is, i'm still waking up x3 | 05:01:27 |
| 16 Dec 2024 |
 boolis | how do I enable the wakeword engine in home-assistant?
home-assistant.config.wake_word = {};
home-assistant.extraComponents = [ "wake_word" ];
| 13:33:16 |
| @hexa:lossy.network | uh, something wyoming? | 14:44:23 |
| @hexa:lossy.network | take a look at services.wyoming.openwakeword | 14:45:35 |
| @hexa:lossy.network | then enable the wyoming component in home-assistant | 14:45:43 |
| @hexa:lossy.network | and connect the two | 14:45:49 |
| boolis | oh right, apparently I have that enabled aswell.
I had this working a while back but now it just doesnt | 14:50:46 |
| @hexa:lossy.network | hm ok | 14:51:50 |
| @hexa:lossy.network | wakeword has regressed for me recently as well | 14:51:56 |
| @hexa:lossy.network | leaking lots of fds | 14:52:11 |
| @hexa:lossy.network | ls -1 /proc/$(systemctl show -P MainPID wyoming-openwakeword)/fd/ | wc -l
| 14:52:58 |
