v0|d has quit [Read error: Connection reset by peer]
jtojnar has quit [Read error: Connection reset by peer]
orivej has quit [Ping timeout: 272 seconds]
drakonis has quit [Ping timeout: 248 seconds]
vika_nezrimaya has quit [Ping timeout: 245 seconds]
justanotheruser has quit [Quit: WeeChat 2.4]
justanotheruser has joined #nixos-dev
das_j has quit [Remote host closed the connection]
globin has quit [Ping timeout: 252 seconds]
primeos has quit [Ping timeout: 252 seconds]
aszlig has quit [Ping timeout: 245 seconds]
nwspk has quit [Ping timeout: 264 seconds]
globin has joined #nixos-dev
aszlig has joined #nixos-dev
primeos has joined #nixos-dev
nwspk has joined #nixos-dev
primeos has quit [Ping timeout: 264 seconds]
nwspk has quit [Ping timeout: 264 seconds]
ericnoan has quit [Ping timeout: 245 seconds]
primeos has joined #nixos-dev
ericnoan has joined #nixos-dev
nwspk has joined #nixos-dev
orivej has joined #nixos-dev
phreedom_ has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
primeos has quit [Ping timeout: 264 seconds]
primeos has joined #nixos-dev
marek has quit [Ping timeout: 268 seconds]
marek has joined #nixos-dev
nwspk has quit [Ping timeout: 252 seconds]
primeos has quit [Ping timeout: 264 seconds]
primeos has joined #nixos-dev
nwspk has joined #nixos-dev
callahad306 has joined #nixos-dev
callahad30 has quit [Ping timeout: 245 seconds]
<domenkozar[m]>
interesting, we have more and more google engineers contributing to nixpkgs
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
<Mic92>
This is just a correlation between smart people, nix and google :)
orivej has quit [Ping timeout: 258 seconds]
jtojnar has joined #nixos-dev
orivej has joined #nixos-dev
pie__ has quit [Ping timeout: 252 seconds]
<arianvp>
fpletz: I'm super happy to see that your talk about Nix got accepted at ASG
<arianvp>
I wanted to submit a similar talk, then didn't and felt bad. but happy we're being represented
orivej has quit [Ping timeout: 246 seconds]
vcunat has quit [Ping timeout: 250 seconds]
<yorick>
ExecStartPre should really have a merge solution
<yorick>
since you can specify it multiple times in systemd
<adisbladis>
yorick: Same for a lot of systemd options actually.. Environment propably being the most generally useful one
orivej has joined #nixos-dev
vcunat has joined #nixos-dev
vcunat has quit [Client Quit]
<gchristensen>
fyi: one of the macos builders has been pulled out of hydra to debug a darwin specific build problem, so we're at reduced capacity for now
FRidh has quit [Ping timeout: 272 seconds]
Jackneill has quit [Ping timeout: 248 seconds]
Jackneill has joined #nixos-dev
pie_ has joined #nixos-dev
v0|d has joined #nixos-dev
justanotheruser has quit [Ping timeout: 268 seconds]
jtojnar has quit [Quit: jtojnar]
jtojnar_ has joined #nixos-dev
justanotheruser has joined #nixos-dev
justanotheruser has quit [Quit: WeeChat 2.4]
justanotheruser has joined #nixos-dev
marek has quit [Ping timeout: 245 seconds]
<arianvp>
yorick: I'm pretty sure that systemd options are merged , aren't they?
<arianvp>
nasty thing is that systemd has many ad hoc ways of defining arrays
marek has joined #nixos-dev
<arianvp>
some fields are comma-separated, some are space separated some are multiple fields repeated
<arianvp>
some are arbitrary combinations of them but not all combinations. it's very inconsistent
<yorick>
arianvp: I don't think so, I have a "todo: this breaks if there's already an ExecStartPre" comment somewhere
<adisbladis>
arianvp: I believe that's using the standard string merge behaviour?
jtojnar_ has quit [Read error: Connection reset by peer]
ixxie has joined #nixos-dev
<gchristensen>
oh dear, my gdb is using python3 with python2 setuptools
<andi->
gdb is using setuptools o.O
ixxie has quit [Ping timeout: 246 seconds]
ixxie has joined #nixos-dev
ixxie has quit [Client Quit]
ixxie has joined #nixos-dev
ixxie has quit [Client Quit]
ixxie has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis has quit [Ping timeout: 248 seconds]
drakonis has joined #nixos-dev
<thoughtpolice>
andi-: Yeah, it's so you can Python script GDB (in two ways: run scripts in GDB, or write scripts that control GDB instances)
<thoughtpolice>
So you need setuptools in case you want to find python libs
<andi->
The last part was missing for me :)
Guanin has joined #nixos-dev
janneke has quit [Quit: janneke quits Mes'sing]
janneke has joined #nixos-dev
phreedom has quit [Write error: Connection reset by peer]
phreedom has joined #nixos-dev
<gchristensen>
I'd like to do some benchmarking on a change I've made to Nix, anyone have ideas on how to do thaht?
<simpson>
gchristensen: Hm, like a reduction-intensive benchmark, or a derivation-intensive benchmark? infinisil might have something for the former, like nixlisp.
<gchristensen>
samueldr: I think it is a bit tricky because `tested` doesn't refer to anything in particular, and then not all of the artifacts produced by jobs `tested` refers to are interesting
<gchristensen>
samueldr: I would really like to make the searchable, multi-page docs part of 19.09. do you think we could do some collaboration on the remaining steps?
<samueldr>
yes, I think we can
<samueldr>
(collaborate)
<samueldr>
gchristensen: what about `tested`?
<samueldr>
gchristensen: the mirror script doesn't refer to tested
<gchristensen>
`tested` is the canary job
<samueldr>
yeah
<gchristensen>
ah
<samueldr>
though I think I have a solution
<gchristensen>
well it does refer to `tested`
<gchristensen>
but it is passed in as an argument
<samueldr>
yeah, though `downloadFile` only refers to job names AFAICT
<samueldr>
so I think we're in the clear
<samueldr>
make an atribute `manifest` or `mirror` or whatever, which has a simple output, a file (json?) with names that `downloadFile` can use
<samueldr>
and I'm thinking that, this way, it would be possible to remove the conditions on nixos and -small our of the script
<samueldr>
out of the*
<gchristensen>
maybe like a file called hydra-build-products :D
<samueldr>
kind of, but for the eval
<samueldr>
no?
<samueldr>
(I might be confusing something too)
<gchristensen>
hrm.
<gchristensen>
not sure
<samueldr>
not sure if I'm confused or not sure about the approach?
<gchristensen>
well I was confused
<gchristensen>
I thought you were saying don't equip the "Tested" job with anything special, but I think you are saying equip the tested job with something special
<samueldr>
yeah
<gchristensen>
my thinking was hydra is already equipped with something
<gchristensen>
so could enumerate all the component jobs of tested and mirror the hydra-build-products with a leading two words we like
<samueldr>
though, isn't tested something like an aggregate job?
<samueldr>
and those don't have outputs?
<gchristensen>
right
<gchristensen>
or to clarify, mirror the hydra-buid-product entries with a type and subtype we like