michaelpj has quit [(Quit: ZNC 1.6.5 - http://znc.in)]
michaelpj has joined joined #nixos-dev
JosW has joined joined #nixos-dev
zraexy has quit [(Ping timeout: 258 seconds)]
LnL has joined joined #nixos-dev
MoreTea has joined joined #nixos-dev
goibhniu has joined joined #nixos-dev
goibhniu has quit [(Ping timeout: 240 seconds)]
FRidh has joined joined #nixos-dev
MoreTea has quit [(Ping timeout: 248 seconds)]
kuznero has joined joined #nixos-dev
goibhniu has joined joined #nixos-dev
__Sander__ has joined joined #nixos-dev
FRidh has quit [(Ping timeout: 248 seconds)]
FRidh has joined joined #nixos-dev
jtojnar_ has quit [(Ping timeout: 248 seconds)]
jtojnar_ has joined joined #nixos-dev
seppellll has joined joined #nixos-dev
seppellll has quit [(Ping timeout: 258 seconds)]
sivteck has joined joined #nixos-dev
FRidh has quit [(Ping timeout: 248 seconds)]
sivteck has quit [(Quit: user missing.)]
sivteck has joined joined #nixos-dev
FRidh has joined joined #nixos-dev
sivteck has quit [(Quit: user missing.)]
seppellll has joined joined #nixos-dev
<LnL>
is there something wrong with the *-unstable channels?
<LnL>
recent builds are green but they have not updated for a couple of days
sivteck has joined joined #nixos-dev
sivteck has quit [(Read error: Connection reset by peer)]
sivteck has joined joined #nixos-dev
sivteck has quit [(Quit: user missing.)]
<copumpkin>
niksnut: okay, after that comment I give up on 408 :P
<kuznero>
Can you please give any general recommendations for the one willing to become part of nixos org on github?
<goibhniu>
kuznero: you'd like to be able to merge PRs?
<copumpkin>
kuznero: the usual guidance is just to ping ikwildrpepper after contributing a fair number (I've seen 50-100) of useful PRs or work in other ways
<kuznero>
goibhniu: eventually, yes. ok
<kuznero>
copumpkin: thanks! got the idea
<copumpkin>
no rules set in stone as far as I know. If you have one PR that revolutionizes how Nix works and everyone loves it, I'm sure they'd probably be fine with it. Just looking for some demonstration that you won't go screw up the repo if people stop paying attention :)
<goibhniu>
I see you have 8 PRs so far.
<gchristensen>
it is a bit early, but I'd love for you to join when you've gotten enough practice, kuznero.
<goibhniu>
Also, if you make sensible comments on other PRs and help people out with getting them merged, that would be great.
<copumpkin>
yeah, we're drowning in PRs, so testing them and providing feedback, etc., will be very helpful
<copumpkin>
drowning in PRs is a good problem to have, but still a problem :)
<kuznero>
I see the point. Thanks! This is good enough guidelines for me going forward :) Hope to bring some more folks from my work place. Not sure though if they are going to be contributing, but at least using NixOS.
<copumpkin>
yay
<goibhniu>
o/
<kuznero>
copumpkin: so, jumping on PRs that are sitting there and see how I can help with those... that sounds like interesting way to keep learning :) Will try
<copumpkin>
yeah obviously defer to others if you don't know what's going on (providing bad advice is detrimental, and we've even had newish folks go insulting contributors, so please don't do that either :P) but anything you can help with would be great
<kuznero>
will try to do my best :)
<gchristensen>
kuznero: and mistakes are okay, do your best and we'll be glad to have you
<kuznero>
gchristensen: thanks
<gchristensen>
"code owners" seem not so helpful, they just always request a review from eelco
<copumpkin>
or should I just do 100-500 and then 500+
<copumpkin>
globin: yeah, cool. Mapping package names to known versions seems tricky in general though
<copumpkin>
some of them have very generic names
<globin>
copumpkin: yup but it really is quite good at it
<niksnut>
copumpkin: he's misguided
<niksnut>
sure, it's not an error from the POV of the server
<niksnut>
but the client should still retry...
<copumpkin>
yeah
<copumpkin>
hoping my latest comment will sway
<niksnut>
it just says "remove this stale connection from yoyr connection pool"
<niksnut>
also, there is nothing that clients of aws-sdk-cpp can do to prevent this
<copumpkin>
other than retry like 3 layers up :P
<niksnut>
the use of a connection pool is an internal detail of aws-sdk-cpp that shouldn't be exposed
<niksnut>
yeah, this makes the retry logic in aws-sdk-cpp kinda pointless
<copumpkin>
maybe mention that too? I didn't realize that the pool stuff was in there
<niksnut>
if we need to implement our own retry on top of it
<globin>
copumpkin: would be nice if we'd include all language in the packages.json, those would be interesting, too => probably build special package.jsons for repology
<copumpkin>
yeah
<gchristensen>
ok y'all, I'm shutting down grahamcofborg for most of the next day, only running when I have 100% battery and am plugged in to charge
<copumpkin>
:) cool
<copumpkin>
gchristensen: any thoughts on 500 vs. 1000?
<copumpkin>
I'm thinking 101-500 is interseting range and then 500+
<gchristensen>
cool, and >??? can be the standard mass-rebuild
<copumpkin>
yeah
<globin>
gchristensen: have a power socket adapter with you? ;)
<gchristensen>
:shipit:
<copumpkin>
although I guess some folks might still want to treat "changes the stdenv" as special
<gchristensen>
globin: 2! :)
<copumpkin>
could just be 10.rebuilds-linux: stdenv
<globin>
gchristensen: whoa %)
<copumpkin>
?
<copumpkin>
that would be pretty clear about the definition
<gchristensen>
copumpkin: meh, they can send a PR if they'd like
<copumpkin>
ok :)
<gchristensen>
globin: one for Emily :)
<copumpkin>
okay, the tags are colored and sized appropriately
<copumpkin>
I guess there's a special case of "rebuilds: 0
<copumpkin>
that is unhandled right now
zraexy has joined joined #nixos-dev
sivteck has quit [(Quit: user missing.)]
sivteck has joined joined #nixos-dev
jtojnar_ has quit [(Remote host closed the connection)]
Sonarpulse has joined joined #nixos-dev
FRidh has quit [(Ping timeout: 240 seconds)]
__Sander__ has quit [(Quit: Konversation terminated!)]
<aminechikhaoui>
What should be the ownership of the /nix/var/nix/gcroots/hydra/ folder in a hydra instance ?
<aminechikhaoui>
I think I messed up a bit with that folder and the hydra-queue-runner of my server is barfing about permission denied of non existent roots
<aminechikhaoui>
ah wait the group was root -_-
goibhniu has quit [(Ping timeout: 240 seconds)]
sivteck has quit [(Quit: user missing.)]
seppellll has left #nixos-dev ["Leaving"]
sivteck has joined joined #nixos-dev
<copumpkin>
in ‘toFile’: the file ‘x.json’ cannot refer to derivation outputs :(
<copumpkin>
:( :( :(
MichaelRaskin has joined joined #nixos-dev
<copumpkin>
niksnut: is there a good way to get nix-instantiate to spit out .drvs it finds along the way during an --eval --strict?
<niksnut>
copumpkin: don't think so
<copumpkin>
:( I'm trying to get --eval --strict --json to contain valid paths and it's proving to be a real PITA
<copumpkin>
I tried writeText (builtins.toJSON ...) as a derivation and that's proving to be a pain because it's a real derivation and doesn't work if system != currentSystem
<copumpkin>
builtins.toFile refuses to write strings with dependencies
<MichaelRaskin>
Well, there is discarding context (although it is unsafe, but it exists.)