gchristensen changed the topic of #nixos-borg to: https://www.patreon.com/ofborg https://monitoring.nix.ci/dashboard/db/ofborg?refresh=10s&orgId=1&from=now-1h&to=now "I get to skip reviewing the PHP code and just wait until it is rewritten in something sane, like POSIX shell. || https://logs.nix.samueldr.com/nixos-borg
tilpner has quit [Ping timeout: 256 seconds]
tilpner has joined #nixos-borg
hmpffff_ has joined #nixos-borg
hmpffff has quit [Ping timeout: 272 seconds]
hmpffff_ has quit [Quit: nchrrrr…]
cole-h has quit [Quit: Goodbye]
hmpffff has joined #nixos-borg
hmpffff_ has joined #nixos-borg
hmpffff has quit [Ping timeout: 256 seconds]
hmpffff has joined #nixos-borg
hmpffff_ has quit [Ping timeout: 260 seconds]
hmpffff has quit [Read error: Connection reset by peer]
hmpffff has joined #nixos-borg
hmpffff has quit [Quit: nchrrrr…]
sphalerite has quit [Quit: WeeChat 2.7.1]
cole-h has joined #nixos-borg
sphalerite has joined #nixos-borg
kalbasit has quit [Ping timeout: 256 seconds]
kalbasit has joined #nixos-borg
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-borg
hmpffff has joined #nixos-borg
<LnL> gchristensen: do you see that hydra event bus as an alternative for the analyzer queue or something separate?
<gchristensen> something else
<LnL> ah alright
<LnL> cause the metadata evaluation tracks different data unless hydra would be updated to also keep track of those
<gchristensen> I'm thinking a bunch of people would like to get various info about builds
<gchristensen> and thinsg like {^_^}'s channel tracker could monitor `tested` similarly
<LnL> oh right that also knows about channel updates
<gchristensen> yea
<gchristensen> and haven't you always wanted a constant stream of pushover events on every build start?
<gchristensen> you don't hav eto answer
<gchristensen> I know the answer is yes
<gchristensen> :P
<LnL> -_-
hmpffff has quit [Quit: nchrrrr…]
<gchristensen> mmhmm
<cole-h> What is this pushover stuff? Just notifications?
<gchristensen> pushover.net is how LnL and I get paged
<gchristensen> want to also get paged? :)
<cole-h> Oh boy, do I ever!
<gchristensen> lmao
<cole-h> (as sarcastic as that sounded, the answer is actually yes)
<LnL> about that, I think some of the alerts could probably do with a lover severity
<gchristensen> I think you're right
<gchristensen> btw I should give you an AWS account so you can run `nixops` commands on the ofborg repo
<gchristensen> cole-h: register for pushover.net, get the app for your phone, and send me your token :)
<gchristensen> LnL: FreeInodes4hAway
<gchristensen> LnL: FreeInodes4hAway
<gchristensen> LnL: FreeInodes4hAway
<gchristensen> LnL: FreeInodes4hAway
* gchristensen places phone in blender
<cole-h> looool
<LnL> rofl
<LnL> I was just typing "the aarch builder running out of disk space for example"
<gchristensen> lol
<gchristensen> LnL: when that happens on the aarch64 builder, it is because volth is cloning all the Android AOSP repos :|
<LnL> better to alert when the aarch builders get stuck
<LnL> or at least have that be the critical one and the other thing just a notification
<gchristensen> yeah
<gchristensen> I think it already even has a StalledBuilder alert configured?
<LnL> pretty sure yes
<gchristensen> so let's just kill that one?
<gchristensen> or
<gchristensen> cole-h: want to figure this out?
<gchristensen> :)
<cole-h> Currently in lecture... x)
<LnL> I'm fine with a regular one, those are silent for me unless a sound is set
<gchristensen> perfect time!
<LnL> btw pushover also works for znc notifications :)
<cole-h> lol
<gchristensen> oh cool
<gchristensen> good to know!
<cole-h> Good thing pushover's license is cheap
<cole-h> Can put that free Google money to good use
<gchristensen> yeah, pushover is great
<gchristensen> I have this snippet at the end of my script to, erm, back up, DVDs curl --form-string priority=1 --form-string "token=..." --form-string "user=..." --form-string "message=$(pwd)" https://api.pushover.net/1/messages.json
<cole-h> LnL: FreeInodes4hAway
<cole-h> x)
<gchristensen> okay, deploying the thing to add cole-h to pushover
<gchristensen> cole-h: that means we're going to need to let you deploy to prod, too
<cole-h> Sounds scary. I'm in.
<gchristensen> no good being paged if you can't do anything about it
<gchristensen> hrm.
<gchristensen> I'm going to mark this as a to-do item for this evening
<gchristensen> gotta finish up some work stuff :)
<cole-h> lol, sounds good. Gotta finish up some school stuff ;)
<cole-h> (I guess that means I should also install + learn nixops lol)
<gchristensen> andi- has been reminding me lately of "not you, team", so ... trying to stop
<LnL> oh, is the buildkite job gone?
* LnL hasn't touched ofborg in way too long
<gchristensen> LnL: it technically is moved to a different org, but I need to move it back to the ofborg org to match the "not you, team" mantra
<cole-h> I think it was moved to gh:ofborg/infrastructure
<cole-h> (Unrelated, that yellow dot bothers me even though I know it's because the deployment is technically ongoing)
<LnL> anybody else noticed ofborg builds are kind of slow?
<gchristensen> hrm, I haven't looked recently :x
<gchristensen> like, the builds in PRs?
<gchristensen> or `cargo build`?
<LnL> just incremental cargo build
<gchristensen> futures :(
<LnL> to be fair it's small, but my led project is faster with a clean build
<gchristensen> are you using futures? :)
<LnL> yeah...
<gchristensen> hm
<gchristensen> my experience has been that, like, tokio or something, makes everything painfully slow
<LnL> I mean yes for ofborg
<LnL> just changing lib.rs still takes 8s on released tho
<LnL> but that is about half :/
<gchristensen> ouch
<LnL> guess I shouldn't be surprised given how complicated async fn
hmpffff has joined #nixos-borg
<LnL> what do you think about something like this? https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html
<gchristensen> sounds good :)
<LnL> that does mean it's essentially a separate crate in the same repo
<gchristensen> yeah that seems okay to me
<gchristensen> are you not so sure?
<LnL> no, just means that you probably want to move to a bunch of separate lib / bin crates in the long term if you go this route
<gchristensen> yeah
<LnL> only concern was carnix, but seems like that should support it based on the changelog
hmpffff has quit [Quit: nchrrrr…]
<LnL> 14 -> 4
<gchristensen> seconds?
<LnL> yeah
<LnL> assuming no changes in the main lib ofcourse
<LnL> do you happen to know if async-std/futures-executor have an impact on this? or it it just the compiler
<gchristensen> hmm I really don't know
<LnL> "async/await with blazing fast compilation time"
<LnL> guess I should try it out
<gchristensen> fingers crossed?
<LnL> pretty much the same so I bet it's all the code generation behind async fn
<gchristensen> oof
andi- has quit [Ping timeout: 252 seconds]
andi- has joined #nixos-borg
orivej has quit [Ping timeout: 265 seconds]
andi- has quit [Excess Flood]
andi- has joined #nixos-borg