<gchristensen>
a problem with longer builds is it takes AGES for ofborg to say it is building and the log streaming isn't very useful
<infinisil>
How about changing it so that it always outputs exactly 2 messages: first for saying "I'm building these", while reporting what doesn't evaluate because of arches. Second one returning all results
<gchristensen>
that is hard because there is no concept of "everything" that will be built
<gchristensen>
nothing is keeping track of what is being built beyond the builder
<infinisil>
I mean just the attrs you give it
<gchristensen>
yeah so it'd be 2 messages posted per arch
<infinisil>
Can't arches be combined?
<infinisil>
Oh I bet they run on totally different machines
<gchristensen>
that is hard because there is no concept of "everything" that will be built, and nothing is keeping track of what is being built beyond the builder :)
<infinisil>
Ah I see now
<infinisil>
Would be nice though, ofborg is quiet spammy, especially since I get an email for every message heh
<gchristensen>
I do too
<gchristensen>
probably better would be a web interface thing
<infinisil>
gchristensen: if you had something that keeps track of builds for the messages thing, you could also use that for somehing super fancy: report a time estimate in the first message of how long the build will take, by remembering the times for previous builds :O
<gchristensen>
yeah, I'd be +1 doing that as a nice-to-have but not sure I want that to be a central part of the tool
<gchristensen>
in other words, I don't want a service like that which coudl break everything if it fails
<infinisil>
Would be neat to have such time estimates be a nix builtin thing
<ekleog>
gchristensen: The initial “I'm building these” message could be sent straight away from the github-comment-filter agent to the github-comment-poster just after parsing the message, though? That'd make nb_arch + 1 messages, even though it wouldn't be possible to include in the initial message “This doesn't evaluate”
<ekleog>
Doesn't help for the spamminess, but does help for the “it takes AGES for ofborg to say it is building”
<gchristensen>
hmmmm!!!
<gchristensen>
and that could link to "logs'll be here y'all"
orivej has quit [Ping timeout: 264 seconds]
Mic92 has quit [Ping timeout: 245 seconds]
Mic92 has joined #nixos-borg
<gchristensen>
man, samueldr, the logger is adding new tabs like crazy
<samueldr>
LnL: it *feels* like there are camps for python vs. ruby
<samueldr>
and I also have read a TON of FUD against ruby
<samueldr>
like "ruby uses so much ram"
<samueldr>
when they conflated ruby and rails :/
<LnL>
and they start arguments about monkey patching without realising that python stuff actually does that much more
<samueldr>
(and for the record, while rails at rest takes up ram, it's hot ram, the app is ready to do stuff)
<LnL>
in the ruby community there's just a shame corner for it
<samueldr>
heh, monkey patching is generally frowned upon EXCEPT when the framework does it for you :)
<samueldr>
(kinda like ruby was half a language SDK)
<gchristensen>
oe
<samueldr>
gchristensen: this should fix the tabs duplicating issue
<samueldr>
though, to be fair, I never really took a seriour look at python, so I won't judge, I just have this visceral reaction agains languages where indentation matters
<samueldr>
(visceral and mostly unjustified)
<gchristensen>
samueldr: deployed!
<samueldr>
I both like and hate how dumb the fix is
<gchristensen>
:D
<samueldr>
I like how it means the viewer's design isn't broken beyond repair
<gchristensen>
yes
<samueldr>
I hate how the language's design is broken beyond repair