| 22 Jun 2022 |
 Sandro | Filesystem also can be S3, right? | 15:38:14 |
 das_j | wat | 15:38:37 |
| das_j | no, s3 is not a filesystem | 15:38:49 |
| das_j | If you mean store_uri - then yes, that can be a s3 url | 15:39:48 |
 trofi | Unqueryable logs makes sense. I hoped for a blessed tool to fetch build logs (possibly with a bit of caching support). | 16:20:04 |
 ajs124 | you'd probably need to send an api request for each build in the eval, with that you can query the binary cache for the logs | 16:24:43 |
| Sandro | In reply to @janne.hess:helsinki-systems.de
If you mean store_uri - then yes, that can be a s3 url I meant hydra stores logs on s3 | 19:51:53 |
| 23 Jun 2022 |
 @linus:schreibt.jetzt | In reply to @trofi:matrix.org
Unqueryable logs makes sense. I hoped for a blessed tool to fetch build logs (possibly with a bit of caching support). nix log is a blessed tool for fetching build logs | 00:40:47 |
| @linus:schreibt.jetzt | It's not hydra-aware though | 00:40:56 |
 Dandellion | At least when I only had one job, now that I have two it never completes an evaluation | 04:07:00 |
| das_j | In reply to @sandro:supersandro.de
I meant hydra stores logs on s3 There is an extra option for that | 06:57:38 |
 @ulrikstrid:matrix.org | Does the githubstatus plugin work with flakes? And can I use a Bearer token instead of Basic auth? | 07:09:53 |
| Sandro | Is the input tab broken with flakes? | 11:13:02 |
| Sandro | In reply to @linus:schreibt.jetzt
It's not hydra-aware though Does hydra not write the logs into the mix store? | 11:13:29 |
| @linus:schreibt.jetzt | In reply to @sandro:supersandro.de
Does hydra not write the logs into the mix store? Yes, but you can't tell nix log "get the logs for this job from this evaluation" without extra steps | 11:27:30 |
| @linus:schreibt.jetzt | You have to give it a drv path | 11:27:30 |
| das_j | In reply to @sandro:supersandro.de
Is the input tab broken with flakes? Does seem like it. A plugin could be written for that | 11:29:47 |
| Sandro | In reply to @linus:schreibt.jetzt
You have to give it a drv path Don't we need to get them anyway? | 16:07:27 |
| Sandro | In reply to @janne.hess:helsinki-systems.de
Does seem like it. A plugin could be written for that Can it without flakes track multiple branches? | 16:08:16 |
| @linus:schreibt.jetzt | In reply to @sandro:supersandro.de
Don't we need to get them anyway? I don't know, tr?fi's use case doesn't specify that they need to get drvs. | 18:14:47 |
| das_j | In reply to @sandro:supersandro.de
Can it without flakes track multiple branches? I wrote one for npins, it works well. So probably (?) | 19:07:09 |
| Sandro | In reply to @janne.hess:helsinki-systems.de
I wrote one for npins, it works well. So probably (?) Where can I find that? | 23:15:09 |
| Sandro | I'd really would want to get inputs to work for flakes | 23:15:10 |
| 24 Jun 2022 |
| das_j | In reply to @sandro:supersandro.de
Where can I find that? It's not really production-grade which is why it's not available anywhere | 12:06:37 |
| das_j | But you essentially hook intp evalAdded, parse the repo URLs and git hashes, and do $evaluation->jobsetevalinputs->create | 12:07:16 |
| das_j | * But you essentially hook into evalAdded, parse the repo URLs and git hashes, and do $evaluation->jobsetevalinputs->create | 12:07:24 |
| @linus:schreibt.jetzt | In reply to @janne.hess:helsinki-systems.de
It's not really production-grade which is why it's not available anywhere put a big ol' disclaimer on it and publish it anyway? | 12:07:42 |
| @linus:schreibt.jetzt | only non-production-grade software is better than no software | 12:08:01 |
| das_j | In reply to @linus:schreibt.jetzt
put a big ol' disclaimer on it and publish it anyway? I'd rather finish it first. It's 95% done, just the github and gitlab integration is lacking a bit | 12:08:09 |
| das_j | The entire plugin requires this in Hydra first though: https://github.com/NixOS/hydra/pull/1220 | 12:08:35 |
