gchristensen changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS 19.09 is released! https://discourse.nixos.org/t/nixos-19-09-release/4306 | 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
edef has joined #nixos-dev
justanotheruser has quit [Ping timeout: 268 seconds]
edef has quit [Ping timeout: 260 seconds]
justanotheruser has joined #nixos-dev
justanotheruser has quit [Ping timeout: 260 seconds]
lovesegfault has joined #nixos-dev
<lovesegfault> I hate i686 so much
justanotheruser has joined #nixos-dev
edef has joined #nixos-dev
ixxie has quit [Ping timeout: 265 seconds]
yl has quit [Ping timeout: 268 seconds]
<{^_^}> firing: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
<gchristensen> new r13y report: https://r13y.com/
ris has quit [Ping timeout: 240 seconds]
<aanderse> gchristensen: nice, thanks for posting :D
<gchristensen> it is setup to go daily again
<aanderse> woo!
<lovesegfault> gchristensen: Is this normal? https://hydra.nixos.org/build/109483099
<lovesegfault> that long to send inputs
<gchristensen> no
<gchristensen> taking acre of it
<lovesegfault> thx, I could cancel in restart but I wasn't sure whether or not to
<lovesegfault> *and
<lovesegfault> gchristensen: I've seen that happen a few times, do you know/understand the cause?
<gchristensen> usually a deadlock bug
<lovesegfault> gchristensen: Within hydra?
<gchristensen> nix
<lovesegfault> I see
<gchristensen> trying to received lots of overlapping paths all at once
<gchristensen> I capture data each time it happens to try and narrow it down
<lovesegfault> Ah, nice
cptchaos83_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
Scriptkiddi has quit [Remote host closed the connection]
das_j has quit [Remote host closed the connection]
Scriptkiddi has joined #nixos-dev
das_j has joined #nixos-dev
orivej has joined #nixos-dev
<{^_^}> firing: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
orivej has quit [Ping timeout: 265 seconds]
zarel_ has joined #nixos-dev
zarel has quit [Ping timeout: 258 seconds]
drakonis has quit [Quit: WeeChat 2.7]
yl has joined #nixos-dev
yl has quit [Ping timeout: 258 seconds]
FRidh has joined #nixos-dev
orivej has joined #nixos-dev
<{^_^}> firing: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
ixxie has joined #nixos-dev
zarel_ is now known as zarel
lovesegfault has quit [Ping timeout: 248 seconds]
__monty__ has joined #nixos-dev
orivej has quit [Ping timeout: 265 seconds]
<{^_^}> firing: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
FRidh has quit [Quit: Konversation terminated!]
<{^_^}> resolved: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
ixxie has quit [Ping timeout: 260 seconds]
kenjis has joined #nixos-dev
ris has joined #nixos-dev
drakonis1 has joined #nixos-dev
orivej has joined #nixos-dev
misuzu has quit [Remote host closed the connection]
spacekookie has quit [Quit: **agressive swooshing**]
spacekookie has joined #nixos-dev
misuzu has joined #nixos-dev
tilpner_ has joined #nixos-dev
tilpner has quit [Ping timeout: 258 seconds]
tilpner_ is now known as tilpner
FRidh has joined #nixos-dev
Synthetica has joined #nixos-dev
orivej has quit [Ping timeout: 260 seconds]
drakonis1 has quit [Quit: WeeChat 2.7]
kenjis has quit [Remote host closed the connection]
kenjis has joined #nixos-dev
kenjis has quit [Ping timeout: 248 seconds]
orivej has joined #nixos-dev
FRidh has quit [Quit: Konversation terminated!]
tilpner has quit [Quit: tilpner]
tilpner has joined #nixos-dev
ixxie has joined #nixos-dev
drakonis has joined #nixos-dev
lovesegfault has joined #nixos-dev
<{^_^}> firing: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
<gchristensen> huh.
lovesegfault has quit [Quit: WeeChat 2.7]
<{^_^}> firing: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
<gchristensen> annoying
<gchristensen> seems a network blip, caused the jobs to fail, they remained failed for long enough just because of the regularity of the timer
<gchristensen> another recent cause was when nixos-unstable hadn't passed in about a week, and hydra was taking a Long Time to find the evaluation for the tested/latest URL.
<gchristensen> some testing shows a database migration we're thinking about running on Tuesday could reduce that query from a few seconds to like a few tens of miliseconds, and would fix that
<LnL> whoa nice :)
<gchristensen> the down side is the migration will take about 15 hours to run
lovesegfault has joined #nixos-dev
<{^_^}> resolved: ChannelUpdateStuck: https://status.nixos.org/prometheus/alerts
<LnL> needs to happen at some point...
<gchristensen> yeah
<__monty__> Another one of these migrations, gchristensen?
<gchristensen> the ones I was talking about in -chat was testing for the server swap on tuesday :)
<gchristensen> https://www.notion.so/grahamc/Database-Indexes-6d246851b1b0436eba09e1e00138358b are my notes from that experimentation
<LnL> you can configure the scrape duration for a target if it's expected to take a bit longer
<LnL> or is it the update itself
<gchristensen> the update itself
<gchristensen> LOG: duration: 738049.813 ms execute <unnamed>: SELECT ...
<lovesegfault> gchristensen: Woke up to a beautiful channel release, thanks for all the help :D
<gchristensen> :)
<lovesegfault> gchristensen: Do nar's have any compression?
<gchristensen> yes
<lovesegfault> Please don't say it's gzip
<gchristensen> I won't
* lovesegfault slams fists
<__monty__> I thought xz was nix's preferred compression?
<lovesegfault> I need to make an RFC to try and get all Nix's standard things on zstd
<tilpner> Ehh
<lovesegfault> it compresses about as well as xz but much faster
<tilpner> When Arch did that, their archives got larger
<tilpner> Which optimises for people with fast connections
<__monty__> Yeah xz is still the stronger compressor afaik.
<tilpner> But IME that's not really necessary, CPU usage of unpacking hasn't been a problem for me
<tilpner> And when I'm on a slow connection, every kB less helps
<lovesegfault> tilpner: It gets annoying on weak hw (rpi, etc)
<lovesegfault> Or even beefy hardware with weak cores (Aarch64 servers, etc)
<tilpner> I think any RFC should come with benchmarks for a few different scenarios
<gchristensen> definitely yes hard data
<lovesegfault> Yeah, I agree
<lovesegfault> I have a couple more days of vacation...
<__monty__> gchristensen: What are we looking at?
<tilpner> Including "the binary cache will cost $n more per month if this RFC is accepted"
<gchristensen> __monty__: compression ratio (bytes after compression / bytes before compression) and how many seconds-per-second are spent compressing data
<__monty__> Why does the compression ratio increase over the last hour?
<gchristensen> presumably different types of job results
<gchristensen> not sure about the variability
<__monty__> So about 2-3s are spent per second on compression. And the ratio is about 1/3?
<tilpner> zstds higher compression levels seem to beat xzs lowest compression level
<gchristensen> I guess so
<lovesegfault> tilpner: How much does the binary cache cost now? Is it S3?
<tilpner> lovesegfault: AFAIK yes to S3, paid by sponsoring companies
<tilpner> But I don't know very far
<tilpner> That goes for monthly storage as well as bandwidth via Fastly
<tilpner> I'm not saying you need to find these numbers, just that they need be determined before any decision is made
<lovesegfault> Yeah, I agree with you
<lovesegfault> gchristensen: Do you still have that incantation to track Python 2 dependencies handy?
<gchristensen> I'd have to dig through my twitter :P
<lovesegfault> gchristensen: I'll do it then, I think I rt'd it
<lovesegfault> nix-store -qR /run/current-system | grep python2 | xargs -n1 nix why-depends -a /run/current-system
<lovesegfault> boom
<tilpner> So, uhh, who of you would expect the position of the "verbose" flag to matter in Nix?
<tilpner> E.g. nix -vv --version vs nix --version -vv
<lovesegfault> oh god
<gchristensen> please file a bug :)
<tilpner> Well, I first wanted to make sure that's not generally accepted weirdness
<LnL> for version/help I can imagine it depends
<LnL> since those flags exit immediately
<__monty__> Position-dependent flags are terrible, like gpg's --expert.
lovesegfault has quit [Quit: WeeChat 2.7]
Cale has quit [Ping timeout: 260 seconds]
<infinisil> __monty__: Yes!
<infinisil> This --expert flag screwed me over once too
<__monty__> Yeah, I don't know why they made a complex tool harder to use.
__monty__ has quit [Quit: leaving]
Cale has joined #nixos-dev
<gchristensen> once the cast is made it can be very difficult to break out
<jtojnar> the udisks2 r13y bug looks like https://sourceforge.net/p/docbook/bugs/1385/, gtk-doc has been already setting generate.consistent.ids for a long time
<gchristensen> nice
<gchristensen> annoying, but nice
drakonis has quit [Quit: WeeChat 2.7]
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-dev
lovesegfault has joined #nixos-dev
drakonis has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
Synthetica has quit [Quit: Connection closed for inactivity]
drakonis has quit [Ping timeout: 260 seconds]