sphalerite changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS 19.03 released! https://discourse.nixos.org/t/nixos-19-03-release/2652 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html https://r13y.com | 19.03 RMs: samueldr,sphalerite | https://logs.nix.samueldr.com/nixos-dev
jtojnar has joined #nixos-dev
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-dev
orivej_ has quit [Ping timeout: 246 seconds]
taktoa has quit [Quit: taktoa]
noonien has quit [Quit: Connection closed for inactivity]
domenkozar has quit [Quit: WeeChat 2.0]
drakonis has joined #nixos-dev
MichaelRaskin has quit [Quit: MichaelRaskin]
peti has quit [Quit: WeeChat 2.1]
ckauhaus has joined #nixos-dev
zarel has joined #nixos-dev
psyanticy has joined #nixos-dev
orivej has joined #nixos-dev
zarel has quit [Ping timeout: 276 seconds]
zarel has joined #nixos-dev
jtojnar has quit [Ping timeout: 255 seconds]
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 250 seconds]
orivej has quit [Ping timeout: 244 seconds]
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 258 seconds]
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 252 seconds]
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 258 seconds]
zarel has quit [Ping timeout: 244 seconds]
zarel has joined #nixos-dev
phreedom has quit [Ping timeout: 256 seconds]
phreedom_ has joined #nixos-dev
{^_^} has quit [Remote host closed the connection]
<aminechikhaoui> niksnut I would guess using the new Nix ui for nixops would be fine at this point ? e.g https://github.com/NixOS/nixops/pull/1135
<aminechikhaoui> not sure if it should be avoided as it's still considered experimental
<niksnut> aminechikhaoui: I think that's fine
<aminechikhaoui> 👍
<niksnut> there are likely to be some UI changes related to flakes, but they shouldn't affect copying store paths
<aminechikhaoui> looking forward to seeing the nix flakes implementation :)
drakonis1 has joined #nixos-dev
drakonis has quit [Quit: WeeChat 2.3]
drakonis1 is now known as drakonis
<gchristensen> it is in the tweag/nix repo!
<aminechikhaoui> great
<drakonis> oho!
<gchristensen> and being built by hydra in the nix/flakes jobslet
<drakonis> wouldn't nix with flakes be the real nix 2.0?
<drakonis> its such a significant improvement on nix
<matthewbauer> anyone know why https://hydra.nixos.org/job/nixpkgs/trunk/unstable is not updating?
justanotheruser has quit [Ping timeout: 246 seconds]
gchristensen has quit [Quit: WeeChat 2.2]
roberth has joined #nixos-dev
grahamc has joined #nixos-dev
justanotheruser has joined #nixos-dev
hedning_ has quit [Ping timeout: 244 seconds]
nocent has joined #nixos-dev
grahamc is now known as gchristensen
gchristensen is now known as {^_^}
{^_^} is now known as gchristensen
{^_^} has joined #nixos-dev
drakonis has quit [Quit: WeeChat 2.4]
genesis has joined #nixos-dev
ajs124 has quit [Quit: Gateway shutdown]
ajs124 has joined #nixos-dev
pie_ has joined #nixos-dev
<pie_> does anyone know how nix does infinite loop detection?
<gchristensen> before forcing an expression to evaluate, it marks the type as a blackhole
<gchristensen> so that if the exact same thunk is evaluated again, it sees it not as a thunk, but as a blackhole and then errors
pie__ has joined #nixos-dev
<pie_> hm, thanks, i think ive heard of that approach
<pie_> basically im thinking it would be great to have some better infinite recursion tooling / better output
<pie_> like a loop trace or something
<gchristensen> 1,000,000x agreed!
<pie_> because i just had a really hard time debugging something
<pie_> and only ended up fixing it by noticing i made a stupid mistake
<pie_> i still dont know why exactly it broke
pie___ has quit [Remote host closed the connection]
<infinisil> pie_: hnix has better errors I think, maybe check out what it would've said
<pie_> oh thats an idea
<pie_> i should go back and check that later...
<pie_> gchristensen, is that basically like keeping track of already visited nodes
<pie_> (tv, see above)
<gchristensen> not sure exactl5y
<pie_> yeah, to me this does look like basically setting a "ive been here" flag
<pie_> thanks
<pie_> hmm...that seems efficient but i can see how you cant get a infinite loop trace from that
<pie_> i.e. it doesnt know where the loop is
<pie_> but...it does somehow keep track of files we've executed through?
<pie_> I guess thats just a normal stack trace.
<gchristensen> maybe my flamegraph code which shows function entrance and exits would be helpful
<infinisil> pie_: The --show-trace trace you get is from `builtins.addErrorContext` fyi
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-dev
pie_ has quit [Ping timeout: 246 seconds]
<lopsided98> The host's bison gets used when cross compiling
psyanticy has quit [Quit: Connection closed for inactivity]
<lopsided98> Oh, I see, its because optional (not optionals) is used with a list argument
ckauhaus has quit [Quit: WeeChat 2.4]
phreedom has joined #nixos-dev
phreedom_ has quit [Ping timeout: 256 seconds]
pie_ has joined #nixos-dev
zarel has quit [Ping timeout: 258 seconds]
phreedom has quit [Quit: No Ping reply in 180 seconds.]
phreedom has joined #nixos-dev
disasm has quit [Ping timeout: 246 seconds]
disasm has joined #nixos-dev
niksnut has quit [Ping timeout: 244 seconds]
niksnut has joined #nixos-dev