| 12 Dec 2024 |
 dotlambda | In reply to @hexa:lossy.network
so where would you do that subtraction? Probably in the GitHub CI script | 15:39:50 |
 @hexa:lossy.network | which means we probably need to convince infinisil | 15:40:18 |
| dotlambda | In reply to @hexa:lossy.network
which means we probably need to convince infinisil which should be easier if it's tests rather than something HA specific | 15:41:03 |
| @hexa:lossy.network | certainly | 15:41:22 |
 @qbit:tapenet.org | can I run esphome on another machine and have my machine running home-assistant connect to it? (i assume so because host, port options..) | 17:39:40 |
| @qbit:tapenet.org | and follow up question, where does one set the "api" bit? | 17:40:00 |
| @qbit:tapenet.org | Can't connect to ESP. Please make sure your YAML file contains an 'api:' line. is the error I get when I try to add the remote esphome instance to my HA | 17:40:24 |
| @qbit:tapenet.org | oh. maybe it's because I don't have anything defined in esphome? | 19:06:02 |
| @hexa:lossy.network | yeah, that talks about your esphome config | 19:38:45 |
| @qbit:tapenet.org | i see - added something and it popped into HA, ty! | 20:35:09 |
 spacekitteh | In reply to @hexa:lossy.network
to be fair, they are rebuilds, and unpacking the home-assistant source 900 times has a certain cost to it why can't it cache those results? :S | 22:04:26 |
| @hexa:lossy.network | it depends on the src fod | 22:04:47 |
| @hexa:lossy.network | the src fod is compressed | 22:04:53 |
| @hexa:lossy.network | and one of the first parts of the derivation after fetching is unpacking | 22:05:04 |
| @hexa:lossy.network | not sure if there is a way to reuse the unpacked thing tbh | 22:05:15 |
| spacekitteh | create a derivation for the unpacked source | 22:05:42 |
| spacekitteh | that should be all that's necessary, no? | 22:05:51 |
| @hexa:lossy.network | hrm | 22:20:32 |
| spacekitteh | if you specified it as a nativeBuildInput then the source wouldn't be required at runtime either, iirc | 22:22:55 |
| spacekitteh | i feel like i'm missing something though, as to why that hasn't been done | 23:31:17 |
| @hexa:lossy.network | frankly, my work has been pretty nixpkgs focused | 23:32:46 |
| @hexa:lossy.network | and that simply hasn't been a standard pattern 😄 | 23:32:59 |
| spacekitteh | exactly, i'm wondering why not, as there surely is a reason | 23:33:30 |
| @hexa:lossy.network | can you create a poc? | 23:33:51 |
| @hexa:lossy.network | * can you create a poc so we can take a look at it? | 23:33:56 |
| spacekitteh | wouldn't it just be an extra derivation like, home-assistant-source = <whatever the stdenv helper is for just grabbing and unpacking a tarball is as a derivation> and then in the actual homeassistant derivation, src = pkgs.home-assistant-source;? | 23:35:49 |
| @hexa:lossy.network | maybe? 😄 | 23:36:34 |
| 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 |
