| 4 Jun 2024 |
 raitobezarius | does your concern about the security still apply in this context? | 19:39:31 |
| raitobezarius | i'd assume that merged contents is assumed to be trusted | 19:39:40 |
| raitobezarius | hm | 19:39:50 |
| raitobezarius | but it's right we are still using it for arbitrary CLs | 19:39:57 |
| raitobezarius | so maybe there could be manipulation to push certain store paths even if the CI for arbitrary CLs wouldn't push to cache | 19:40:11 |
| raitobezarius | maybe in that case, what we can do is to have GHA infrastructure perform regular builds and push it to our cache? | 19:40:34 |
 Qyriad | In reply to@raitobezarius:matrix.org
i meant to build a specific branch regularly on the top of a set of channels what we mean is that building a specific branch regularly can perfectly reasonable be a different CI system than our CL CI system | 23:47:20 |
| Qyriad | * what we mean is that building a specific branch regularly can perfectly reasonably be a different CI system than our CL CI system | 23:47:27 |
| Qyriad | In reply to@raitobezarius:matrix.org
maybe in that case, what we can do is to have GHA infrastructure perform regular builds and push it to our cache? that would work | 23:47:35 |
| 5 Jun 2024 |
 delroth | In reply to @qyriad:katesiria.org
what we mean is that building a specific branch regularly can perfectly reasonably be a different CI system than our CL CI system hydra? </hides> | 00:07:54 |
| delroth | In reply to @qyriad:katesiria.org
what we mean is that building a specific branch regularly can perfectly reasonably be a different CI system than our CL CI system * hydra? /hides | 00:08:01 |
| delroth | (I'm only like 40% non-serious, hydra is kinda designed for this use case, it can monitor several git inputs for changes and knows how to push stuff to an S3 cache) | 00:08:56 |
| Qyriad | Yes honestly we think Hydra is, unfortunately, a reasonable choice here | 00:09:49 |
| Qyriad | Though I think we should maybe evaluate other options too | 00:10:03 |
| Qyriad | Oh dear, @⚠️ eldritch horrors operating in this area ⚠️ the reason that {{#include}} doesn't work in src/nix/nix.md is that, specifically for the nix --help manpage, and not for HTML nor for the manpage placed on disk, those markdown files never actually go through docbook?? | 00:27:13 |
| Qyriad | Oh dear, @⚠️ eldritch horrors operating in this area ⚠️ the reason that {{#include}} doesn't work in src/nix/nix.md is that, specifically for the nix --help manpage, and not for HTML nor for the manpage placed on disk, those markdown files never actually go through mdbook?? | 00:27:19 |
| Qyriad | nix --help re-runs its own manpage generation logic inline to display the manpage | 00:41:04 |
| Qyriad | at that point why not have an actual help message… | 00:41:10 |
 ⚠️ eldritch horrors operating in this area ⚠️ | In reply to @qyriad:katesiria.org
nix --help re-runs its own manpage generation logic inline to display the manpage yes this is evil ans must stop | 00:50:09 |
| ⚠️ eldritch horrors operating in this area ⚠️ | all MD should go through the same preprocessor, and nix binary ideally shouldn't contain an MD processor at all | 00:51:35 |
 jade_ | i would be tempted to use GHA for this since it is relatively likely to probably be trustworthy | 01:04:53 |
| jade_ | and is lower effort | 01:05:00 |
 Lunaphied | In reply to @pennae:matrix.eno.space
all MD should go through the same preprocessor, and nix binary ideally shouldn't contain an MD processor at all It'll need one for doc comments but otherwise yeah | 02:12:08 |
| Lunaphied | In reply to @raitobezarius:matrix.org
maybe in that case, what we can do is to have GHA infrastructure perform regular builds and push it to our cache? This means delegating trust to GHA | 02:13:22 |
| delroth | Oh god, I've been looking at the static initializers again, and there are some major crimes being done there. For example, GlobalConfig::Register is being used across shared libraries, so now it's really not trivial to invert the dependency to have a single initialization function. | 03:31:40 |
| jade_ | sigh | 05:31:18 |
| jade_ | hm | 05:31:34 |
| jade_ | you could fix this tho | 05:31:37 |
| jade_ | you would just have to have init_libWhatever | 05:31:45 |
| jade_ | and then that gets called on startup | 05:31:51 |
