| 18 Mar 2025 |
 emily | only a subset of things block the channel from advancing | 15:49:04 |
| emily | if all failed builds stopped unstable from bumping, it'd never bump | 15:49:12 |
| emily | but we do have e.g. automated end-to-end testing of installations, common graphical environments, etc. | 15:49:24 |
 laauurraa | Yeah it does elikoga, that's what I expected. Being a bit difficult to test whether it launches or not | 15:49:28 |
| emily | (since we have ~100k builds and many of them are always broken 🫠) | 15:50:18 |
| laauurraa | I wish it was a little bit clearer when a package is stable or not? | 15:50:37 |
| laauurraa | Would it be possible to add something to the nixpkgs search interface to link or show like a red/yellow/green bubble per platform about how "stable" it is? Whether builds have errors etc? | 15:52:40 |
| laauurraa | That would be useful | 15:52:46 |
| laauurraa | Or even just a link to the relevant page in hydra would already be helpful | 15:53:18 |
| 19 Mar 2025 |
|  @jkxyz:matrix.org left the room. | 16:17:32 |
| 20 Mar 2025 |
|  srp joined the room. | 03:15:29 |
| srp changed their display name from Seraphim Pardee to srp. | 03:19:04 |
 elikoga | In reply to @laauurraa:matrix.org
Would it be possible to add something to the nixpkgs search interface to link or show like a red/yellow/green bubble per platform about how "stable" it is? Whether builds have errors etc? Nobody built it yet, so it's not there | 11:39:34 |
| elikoga | * Nobody built that integration yet, so it's not there | 11:39:47 |
| elikoga | I don't believe that it's trivial to link the different projects without pulling your hair out in frustration | 11:41:06 |
|  distrostu (Jono) joined the room. | 16:20:06 |
| distrostu (Jono) | I'm having issues with github auth when updating my flake
[jono@dobro:~/sync/configs/nix]$ nix flake update --flake .
error:
… while updating the lock file of flake 'git+file:///home/jono/sync/configs?dir=nix'
… while updating the flake input 'disko'
… while fetching the input 'github:nix-community/disko'
error: unable to download 'https://api.github.com/repos/nix-community/disko/commits/HEAD': HTTP error 401
response body:
{
"message": "Bad credentials",
"documentation_url": "https://docs.github.com/rest",
"status": "401"
}
(base)
if I directly curl that https://api.github.com/repos/nix-community/disko/commits/HEAD
I get a 200.
I have a feeling there is some expired access token on my system, but I dont think I set one and I'm not sure where it would be?
| 16:20:31 |
| distrostu (Jono) | * I'm having issues with github auth when updating my flake
[jono@dobro:~/sync/configs/nix\]$ nix flake update --flake .
error:
… while updating the lock file of flake 'git+file:///home/jono/sync/configs?dir=nix'
… while updating the flake input 'disko'
… while fetching the input 'github:nix-community/disko'
error: unable to download 'https://api.github.com/repos/nix-community/disko/commits/HEAD': HTTP error 401
response body:
{
"message": "Bad credentials",
"documentation_url": "https://docs.github.com/rest",
"status": "401"
}
(base)
if I directly curl that https://api.github.com/repos/nix-community/disko/commits/HEAD
I get a 200.
I have a feeling there is some expired access token on my system, but I dont think I set one and I'm not sure where it would be?
| 16:21:05 |
| 21 Mar 2025 |
| emily | TIL: outputs = import ./function.nix; is not allowed | 11:38:19 |
| emily | wonder if that's a bug | 11:38:24 |
 remi-gelinas | In flake.nix? That's expected, it's not a real Nix file | 11:39:00 |
| elikoga | There's quite a bit of restrictions on the flake.nix format that people complain about sometimes | 11:39:06 |
| emily | for inputs I expect that by now, yes | 11:39:10 |
| emily | for outputs I don't think there is any rational point | 11:39:16 |
| emily | and the error seems like it's probably just an implementation bug | 11:39:24 |
| emily | ("expected a function but got a thunk") | 11:39:31 |
| elikoga | No that sounds like the format restriction+bad error messages | 11:39:46 |
| emily | oh, I guess it's because outputs's arguments get introspected to define inputs 🙃 | 11:39:47 |
| emily | when you don't explicitly list them | 11:39:56 |
| emily | (and it uses the registry inputs, which are pinned by default in some setups, so pretty footgunny) | 11:40:11 |
