worldofpeace_ changed the topic of #nixos-dev to: #nixos-dev NixOS Development (#nixos for questions) | NixOS 20.03 BETA Announced https://discourse.nixos.org/t/nixos-20-03-beta/5935 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 19.09 RMs: disasm, sphalerite; 20.03: worldofpeace, disasm | https://logs.nix.samueldr.com/nixos-dev
<jtojnar> deadlock detected
<worldofpeace> Jan Tojnar: ooh, staging-next was merged ✨
erictapen has quit [Ping timeout: 265 seconds]
<jtojnar> yup, now we just need unstable to succeed
<jtojnar> and then bump gnome to 3.36.1
<worldofpeace> Jan Tojnar: I'm also going to be able to update pantheon to use mutter 3.36. Would you be cool with this patch https://github.com/NixOS/nixpkgs/blob/master/pkgs/desktops/gnome-3/core/mutter/0001-Revert-ClutterActor-Preserve-valid-paint-volumes-til.patch being added to default mutter? Upstream is unresponsive to fixing that issue.
<worldofpeace> very annoying ghosting of menu's in gala
<jtojnar> worldofpeace could we add it in gala with overrideAttrs?
<jtojnar> from reading the issue, it does not look like gnome-shell is affected and reverting it would affect performance
<worldofpeace> Jan Tojnar: I'm not sure. The patch I ended up with was what worked perfectly 7 months ago
<jtojnar> worldofpeace yeah, looking at your patch, commenting that line is equivalent
<jtojnar> though removing the property altogether is probably safer in case they add another falsification
<jtojnar> why si linux timing out on aarch64-linux so often?
<cole-h> Big build on not-big devices, maybe?
<jtojnar> would that happen?
<samueldr> we don't have not-big aarch64 devices on Hydra, cole-h
<cole-h> Oh :)
<samueldr> my theory, without the ability to check, is ressource exhaustion
<samueldr> most likely I/O
<samueldr> I don't remember how the machines are configured, but if the kernel build is sent to a server that runs multiple jobs in parallel, I/O takes a hit
<samueldr> and looking at /machines, it looks like most aarch64-linux machines do run multiple tasks in parallel
<samueldr> if my assumption is right, this is something that could be solved via alternative scheduling methods
<samueldr> I'm assuming a lot, but I'm thinking most "big builds" like webkits, chromes, firefoxes, linux, all end-up in resource exhaustion tarpits
<gchristensen> we could make 1 arm box bigp
<gchristensen> we could make 1 arm box big-parallel with few jobs at a time
<samueldr> if we can try it out, 1 or 2 jobs
<gchristensen> I can't try it tonight I don't think
<samueldr> that's alright, whenever :)
<gchristensen> I mean I could, but it'd still get -j2 or whatever :P
<samueldr> ah
<gchristensen> (kind of wish the cores param could be sent over the remote build protocol)
<samueldr> let's imagine that firefox never builds after 10 hours, that's one failed job, that during those 10 hours stopped up to 14 other jobs from being able to finish in less than 10 hours
<samueldr> even if firefox takes 2 hours to build (it shouldn't), it's a win, we would win 5 firefox over none
<gchristensen> +1
<samueldr> and the queue could end up beint treated more slowly, but with better results (and even then I'm not positive it would be slower)
<gchristensen> +1
<gchristensen> yeah I've thought this'd be a good thing to try for a bit, but was persuaded by people worried it'd be wasteful
<samueldr> I'm sure the tarpit makes trivialer jobs take much longer, too
<gchristensen> :)
Scriptkiddi has quit [Quit: killed]
ajs124 has quit [Quit: killed]
das_j has quit [Quit: killed]
ajs124 has joined #nixos-dev
Scriptkiddi has joined #nixos-dev
das_j has joined #nixos-dev
teto has quit [Ping timeout: 272 seconds]
LnL has quit [Ping timeout: 256 seconds]
LnL has joined #nixos-dev
LnL has joined #nixos-dev
LnL has quit [Changing host]
justan0theruser is now known as justanotheruser
drakonis has quit [Read error: Connection reset by peer]
<etu> jtojnar: Does it still fail or did you look into it?
<jtojnar> etu should be fixed now
<etu> jtojnar: Ok, just found your commit, thanks :)
lovesegfault has joined #nixos-dev
<lovesegfault> Can someone merge this for me: https://github.com/NixOS/nixpkgs/pull/84163
<{^_^}> #84163 (by lovesegfault, 2 days ago, open): linuxPackages.nvidia_x11: 440.59 -> 440.64
bhipple has quit [Remote host closed the connection]
<Emantor> Whats the general take on "inherit (src.meta) homepage"? I'm getting resistance to change to this in https://github.com/NixOS/nixpkgs/pull/84341/files
<kcalvinalvin> Are there any tips to debug a package that takes really long to build? I'm currently trying to fix a broken package but the build doesn't error out until 25 minutes in
<kcalvinalvin> Wondering if there are some tricks to help with this
<lovesegfault> jtojnar: reproing the build failure for you
<lovesegfault> one moment
<jtojnar> Emantor yeah, I do not like it for the reasons stated, I visit the website on every PR review and not having the URL is an extra step
<jtojnar> kcalvinalvin one possibility is trying to build it in nix-shell, then you can at least reuse the built artefacts, but it will not help with sandboxing issues
<Emantor> I'm 50/50 on it. But typing github repo URLs comes naturally to me, so thats just me. I often prefer not reaching for the mouse and typing things.
lovesegfault has quit [Ping timeout: 265 seconds]
FRidh has joined #nixos-dev
<kcalvinalvin> jtojnar hmmm ok. Thanks for the suggestion
<jtojnar> lovesegfault "No package 'gio-unix-2.0' found" is a packaging issue, it needs to depend on glib
cole-h has quit [Quit: Goodbye]
CRTified has quit [Ping timeout: 240 seconds]
LnL has joined #nixos-dev
LnL has joined #nixos-dev
LnL has quit [Changing host]
LnL has quit [Remote host closed the connection]
LnL has joined #nixos-dev
LnL has joined #nixos-dev
LnL has quit [Changing host]
LnL has joined #nixos-dev
LnL has joined #nixos-dev
LnL has quit [Changing host]
CRTified has joined #nixos-dev
FRidh2 has joined #nixos-dev
FRidh has quit [Ping timeout: 265 seconds]
__monty__ has joined #nixos-dev
erictapen has joined #nixos-dev
v0|d has quit [Remote host closed the connection]
v0|d has joined #nixos-dev
rsa_ has quit [Ping timeout: 265 seconds]
rsa_ has joined #nixos-dev
orivej has quit [Ping timeout: 264 seconds]
<gchristensen> ,tell cole-h a simple one wouldbe collapsing the "adding" "removed" "already" log messages in to one line
<{^_^}> gchristensen: I'll pass that on to cole-h
<gchristensen> I think I caught the biggest source of ofborg-internal-error labels
<gchristensen> it used to be that errors adding a commit status were ignored and the job was restarted. this caused a problem where if there was a error in ofborg, it would write a thousand statuses to a single commit in a retry loop. I changed that recently to propogate the error and ... consider it an error, and apply the ofborg-internal-error label in this case. one of the biggest sources of these errors
<gchristensen> for a bit was GitHub making some fields nullable, and our github API Client considering them required. the next biggest (just fixed) was trying to add a status to a PR after the PR had been force pushed, and the commit not being part of that PR anymore.
teto has joined #nixos-dev
teto has quit [Ping timeout: 260 seconds]
teto has joined #nixos-dev
erictapen has quit [Ping timeout: 256 seconds]
erictapen has joined #nixos-dev
erictapen has quit [Ping timeout: 265 seconds]
erictapen has joined #nixos-dev
rsa has joined #nixos-dev
<globin> teto: i have a fix for all targetPrefix stuff that I'm testing currently
<globin> please don't waste time on qt etc
rsa_ has quit [Ping timeout: 265 seconds]
<teto> globin: anything you would like me to take a look at then ?
<globin> teto: also I'd prefer if you'd create PRs to the branch as long as I'm actively working on it :)
<globin> teto: python2 scandir is still a problem I haven't looked at yet
<teto> globin: sure that's why I asked, then I saw other committing :) feel free to forcepush then
<globin> sphalerite and Ericson2314 at least were in contact with me before pushing
<gchristensen> ,tell cole-h (I already got it actually)
<{^_^}> gchristensen: I'll pass that on to cole-h
erictapen has quit [Ping timeout: 265 seconds]
<teto> btw, when running a --strict --eval, many issues appear in fetchers, it makes harder to see the issues in structured-attrs. Any interest in addressing this ? the issue exists on unstable too
<globin> teto: i currently just diff the current structured-attrs eval to the current trunk eval and look at removed drvs while searching for x86_64-linux to see the drvs that can't eval
rsa_ has joined #nixos-dev
justanotheruser has quit [Ping timeout: 272 seconds]
rsa has quit [Ping timeout: 260 seconds]
bgamari has quit [Ping timeout: 256 seconds]
bgamari has joined #nixos-dev
<jtojnar> huh Evaluation pending since: 17h ago
cole-h has joined #nixos-dev
erictapen has joined #nixos-dev
justanotheruser has joined #nixos-dev
<rycee> Switched my main laptop over to 20.03, works very well!
drakonis has joined #nixos-dev
erictapen has quit [Ping timeout: 250 seconds]
FRidh2 has quit [Ping timeout: 240 seconds]
FRidh2 has joined #nixos-dev
FRidh2 has quit [Client Quit]
teozkr__ has joined #nixos-dev
tetdim has joined #nixos-dev
gleber__ has joined #nixos-dev
cbarrett_ has joined #nixos-dev
teozkr_ has quit [Ping timeout: 246 seconds]
gleber_ has quit [Ping timeout: 246 seconds]
cbarrett has quit [Ping timeout: 246 seconds]
tetdim_ has quit [Quit: ZNC 1.7.3 - https://znc.in]
gleber__ is now known as gleber_
teozkr__ is now known as teozkr_
cbarrett_ is now known as cbarrett
orivej has joined #nixos-dev
<arianvp> How does NixOps do these things where one resource depends on another?
<arianvp> e.g. an route53 on an ELB
<arianvp> does it just arbitrarily re-evaluate the nix file until it reaches a fixed point?
<gchristensen> mmm no
<domenkozar[m]> arianvp: inside the code it enforces order
<domenkozar[m]> it's magic :)
<gchristensen> hrm. I'm not sure, I think it is done in python
<domenkozar[m]> yup
<arianvp> ah so it doesn't make a graph and parallelize?
<arianvp> but just things in serialise?
<domenkozar[m]> resources are evaluated in very specific order
<domenkozar[m]> then machines
<arianvp> that's cheating :)
<arianvp> but fine
<arianvp> I'm hacking something to turn any terraform resource provider into a nixops plugin automagically
<arianvp> domenkozar[m]: and what if you have cross-resource dependencies?
<arianvp> my hetzner having a route in route53?
<gchristensen> oh cool, you should talk to adisbladis about that too once he's back
<gchristensen> I think he has a wip prototype
<domenkozar[m]> arianvp: then you need to order them right
<domenkozar[m]> that's why route53 is one of the first
<arianvp> but how does that work now that nixops is 'pluggable' ?
<domenkozar[m]> good question
<arianvp> do we need to have some global defined ordering in nixops itself?
<domenkozar[m]> no idea, I didn't review that code
<gchristensen> is that actually at evaluation time? I thought that was done in python
<domenkozar[m]> iirc it evaluates bits at different times, but it's for sure in python
<arianvp> I think it evaluates two times. once to get the resources that python than turns into clouds
<arianvp> than it feeds the output from the CloudTM back into the evlauator so that your instances can refer to resources ?
<arianvp> but I guess it has to evaluate multiple times. Once for each cloud resource, given it takes the other resources as arguments
<arianvp> this all is a bit confusing. what if I accidentally refer to route53 in s3? does it crash?
<gchristensen> yeah, this is how it works
<gchristensen> each resource can define a create_after function
<gchristensen> I think it only has to run nix-instantiate once
abathur has joined #nixos-dev
erictapen has joined #nixos-dev
erictapen has quit [Ping timeout: 240 seconds]
erictapen has joined #nixos-dev
lovesegfault has joined #nixos-dev
teto has quit [Ping timeout: 265 seconds]
__monty__ has quit [Quit: leaving]
lovesegfault has quit [Quit: WeeChat 2.8]
lovesegfault has joined #nixos-dev
<worldofpeace> can someone transfer this to nixos-homepage https://github.com/NixOS/nixpkgs/issues/84516 ?
<{^_^}> #84516 (by phenomicall, 43 minutes ago, open): Bad link in website nixos.org
<gchristensen> yep
justanotheruser has quit [Ping timeout: 265 seconds]
<samueldr> gchristensen: is today better for looking at the (assumed) tarpit issue?
<garbas> gchristensen: tnx. are you working on it? or should i give it a try?
<samueldr> garbas: s;[%root%]/;[%root%];g it looks like
<garbas> yeah, already have patch
<samueldr> might need a bit of escaping for the regex though
<samueldr> great
justanotheruser has joined #nixos-dev
erictapen has quit [Ping timeout: 256 seconds]
erictapen has joined #nixos-dev
<gchristensen> garbas: not looking :)
<{^_^}> nixos-homepage#384 (by garbas, 3 minutes ago, open): fix bad links, fixes #383
<cole-h> garbas++ Appears to fix it for me.
<{^_^}> cole-h: 8 hours, 21 minutes ago <gchristensen> (I already got it actually)
<{^_^}> garbas's karma got increased to 12
<{^_^}> cole-h: 11 hours, 32 minutes ago <gchristensen> a simple one wouldbe collapsing the "adding" "removed" "already" log messages in to one line
<cole-h> lol
v0|d has quit [Ping timeout: 256 seconds]
lovesegfault has quit [Quit: WeeChat 2.7.1]
<gchristensen> samueldr: let's see :)
<gchristensen> when I rebuilt my home server, I didn't restore the old way I was building the aarch64 images -- thinking it'd be nice to set it up in a way where the SSH key used for testing the image was short lived. but in this case I should probably just start makig it work :)
* emily advertises #84522 to anyone interested in hardened NixOS
<{^_^}> https://github.com/NixOS/nixpkgs/pull/84522 (by emilazy, 5 minutes ago, open): linux_*_hardened: use linux-hardened patch set