00:00
<
flokli >
some are hard-coded, some refer to the vars defined on the top
00:00
<
samueldr >
hmm, bad me
00:00
<
flokli >
nah, it's fine
00:01
<
flokli >
(I didn't change the colors in the two header bars yet)
00:01
<
infinisil >
flokli: But that's white text!
00:02
<
samueldr >
it's the vim theme I'm using :3
00:03
* samueldr
kinda dislikes solarized
00:03
<
infinisil >
Same samueldr
00:04
<
samueldr >
but eh, everyone has its faults :)
00:04
<
infinisil >
I used it for a while, but now I can't stand the colors anymore
00:04
<
samueldr >
from memory, it was "mathematically designed", which must mean "ugly"?
00:06
<
infinisil >
Hah, I'd rather have designers design stuff than mathematicians
00:11
<
samueldr >
instructions should work better
00:18
<
flokli >
thanks samueldr
00:21
<
samueldr >
thanks for caring and writing something :)
00:26
<
gchristensen >
<3 <3 <3
00:27
<
gchristensen >
I've found solarised to also be too low contrast. it was a cute hat trick that it was "perfect" in reverse and what-not, but .... eh...
00:27
<
gchristensen >
tbh my favorite color scheme is whatever emacs' default is
00:44
<
qyliss >
How should I tell if a build has failed or timed out? I see that sometimes there is a “build timed out” message in the GitHub checks UI, but there are builds that I think probably just timed out that don’t say that, and the logs aren’t much help either.
00:45
<
gchristensen >
link to an example?
00:49
<
qyliss >
Oh, wait, nm
00:49
<
qyliss >
I’ve been reading logs wrong
00:51
<
qyliss >
I had missed the “aborted” part
00:52
<
qyliss >
It’s not obvious from skimming, since it’s only about halfway down the file
00:52
<
gchristensen >
ah, yeah, it can be hard to find that
00:53
<
qyliss >
So many words for “failure”
00:53
<
qyliss >
“error”, “aborted”, …
03:12
orivej has quit [Ping timeout: 240 seconds]
08:03
orivej has joined #nixos-borg
13:04
<
LnL >
gchristensen: builder is back up, sorry for the delay
13:05
<
gchristensen >
no worries :)
13:05
<
gchristensen >
thank you!
14:10
<
tilpner >
Should ofborg request reviews from maintainers yet?
14:11
<
tilpner >
Or was that just the 11.by tag?
14:12
<
MichaelRaskin >
It mostly does already
14:14
<
{^_^} >
rfcs#39 (by grahamc, 1 week ago, open): RFC-0039: unprivileged maintainer team
14:16
<
tilpner >
So people who aren't part of the GH organisation can't be requested to review?
14:16
<
tilpner >
That would explain why it didn't work on this PR, thanks :)
14:19
<
gchristensen >
if you'd like to see the identified list, there is a check at the bottom with a Details link called "maintainers" or something
14:20
<
gchristensen >
click that, it'll show everything ofborg found
14:22
<
tilpner >
It was identified correctly, but couldn't request the review
14:22
<
gchristensen >
good
15:03
jtojnar has joined #nixos-borg
15:04
<
{^_^} >
#54615 (by jtojnar, 1 day ago, open): gtk3-x11: fix build
15:04
<
jtojnar >
it only picks up the two other packages
18:28
<
gchristensen >
never heard of that attrset
18:32
<
gchristensen >
jtojnar: must not recurseinto or something?
19:12
<
LnL >
yeah, only pythonPackages is recursed
20:04
{^_^} has quit [Remote host closed the connection]
20:04
gchristensen has quit [Quit: WeeChat 2.0]
20:05
{^_^} has joined #nixos-borg
20:07
gchristensen has joined #nixos-borg
21:51
MichaelRaskin has quit [Quit: MichaelRaskin]
23:55
orivej has quit [Ping timeout: 268 seconds]