<samueldr>
hmmm, I can't find a link to the graph that would help me figure out if the aarch64 builders are having issues being provisioned or not, again
justanotheruser has quit [Ping timeout: 276 seconds]
justanotheruser has quit [Ping timeout: 265 seconds]
justanotheruser has joined #nixos-dev
<adisbladis>
FRidh: Can I pm?
drakonis has quit [Ping timeout: 250 seconds]
<pie_>
clever: dunno when im going to get around to trying to work on this harder, but a while back i wanted to do some invariance testing of nix expressions because i was trying to write some stuff that was too complicated for me to get right
<pie_>
and nix doesnt really provide the equality testing primitives for me to do that
<pie_>
so just now i thought, what if i expose something via importnative?
<clever>
pie_: what are you trying to test?
<pie_>
i dont have it in front of me right now but uhh... the withPackages stuff
<pie_>
i dont have a real question other than do you think it would be reasonable for me to try to expose some more equality testing stuff though the c++ interfaces
<pie_>
i think one of the things i wanted was testing equality of funcitons, but i cant remember whz
<pie_>
*why
<clever>
pie_: == does a decent amount of stuff, so you could check to see if it fits first
<pie_>
i remember having some problems with that but i cant remember what exactly, id have to have another go
<samueldr>
not thrilled on the prospect of bisecting 19.03's history compared to 18.09
red[evilred] has joined #nixos-dev
<red[evilred]>
Eww
<red[evilred]>
Doesn’t sound like a good time
<red[evilred]>
It wouldn’t be too bad if you could farm out compilation to a couple hundred cores
<samueldr>
it's likely that the scope can be reduced a bunch... e.g. ignore all under the pkgs and nixos folder, look at the commits and intuit the issue
<red[evilred]>
I guess it isn’t an issue you can track by just following code flow to find the bug and then pin it to a commit?
<domenkozar[m]>
kreisys: didn't you deploy hetzner recently?
<aszlig>
domenkozar[m]: thanks, will look into that later
<aszlig>
domenkozar[m]: looks more like they changed their internal robot API
<samueldr>
with master, tried generating 18.09's listing and it indeed doesn't list unfree packages
<aszlig>
oh wait a minute, this is not an issue with the scraper
<domenkozar[m]>
but rather?
drakonis has quit [Quit: WeeChat 2.6]
<aszlig>
domenkozar[m]: something specific to your robot account i guess, because when doing the same request for all my robot accounts, i don't get an http 401
<domenkozar[m]>
I tried the same documentation with two different people and they both got the same error
<aszlig>
it looks more like the credentials are wrong
<domenkozar[m]>
what page should they be used on to confirm they work?
<samueldr>
hmmm, while the "cause" of the issue has been identifier, further changes seem to have changed the behaviours such as simply reverting the change is not enough
<samueldr>
has been identified*
Jackneill has quit [Read error: Connection reset by peer]
ixxie has joined #nixos-dev
ris has joined #nixos-dev
<tilpner>
Can I just ask people to be shepherds for my RFC, or will that introduce an unwanted bias?
<tilpner>
Also, it says "The author cannot be part of the Shepherd Team", but what co-authors?
<tilpner>
*what about co-authors
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
psyanticy has quit [Quit: Connection closed for inactivity]
pie_ has quit [Ping timeout: 250 seconds]
<globin>
tilpner, both is fine
<tilpner>
Hey globin, want to be a shepherd for rfcs#55 ? c.c