AlwaysLivid has quit [Remote host closed the connection]
AlwaysLivid has joined #nixos-dev
cole-h has quit [Ping timeout: 260 seconds]
evils has quit [Ping timeout: 240 seconds]
andi- has quit [Ping timeout: 248 seconds]
andi- has joined #nixos-dev
andi- has quit [Ping timeout: 246 seconds]
andi- has joined #nixos-dev
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #nixos-dev
rajivr has joined #nixos-dev
tomberek has joined #nixos-dev
<zhaofeng_alt>
Oops, misread and was assuming you were having problems with EC2 (was quickly glancing over the channels). Serial console on EC2 is huge!
orivej has quit [Ping timeout: 252 seconds]
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #nixos-dev
copumpkin has quit [Quit: Bye!]
copumpkin has joined #nixos-dev
cjb has quit []
evanjs has quit [Read error: Connection reset by peer]
<siraben>
supersandro2000: also means cache is getting colder and colder
<supersandro2000>
the jobs where canceled to get the openssl update out
<supersandro2000>
that was last weak, not current ones
<siraben>
yeah, hopefully we resume soon
<cole-h>
note the last 14 builds finished at "XXm ago" (15, 30, 35, etc)
<cole-h>
so likely unrelated to the openssl update
<cole-h>
or at least, not directly
<siraben>
what then? the interface is confusing
<cole-h>
yes, hydra's interface is confusing :) the only thing we can do is wait
<cole-h>
unless there's someone awake who can force eval nixpkgs-unstable
<cole-h>
(maybe samueldr?)
evils has joined #nixos-dev
<ma27[m]>
cole-h: I may be wrong, but isn't anybody able to evaluate a jobset if authenticated with e.g. a google account? Or is that not true for nixpkgs-unstable?
<cole-h>
the button may be there, but it's nonfunctional for those without permissions IIRC
<cole-h>
uh
<cole-h>
nevermind?
<cole-h>
maybe there's something different that needs to happen, but, uh, I re-evaluated nixpkgs:trunk :P
<ma27[m]>
we'll see I guess :)
NinjaTrappeur has quit [Ping timeout: 246 seconds]
NinjaTrappeur has joined #nixos-dev
capisce has quit [Remote host closed the connection]
capisce has joined #nixos-dev
cole-h has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-dev
<supersandro2000>
I just logged into hydra with my github account and I have the admin and restart-jobs role but I cannot restart anything
<supersandro2000>
bug in the UI?
orivej has joined #nixos-dev
<gchristensen>
mmm looking supersandro2000
<gchristensen>
supersandro2000: see DM
<gchristensen>
erm. ... PM. or do people still call it corner? :)
orivej has quit [Ping timeout: 268 seconds]
Baughn has quit [Ping timeout: 268 seconds]
<supersandro2000>
corner? I don't get that
<gchristensen>
I think that is very old IRC terminology
<siraben>
what's getting cornered
<gchristensen>
a private message
<siraben>
ah
<siraben>
interesting, haven't heard that before.
<siraben>
gchristensen: btw I think I pinged you about this before but, ofborg doesn't detect coqPackages rebuilds
<siraben>
I didn't see it both times I added a new coqPackage
<gchristensen>
is it marked as recurseIntoAttrs?
<siraben>
Unsure, haven't looked into the Coq infra that much
<gchristensen>
fwiw the bit about admin / restart-jobs was a confusion about how the UI presents the information in a not great way :)
boredom101 has joined #nixos-dev
<sterni>
siraben: it should for the default package set
<sterni>
siraben: but it is very strange I've observed something similar for ocamlPackages as well where the ofborg eval would not list all rebuilds that nixpkgs-review would come up with locally
boredom101 has quit [Quit: Connection closed]
orivej has joined #nixos-dev
evanjs has quit [Ping timeout: 260 seconds]
evanjs has joined #nixos-dev
evanjs has quit [Ping timeout: 260 seconds]
evanjs- has joined #nixos-dev
jonringer has joined #nixos-dev
mjlbach has quit [Ping timeout: 248 seconds]
mjlbach has joined #nixos-dev
jonringer has quit [Remote host closed the connection]
jonringer has joined #nixos-dev
<gchristensen>
samueldr: may I have your help testing hydra#677? I can send you a link to a ngrok thing
<hexa->
imo increase max-width on the container class
<hexa->
but I'm not sure if that is a sensible thing to do
<FRidh>
what is the motivation for a max_width of 1140px? relative lower resolution screens?
<FRidh>
hexa-: just what I was thinking )
<gchristensen>
1300px?
<FRidh>
or percentage?
<gchristensen>
this is above my paygrade
<FRidh>
although that could get inconvenient
<FRidh>
same
<hexa->
lmao
<gchristensen>
okay well it sounds like nobody found anything obviously wrong
<FRidh>
but yes 1300px looks good
<gchristensen>
cc samueldr
<FRidh>
the name dwarf-fortress-packages.dwarf-therapist-original.aarch64-linux doesn't fit though, but I guess there are more long names we should not bother with
<gchristensen>
I thought maybe it should overflow: ellipsis the name, but probably not a good idea
<gchristensen>
I updated the ngrok to have the logo like h.n.o
scott4 has joined #nixos-dev
scott has quit [Quit: Ping timeout (120 seconds)]
pinpox has quit [Quit: Ping timeout (120 seconds)]
scott4 is now known as scott
pinpox8 has joined #nixos-dev
__monty__ has joined #nixos-dev
MichaelRaskin has joined #nixos-dev
ris has joined #nixos-dev
<samueldr>
for frog's snacks
<samueldr>
the bikeshed is true!
<gchristensen>
oh?
<samueldr>
they are all bootstrap default
<samueldr>
and not even my implementation!
<samueldr>
(if I read correctly that this was about the bootstrap 4 thingy)
<gchristensen>
yeah
<gchristensen>
where is the bikeshed?
<samueldr>
navbar design, then the max width
<gchristensen>
oh
<gchristensen>
the navbar is in master already, so the container brought it back to current design
<FRidh>
yea ignore those things
<samueldr>
yeah, was just quickly glossing over the history :)
<FRidh>
can always be fixed up later
<gchristensen>
the max width I'm not fussed about, the display is weird already on master :)
<samueldr>
that was going to be my suggestion
<samueldr>
anyway since we're wreaking^W improving things there are other suggestions UX wise that would help using hydra that we could/should explore
<gchristensen>
yeah
<gchristensen>
for now I guess I'd like your blessing that this PR is good
<samueldr>
I was waiting for someone like you to check on it before going through it again
<gchristensen>
yeah, I checked :)
<gchristensen>
it looks good to me, a bunch of other people here also poked around
<samueldr>
I'll look and try to see what is missing compared to the current
<samueldr>
(if anything is missing)
<gchristensen>
cool
<gchristensen>
that ngrok URL should still be working
<samueldr>
I think my internet is on the slow path today
<samueldr>
github took a while to load too
<gchristensen>
ah
<samueldr>
oh no! found something on the exact page your ngrok link linked to, but something twhitehead couldn't have seen on their instance IIRC
<samueldr>
evaluation errors' background is not styled
<samueldr>
rnhmjoj: are those "trivial" rebuilds? mostly packing up perl?
<samueldr>
or are there expensive-in-time rebuilds?
<samueldr>
that's where the nuance lies in staging vs. master
<samueldr>
ah, a good hodge podge of misc. rebuilds, makes this harder to judge then
<rnhmjoj>
i'm not sure, that's why i'm asking. most are leaf packages, nixos utilities and then there's nix and dpkg which may trigger a lot of rebuilds
<gchristensen>
it should proooobably go to staging
<samueldr>
well, it totals *through all arches and platforms* only 1879 builds
<samueldr>
which is where it really is hard to gauge :)
mkaito has quit [Quit: WeeChat 3.1]
<rnhmjoj>
uhm, if there's doubt, i would just go through staging: it's not a critical update or anything like that
<samueldr>
yes
<samueldr>
that's the safe bet
<samueldr>
especially if it's only cleanup
rajivr has quit [Quit: Connection closed for inactivity]
pinpox8 is now known as pinpox
FRidh has quit [Quit: Konversation terminated!]
FRidh has joined #nixos-dev
<gchristensen>
I wonder if there is any way we could test it reasonably well without a VM, with just a regular perl test, and not actually verify it works with gittea -- while running the gittea server is an admirably impressive highlight of NixOS, I'm a bit skeptical about making "can run gittea" in the critical path of "is this PR good"
<ma27[m]>
you mean like intercepting the API call from the GiteaStatus Plugin and make some assertions against it?
<gchristensen>
yeah
<ma27[m]>
I guess it should be possible
<ma27[m]>
will give it a try when I have the time for that :)
<gchristensen>
it strikes me that all these notifier plugins all have like 50 lines of the same code and maybe that could be made library-ey
<ma27[m]>
I fully agree with it. I thnk I mentioned it somewhere that I mostly customized the stuff from the gitlab plugin which seems kinda copied from other things...
<gchristensen>
yeah
<ma27[m]>
I hate to say this, but I mainly did the copy approach because perl
<gchristensen>
of course, that is how I did my first several hydra prs
<gchristensen>
now I do TDD perl when I can because it is so much easier to know I'm not messing up scalar and list context
<ma27[m]>
not sure if I'm consider myself sufficiently qualified to bring in a reasonable improvement there atm
<ma27[m]>
ohh yeah, that's the most common thing I screw up almost every time ^^
<ma27[m]>
but even if we do that, I'd suggest to do this in a separate PR
<gchristensen>
yeah
<ma27[m]>
talking about Hydra, how should we proceed with https://github.com/NixOS/hydra/pull/743 btw? Or do you lack time to even look at it rn (I mean, that's totally understandable, that one is rather a beast and contains ma27-perl, so probably some weird stuff :p )
<{^_^}>
hydra#743 (by Ma27, 48 weeks ago, open): Add a filter for maintainers in the jobset-eval view
<gchristensen>
yeah ... I'm definitely a bit intimidated by it
<gchristensen>
it is time for me to dedicate chunks of time like that these days, since I'm either working or reviewing stuff in between home/family/baby things
<ma27[m]>
yeah no worries :) is there anything I can do atm to make it, well, less intimidating? :)
orivej has joined #nixos-dev
AlwaysLivid has joined #nixos-dev
FRidh has quit [Quit: Konversation terminated!]
AlwaysLivid has quit [Remote host closed the connection]
<abathur>
resholve's been a chicken/egg problem for me, lately; trying to work on some smaller tools that can compose up to fix some resholve-level problems, but then I want to resholve the tools...
<gchristensen>
hehehe
<abathur>
it vexes me
<abathur>
I am vexed
<gchristensen>
it is remarkable how I constantly, also, bump in to bootstrapping problems
<abathur>
I know I'm a glutton for punishment because I'm pondering whether I can hotwire resholve to rewrite sort -> @coreutils@/bin/sort :)
<abathur>
and then just pre-generate pre-bootstrapped nix copies for these
__monty__ has quit [Quit: leaving]
<MichaelRaskin>
I would create /tmp/resholve/@coreutils@ as a symlink, then add it to the start of $PATH, then sed the /tmp/resholve part out
<MichaelRaskin>
Of course, scaling to all packages would have a catch of going by derivation name, not by attribute name. But oh well
plumm has joined #nixos-dev
<plumm>
Hello, does anyone here build nix from source (on darwin?) I had to modify the build tree a bit, but I was able to get through autoconfigure, but now I get this "src/libexpr/parser.y:2.9-16: syntax error, unexpected identifier, expecting string"
tokudan has quit [Remote host closed the connection]
<supersandro2000>
arm64 or amd64?
<supersandro2000>
tests are broken on arm
<supersandro2000>
*amd64
tokudan has joined #nixos-dev
supersandro2000 has quit [Disconnected by services]