<julm>
qyliss: glad to see you've made a services.public-inbox! However AFAICS, git clone https://edef.eu/~qyliss/nixlib.git takes a long long time because --depth 1 cannot be used over "dumb http" protocol
<julm>
good, took ~15 minutes to clone, but it worked :)
<julm>
qyliss++
<{^_^}>
qyliss's karma got increased!
alp has joined #nixos-dev
JJJollyjim has joined #nixos-dev
cole-h has quit [Quit: Goodbye]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
justanotheruser has quit [Ping timeout: 256 seconds]
<clever>
i'm suspecting that the `$x->{new}` part of this line in hydra, is causing queue-runner to just entirely ignore cached builds
<clever>
as a result, the build is just forever stuck in the queue, and never completes
<clever>
but it can easily got un-noticed, because restarting any build causes a `checking the queue for builds > 0...` which resolves the issue temporarily
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
drakonis has joined #nixos-dev
orivej has quit [Ping timeout: 260 seconds]
bhipple has quit [Ping timeout: 246 seconds]
bhipple has joined #nixos-dev
<cole-h>
domenkozar[m]: Does cachix-action also `cachix use` the specified cache? Or is it only used for pushing to a cache?
pxc has quit [Read error: Connection reset by peer]
pxc has joined #nixos-dev
<domenkozar[m]>
both :)
<cole-h>
Perfect, thanks :D
alp has quit [Ping timeout: 265 seconds]
alp has joined #nixos-dev
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
bhipple has quit [Ping timeout: 256 seconds]
bhipple has joined #nixos-dev
alp has quit [Ping timeout: 244 seconds]
alp has joined #nixos-dev
ixxie has quit [Quit: Lost terminal]
__monty__ has quit [Quit: Gotta work on that WPM, zaeph.]
alp has quit [Quit: Leaving]
bhipple has quit [Ping timeout: 260 seconds]
<manveru>
seems like flakes with more than 50 or inputs from github will trigger github rate limiting :P
<manveru>
*50 or more
<drakonis>
wait what
<manveru>
tried making a flake with 360 inputs, guess this isn't gonna happen anytime soon
<drakonis>
i gotta see this
<emily>
manveru: yeah :/ there is an option to provide github api token
<emily>
github-access-token
<manveru>
`nix flake update` uses github api instead of `git ls-remote`, so it has to be throttled...
<emily>
but it is trusted user only, and there is no way to set it in nixos without leaking your token into the store afaict
* emily
wishes it respected GITHUB_TOKEN like many tools but I guess it might be going through the daemon which complicates that
<drakonis>
you got me curious now
<manveru>
you want to get the error?
<drakonis>
i'm curious about how the flake file looks like
<{^_^}>
#87260 (by cyplo, 2 days ago, open): cannot boot linux_latest_hardened on lvm-on-luks anymore
<julm>
how can I watch/register for PR mentioning specific keyword/topic in nixpkgs? I'd like to be notified when there is a PR to review concerning stuffs I know/care but for which I am not a maintainer of?
<MichaelRaskin>
I think you could make a bookmark of the search?
<MichaelRaskin>
Or maybe become a maintainer
<gchristensen>
nix flake update should be client-side
<gchristensen>
afaik
<julm>
MichaelRaskin: ok, so no magic features of some tools like nixpkgs-review exploiting GitHub's API
<cole-h>
Not premade, that I know of. You could always make your own ;^)
<MichaelRaskin>
julm: there is a magic feature! it handles maintainer list!
<MichaelRaskin>
I mean, there are independently maintainer list, and CODEOWNERS files. How many levels there _should_ be?
<julm>
I can maybe easily configure my irssi to filter messages from {^_^} on #nixos in a dedicated buffer
<MichaelRaskin>
You can still wget GH saved search, I guess, until they «improve it» by making JS-only
<emily>
julm: I mean, have you considered adding yourself to the maintainers list? ^^
<emily>
"interested enough to monitor GitHub issues/PRs" is pretty much exactly the criterion in my understanding
<julm>
not sure if it would be ok to claim to be a maintainer when I just want to be a concerned follower :\
<julm>
to know what's coming, and have a voice, or not
<MichaelRaskin>
I think only one attempt of defining maintainership expectations has ever reached a consensus.
<MichaelRaskin>
And it says that a maintainer will do a best effort to help resolving any issues with the package explicitly brought to their attention, and believes they can be useful in that.
<MichaelRaskin>
I guess we are talking about packages where there is no extremely active and involved maintainer, right?
<emily>
if maintainers were required to keep packages up-to-date at all times then there'd be a lot more packages in nixpkgs without maintainers :p
<MichaelRaskin>
Nah, just a lot fewer packages in Nixpgs
<emily>
I think especially when you're only one of several maintainers the obligations are quite slim
<MichaelRaskin>
And maybe Nixpkgs would have burned out by now.
<MichaelRaskin>
On the other hand, maintainer authority is also quite limited.
tilpner has quit [Remote host closed the connection]
<julm>
MichaelRaskin: I was thinking about postgresql or other advanced/critical packages, for which I'm a concerned user but not knowledgeable enough to pretend to be maintainer. But maybe in that case following the changelog is enough, but it's kinda more passive because it somehow comes after the decisions have been made
<MichaelRaskin>
Not sure there is always changelog there
<MichaelRaskin>
You can also subscribe a mailbox you do not value to a full stream of Github notifications
<MichaelRaskin>
It's not that bad, I do it and skim the headers
<MichaelRaskin>
I have a feeling we tend not to use CODEOWNERS too much
<julm>
maybe II can patch CODEOWNERS locally so that nixpkgs-review will alert me
<MichaelRaskin>
That sounds complicated.
<MichaelRaskin>
Maybe create a new mailbox and filter it?
<julm>
hm, I don't grep anything in nixpkgs-review that concern the maintainer list or CODEOWNER
<julm>
MichaelRaskin: the mail notification seems the best indeed. That was there all along in the front page: "Watch -> Watching" on https://github.com/NixOS/nixpkgs