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
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-borg
cole-h__ has joined #nixos-borg
cole-h has quit [Ping timeout: 256 seconds]
cole-h__ has quit [Quit: Goodbye]
cole-h has joined #nixos-borg
orivej_ has quit [Ping timeout: 240 seconds]
cole-h__ has joined #nixos-borg
cole-h has quit [Ping timeout: 256 seconds]
cole-h__ has quit [Quit: Goodbye]
cole-h has joined #nixos-borg
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-borg
<gchristensen> Last successful build 2019-08-20 08:03:28
<{^_^}> [ofborg] @grahamc pushed to released « import the overlay in one more place »: https://git.io/Jfzz9
<{^_^}> [ofborg] @grahamc pushed to released « Pepper in allowing old openssl »: https://git.io/Jfzgc
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-borg
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-borg
evanjs has quit [Quit: ZNC 1.8.0 - https://znc.in]
evanjs has joined #nixos-borg
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-borg
<gchristensen> w00t aarch64 box is running an updated ofborg
<cole-h_> :D
* cole-h_ can't wait until that "allow old openssl" commit can be undone treewide
<gchristensen> :)
<cole-h_> After this week I should be able to start hacking on borg again. NixOS is mostly set up :D
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 260 seconds]
orivej_ has joined #nixos-borg
cole-h has quit [Quit: Goodbye]
orivej_ has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-borg
cole-h_ has quit [Quit: Goodbye]
hmpffff has joined #nixos-borg
hmpffff_ has joined #nixos-borg
hmpffff has quit [Ping timeout: 272 seconds]
hmpffff has joined #nixos-borg
hmpffff_ has quit [Ping timeout: 256 seconds]
hmpffff has quit [Ping timeout: 260 seconds]
hmpffff has joined #nixos-borg
hmpffff__ has joined #nixos-borg
hmpffff has quit [Ping timeout: 246 seconds]
hmpffff has joined #nixos-borg
hmpffff__ has quit [Ping timeout: 256 seconds]
hmpffff_ has joined #nixos-borg
hmpffff has quit [Ping timeout: 272 seconds]
hmpffff_ has quit [Ping timeout: 256 seconds]
hmpffff has joined #nixos-borg
orivej has quit [Ping timeout: 256 seconds]
orivej_ has joined #nixos-borg
<MichaelRaskin> Ouch. libarchive is broken which breaks all ofBorg evals…
orivej_ has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-borg
hmpffff has quit [Ping timeout: 258 seconds]
hmpffff has joined #nixos-borg
hmpffff_ has joined #nixos-borg
hmpffff has quit [Ping timeout: 260 seconds]
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
<LnL> why is libarchive broken?
orivej_ has joined #nixos-borg
hmpffff_ has quit [Ping timeout: 258 seconds]
orivej has quit [Ping timeout: 256 seconds]
<MichaelRaskin> Hmm, Hydra thinks otherwise
<{^_^}> nixpkgs#88266 (by r-ryantm, 1 hour ago, open): btrfs-progs: 5.6 -> 5.6.1
<LnL> ah staging, builds aren't going to work there in most cases
orivej_ has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-borg
<MichaelRaskin> Wait, does it build _staging_ Nix for _eval_ of PRs to staging?
<LnL> libs as a build not an eval
<MichaelRaskin> Hmm. So Nix from staging
<LnL> there's a pr to not use the target nixpkgs, but I don't really like the idea of using a random nixpkgs from the deployment
<MichaelRaskin> Hm. So Nix broken on staging is now red-cross-mark worth problem.
<LnL> running builds in the evaluator is also a problem, but that's another way of looking at it yes
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 256 seconds]
hmpffff has joined #nixos-borg
hmpffff has quit [Client Quit]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 265 seconds]
orivej_ has joined #nixos-borg
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
orivej has quit [Read error: Connection reset by peer]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 256 seconds]
orivej_ has joined #nixos-borg
orivej_ has quit [Ping timeout: 260 seconds]
hmpffff has joined #nixos-borg
cole-h has joined #nixos-borg
evanjs has quit [Quit: ZNC 1.8.0 - https://znc.in]
evanjs has joined #nixos-borg
orivej has joined #nixos-borg
<cole-h> gchristensen: After I merge the README later today (hopefully), your only job is to change the description of the repo "@GrahamcOfBorg tooling automatio" -> "@ofborg tooling automation" :D (Since IIRC LnL has w+ to infra, we can do that part without you)
<gchristensen> w0000t!
<gchristensen> <3 <3 <3
<LnL> great :)
<cole-h> "Oh yeah, it's all coming together."
<gchristensen> also big thanks to andi- for getting the openssl 1.0.2u PR in to ofborg months ago, it made yesterday's late-night fixing of hydra much less miserable
<cole-h> <3 andi-
<{^_^}> andi- was put on Santa's "nice" list
<cole-h> :D
<LnL> oh, what happened?
<cole-h> ofborg#436 I believe
<{^_^}> https://github.com/NixOS/ofborg/pull/436 (by andir, 12 weeks ago, merged): Update to current nixpkgs-unstable
<gchristensen> ofborg hasn't been able to build in hydra since like August, because hydra provides its own nixpkgs
<LnL> ah the hydra builds, yeah I... noticed something was wrong there quite some time ago
<gchristensen> :)
<gchristensen> yeah, so the community builder build picks the latest successful build by hydra
<LnL> didn't realise it was used by something
<cole-h> Same :D I was messing around with Hydra and saw we had a jobset (?), clicked it, and saw "2019" and noped right out LOL
<cole-h> "That's something I'll deal with later, if Graham doesn't beat me to it."
<LnL> I see, no wonder it was a bit old :D
<gchristensen> :P
* cole-h just pulled up the dashboard
<cole-h> 28 online versions @ 0.1.9 :D
<gchristensen> w00t
<gchristensen> *knock on wood* it'll auto build and deploy each week
<gchristensen> I could give y'all access to push the "build and deploy" button, though
<cole-h> I was about to say, I can see it (and the "New Build" button) already :D
<cole-h> "..???" lmao
<gchristensen> that button is safe to press any time. it builds a new image, erases, and reboots the community box. it runs weekly, and typically if I run it any other time I drop a note in #nixos-aarch64 -- but it isn't required and the expectation is firmly "this box is transient"
<cole-h> Another channel for me to join :D
<gchristensen> ^ I added that text to the project description under the header on https://buildkite.com/grahamc/nix-community-aarch64-build-box/builds/149
<cole-h> 👍
<cole-h> Something I just noticed on the dashboard: only core-0 and aarch64 show up on inodes + disk free graphs
<LnL> shouldn't really need it, with the builders updated they should be reconnecting properly now
<gchristensen> yeah
<gchristensen> but maybe you want to push out a fix
<cole-h> 🤞
<LnL> yeah, still useful for some specific cases but it's generally better to handle versions properly if it's not too problematic
<cole-h> +1. I've been thinking about working on a changelog eventually. Might be nice to see some of the problems addressed between releases, even if it's only really useful to those of us intimately involved
<gchristensen> I know someone else who runs ofborg X_X
<gchristensen> but don't do any work with that in mind.
<cole-h> ?
<gchristensen> I know somebody who runs a private ofborg
<LnL> oh that actually happened?
<gchristensen> hah, yeah
<gchristensen> but I pretend that is not true, and I specifically *don't* want that to influence how we develop or work on ofborg
<LnL> was referring more to the versioned messages, etc.
<gchristensen> ah
<LnL> btw, do we need to find another victim to run a darwin builder?
<gchristensen> oh, on that note, I know of one which we can use
<cole-h> Suhweet!
<gchristensen> but have not had the time to set it up :/
<LnL> ah ok
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-borg
<andi-> How happy are you with the git checkout performance of ofBorg? With broken.sh I am seeing it (as of now) as the primary time waste :/
<gchristensen> it is slow :)
<andi-> My current idea is `git -C $checkout archive --format=tar $rev | tar ...` in a tempdir
<andi-> that might be faster
<andi-> and to disable the annoying auto gc
<gchristensen> oh yeah that causes a lot of problems for my builders, eventually they get completely wedged. I've considered forcing a GC every day or something
orivej has quit [Quit: No Ping reply in 180 seconds.]
<LnL> I've wondered if worktrees would help a bit here
<LnL> ah it uses git clone --shared, not sure if there's a big difference then
<gchristensen> all that is not really used anymore, since it always reuses the same direcotry I think
<LnL> not sure there's actually much point to using git other than for the target branch
<andi-> I actually think worktrees aren't that much of an impreovement over --reference with hardlinks as it is currently used
<LnL> creates lots of temporary commits that are only referenced/used once
<andi-> Yeah
<LnL> git fetch ; git clean -fd ; git checkout ; patch
<andi-> I did get ~20min improvement out of a 4h run by just putting the GIT clone on a tmpfs
<andi-> Not as much as I hoped.. It was a pretty fast NVMe disk already
<andi-> the problem with reusing the same git dir is that you can only run one job at a time
<LnL> not really an issue for the evaluators
<LnL> but why not use a pool? only thing that locks if you share space is the fetch
<andi-> maybe, I'll play a bit with that idea.
<cole-h> LnL: OK, I'm ready to get the README stuff in. Got a second to merge the related infra PR?
<LnL> sure
<{^_^}> [ofborg] @cole-h merged pull request #482 → "Not you: team." (Rework README) → https://git.io/JfZFs
<{^_^}> [ofborg] @cole-h pushed 3 commits to released: https://git.io/Jfgmq
<{^_^}> ofborg/infrastructure#21 (by cole-h, 2 weeks ago, open): Remove {extra-,}known-users
<LnL> ah that one, forgot about it
<cole-h> :D
<cole-h> All done!
<cole-h> gchristensen: Now it's your turn! s/@GrahamcOfBorg/@ofborg/ in the description :D
<cole-h> LnL: All 16 aarch builders came back up. Woohoo! Good work on that stuck-queue issue 🎉
<gchristensen> done!
<gchristensen> wooo!
<cole-h> <3 gchristensen <3 LnL
<{^_^}> LnL's karma got increased to 54
<{^_^}> gchristensen's karma got increased to 300.9999999999998
<cole-h> 👀
<gchristensen> <3 cole-h <3 LnL :)
<{^_^}> LnL's karma got increased to 55
<{^_^}> cole-h's karma got increased to 56
<cole-h> OK, now back to fiddling with my NixOS setup x)
<LnL> so, guess I'll tackle the evaluator services next?
<gchristensen> yass
<cole-h> Also, if it isn't too much to ask (or too dangerous), I'd like to try and get ofborg/infrastructure#20 in for the next deploy, whenever that is
<{^_^}> https://github.com/ofborg/infrastructure/pull/20 (by cole-h, 2 weeks ago, open): No more warnings
<LnL> how about now?
<gchristensen> y'all are doing great, keep it up, y'all don't need me ):
<gchristensen> y'all are doing great, keep it up, y'all don't need me :)
<cole-h> lol, works for me haha
<andi-> the old PHP stuff is now gone from the README but is it still part of the entire setup? ;)
<LnL> yep, no changing the topic! :p
<cole-h> The stuff that was removed is part of the infra repo
<gchristensen> andi-: at this point I'm opposed to removing the PHP just on principle :P
<andi-> We shoudl probably try to get along without gchristensen for a month just to test drive things ;)
<gchristensen> I'm happy to fall away
<gchristensen> I mean, tbh, other than the little fix up last night I haven't even really reviewed the PRs
<cole-h> Heh
<gchristensen> andi-: I should probably write a discourse thing about s/me/team/g
<cole-h> I think it's kinda funny that GH shows me more context in an email than in the actual review/comment on a PR
<cole-h> gchristensen: Careful with that, you might change "meme" into "teamteam".
<gchristensen> that would be a truly clbuttic mistake
<andi-> gchristensen: I think that would be a great idea. Maybe that could be an inspiration for other parts of the project.
<cole-h> Oh no
<cole-h> "a bytes-like object is required, not 'str'"
<gchristensen> ooo?
<gchristensen> hey what are you running
<LnL> hmm, python?
<cole-h> :(
<cole-h> And here I thought I could get away with s/string/str/
<LnL> looks like you found a nixops python3 bug
<cole-h> Also real cool how it tells me nothing :D
<gchristensen> jikes
<LnL> also what is the hetzner host doing there?
<gchristensen> I can't look right now (I'm trying, andi-!)
<andi-> Can't see that page :'(
<gchristensen> andi-: fears around API keys :(
<gchristensen> andi-: I'll add you though, do you have a buildkite account already?
<cole-h> LnL: Good catch
<andi-> No I haven't really felt the need for it
<andi-> they don't do oauth, do they?
<LnL> "resource ‘builder-0’ is obsolete"
<gchristensen> I'd love to add you if you're willing :P
<LnL> yeah it's been gone for like a month
<andi-> nor IPv6 :'(
* andi- sighs and signs up
<LnL> oh no all of them
<cole-h> I guess that PR was dangerous x)
<cole-h> Gonna try dry-activate once more... maybe (hopefully) just random chance?
<cole-h> nope
<cole-h> Wait, different error lol
<cole-h> "KeyError: 'PACKET_ACCESS_KEY'"
<LnL> other builds have the same obsolete messages so yeah guess it's packet/api related
<gchristensen> hmmm
<cole-h> Which other builds?
<LnL> gchristensen: make that an intervention yesterday and today I guess :)
<cole-h> x(
<gchristensen> hah right
<LnL> cole-h: you previous deploy
<gchristensen> adisbladis, LnL, samueldr, andi- (you haven't accepted yet, so I don't know if you did yet or not) please configure 2fa on your buildkite accounts
<LnL> your*
<cole-h> LnL: Ah
<cole-h> One more try, see if I can get a third different error, and then I go get breakfast (at 11am lol)
<cole-h> Nope, same error this time -- PACKET_ACCESS_KEY. OK, brb like 20 minutes probably
<gchristensen> hrm
<LnL> sounds like vault isn't getting the secret anymore or something
orivej has joined #nixos-borg
<gchristensen> it isn't using a --pure shell is it :X
<cole-h> lol
<gchristensen> I was hitting a problem with that for some time yesterday
<cole-h> I don't think so considering it worked not half an hour ago...
<cole-h> s/half//
<gchristensen> heh
<gchristensen> will look at logs shortly
<cole-h> `rg -- --pure` doesn't turn up anything
<LnL> yeah #!nix-shell -i bash ../shell.nix
<LnL> unless that runs in another shell
<gchristensen> guh, I need to figure out how to make `journalctl -f -u` tab-completion not take literal minutes
<cole-h> andi-: Looks like we wouldn't have even made it a day without gchristensen if we had tried that month idea this month... :D
<gchristensen> :(
<gchristensen> expanding "🔑 Authenticating with Vault" I see
<gchristensen> # PACKET_ACCESS_KEY changed
<gchristensen> where?
<cole-h> "🔑 Authenticating with Vault" of my most recent try
<cole-h> dry activate try, that is
<gchristensen> heh.
<gchristensen> * err 'POST https://api.packet.net/projects/86d5d066-b891-4608-af55-a481aa2c0094/api-keys: 404 ' when attempting to create API key in Packet
<gchristensen> oohhhhkayyyyy
<cole-h> Yep
<cole-h> (Didn't want to post in case that was sensitive, but I saw that too... lol)
<cole-h> Oh hey
<gchristensen> yup.
<cole-h> Yep lol
<gchristensen> didn't need me after all! good digging
<cole-h> :D
<LnL> oh!
* cole-h bookmarks packet status and buildkite status for future reference
<LnL> hmm, does that have an api?
<gchristensen> good question
<cole-h> If statuspage has an API, yes, probably
<cole-h> Wow their search on `developer.statuspage.io` is soooooooo bad
<cole-h> I type "incidents" and it goes to "inced", then "incedent" then "indecens" lol
<cole-h> (Ignore the typo)
<{^_^}> packethost/packet-python#45 (by grahamc, 1 year ago, open): When the API is super down, the API client behaves poorly
<cole-h> "super down" nice
<cole-h> We'll see if you actually weren't needed after this API issue is resolved... That 'str' error from the first run still seems strange (though may have been due to the API weirdness since the mentions `ssh_key_id` in the trace)
<cole-h> Oh
<gchristensen> it is because their API just returns like "503 Backend Fetch Failed" or something as a bytes thing
<cole-h> Wait I didn't actually read that issue you linked lol
<gchristensen> like, it has to be incredibly broken
<cole-h> Derp
hmpffff has quit [Quit: nchrrrr…]
<gchristensen> oh, b'Forbidden\n'
<cole-h> OK, so 99% chance it'll be fine once Packet recovers
<andi-> super down and incredibly broken. Exciting times :)
<LnL> :D
<gchristensen> lol
* cole-h installs an auto-refresh addon just for status.packet.com
<LnL> wait the status api requires oauth!?
<gchristensen> it is probably intended for writing :(
<cole-h> Yeah, I tried GETing it and also got rejected for no auth token :D
<LnL> this is probably good enough https://status.packet.com/api/v2/status.json
<gchristensen> nice
<cole-h> Oh nice
<gchristensen> oops
<gchristensen> a fix has been implemented
<cole-h> Retry!
<cole-h> Another failure :D
<gchristensen> summary of the failure?
<cole-h> nix-build failed
<cole-h> "unable to build all machine configurations"
<cole-h> And hetzner is still showing up as obsolete for some reason
<gchristensen> we don't have those machines anymore
<cole-h> Right, so why is it showing up?
<gchristensen> it is still in the state file, since it hasn't been deleted with, say, `nixops deploy -k`
<cole-h> Ah
<cole-h> Oh hey I'm blind
<cole-h> "attribute 'services' missing"
<cole-h> Guess I can't do that
<LnL> ah no I think you mixed up overlays with nixos modules
<cole-h> Now the question becomes: how do I get `config.services.phpfpm.pools.main.socket` there?
<LnL> well it's just a function so add an arument? :)
<cole-h> Grr, you and your logic
<cole-h> I'm too lazy to turn off my nixpkgs-fmt, so you'll have to deal with the large diff when I send this PR in...
<cole-h> JK I'll turn it off...
<gchristensen> I mean
<gchristensen> send it
<gchristensen> just make sure the reformat is in its own, isolated, commit
<cole-h> Fair.
<gchristensen> and ideally add a check for it being nicely formatted to CI
hmpffff has joined #nixos-borg
<cole-h> That'll go on my TODO list. I'd like to unblock this deploy ASAP :P
<gchristensen> thanks :)
<{^_^}> ofborg/infrastructure#23 (by cole-h, 9 seconds ago, open): nginxVhostPHP: add socket argument
<cole-h> Do I have to make a new build for that to work, or will a retry see this new commit?
<cole-h> New build it seems.
<cole-h> Yay :D
<cole-h> I don't see anything obviously broken, so I think it's safe to celebrate: no more red messages (aside from nixops's color coded fanciness) in deploys!! 🎉 :D
<gchristensen> w00t!
<gchristensen> does the webhook still work? :)
<cole-h> How to check? x)
<gchristensen> ask for an eval via a comment
<gchristensen> or open a PR
<cole-h> :(
<gchristensen> hm?
<gchristensen> check the nginx and php-fpm etc. logs on core-0
<cole-h> phpfpm-main looks good, nginx seems OK (ExecutionFailureExceptions were seen since before the deploy)
<cole-h> nvm, just got nginx log
<gchristensen> hehe sorted it
<gchristensen> "@ofborg eval morestuffhere" doesn't work
<cole-h> Oh
<cole-h> lmao
<cole-h> I forgot
<cole-h> Derp.
<cole-h> Man, those are a few stressful minutes I won't be getting back... :P
<gchristensen> :)
<cole-h> But I love it
<cole-h> This is so much fun
<cole-h> Open source is fantastic
<cole-h> ...crap. I misspelled my funny message: https://i.imgur.com/b72AAny.png :(
<gchristensen> lmao
<cole-h> "boogaloot"
<cole-h> ,loot <-- just reminded me of this
<{^_^}> <-- just reminded me of this: [2018-05-26 20:24:58] <gchristensen> 25 points gets you a sticker, 100 points gets you a t-shirt, 1000 verified points gets you a free trip to nixcon *restrictions apply, must be verifiable points, given by grateful people, in channels I'm in
<cole-h> ~40 more points and that tee is mine >:)
<gchristensen> ohno
<LnL> hehe
<cole-h> LnL: You better step up your game -- I might get that shirt before you do ;^)
<gchristensen> LnL gets a shirt as soon as they arrive regardless :)
<gchristensen> I owe LnL so many beers
<cole-h> Darn. I better step my game up, so we get the shirt at roughly the same time, then :P
<LnL> gchristensen: right back at you :)
<andi-> <3 cole-h thanks for all your work on ofborg (been reading all those notification mails about it ;))
<{^_^}> cole-h's karma got increased to 57
<cole-h> Thanks for indirectly giving me the title to that README PR :P
<cole-h> (Before I submitted it I had to grep my logs for the actual phrase)
<gchristensen> +1
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-borg
* LnL is slightly confused
<LnL> ofborg doesn't use the prometheus library?
<gchristensen> heh
<gchristensen> blow it all up
<gchristensen> the metrics collection is full of lies
<LnL> lol, don't follow
* andi- notes down "our CI is lying"
<cole-h> Wait wait you can't do that, you signed an NDA by joining this channel
<cole-h> :P
<gchristensen> the metrics collection is really bad and half-done
<cole-h> (Also, stats collector seems dead again. See: checks completed chart empty)
<gchristensen> instead of sending metrics over rmq and using the stats collector, prom should just scrape the machines
<LnL> oh so those are the only metrics?
evanjs has quit [Quit: ZNC 1.8.0 - https://znc.in]
evanjs has joined #nixos-borg
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
orivej has quit [Read error: Connection reset by peer]
orivej_ has joined #nixos-borg
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
<LnL> hyper was more annoying than I was expecting
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
<{^_^}> [ofborg] @LnL7 opened pull request #489 → packet exporter → https://git.io/Jfgn7
<LnL> hyper doesn't really seem to be the way to go without tokio however so should probably look into one of the other libs
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 264 seconds]
orivej_ has joined #nixos-borg
orivej_ has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-borg
hmpffff has quit [Quit: Bye…]
orivej has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-borg
<LnL> stats got stuck again and looks like updating it still needs a bit of refactoring
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
<gchristensen> IMO just delete it
<gchristensen> :|
<cole-h> RiiR :P
<cole-h> Even though it's already in Rust
<gchristensen> the numebrs were almost literally never right, anyway
orivej_ has joined #nixos-borg
orivej has quit [Ping timeout: 246 seconds]
orivej_ has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-borg
<LnL> since this is currently all macro stuff, do you have a list of metrics that currently exposes?
<LnL> or is it just the ofborg_* namespaced stuff
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-borg
orivej has quit [Read error: Connection reset by peer]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-borg
<gchristensen> LnL: just the ofborg_* stuff
<{^_^}> [ofborg] @zowoq opened pull request #490 → config.public.json: add zowoq to trusted users for darwin access → https://git.io/Jfglx
cole-h has quit [Quit: Goodbye]
orivej has quit [Quit: No Ping reply in 180 seconds.]
cole-h has joined #nixos-borg
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 265 seconds]
orivej_ has joined #nixos-borg