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]
<flokli> Is there something still odd with the log viewer? https://logs.nix.ci/?key=nixos/nixpkgs.84136&attempt_id=451053b6-02c5-434c-8046-82c866f2cd0a still seems stuck at 'Subscribing to "nixos/nixpkgs.84136"...', and doesn't show other "tabs" (even though builds have run)
<MichaelRaskin> How old the build is?
<flokli> it is from #84136 as well. 3 hours ago?
<{^_^}> https://github.com/NixOS/nixpkgs/pull/84136 (by Izorkin, 2 days ago, open): nixos/tests: add check mariadb galera cluster
<MichaelRaskin> Indeed too soon.
<flokli> MichaelRaskin: hm?
<MichaelRaskin> Well, it is known that ofBorg logs have pretty short retention time, but not _that_ short
<MichaelRaskin> (It least not intentionally that short)
orivej has quit [Ping timeout: 256 seconds]
<gchristensen> hmmm
hmpffff has joined #nixos-borg
hmpffff has quit [Quit: nchrrrr…]
<gchristensen> flokli: https://logs.nix.ci/?key=nixos/nixpkgs.84136&attempt_id=451053b6-02c5-434c-8046-82c866f2cd0a
hmpffff has joined #nixos-borg
<flokli> sweet, it's back! thanks!
<gchristensen> =)
<gchristensen> thanks for reminding me it was behaving strangely
hmpffff has quit [Quit: nchrrrr…]
hmpffff has joined #nixos-borg
cole-h has joined #nixos-borg
<{^_^}> [ofborg] @cole-h opened pull request #450 → checkout: silence diffs when checking validity of a commit → https://git.io/JvN4C
hmpffff_ has joined #nixos-borg
hmpffff has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-borg
<{^_^}> [ofborg] @grahamc merged pull request #450 → checkout: silence diffs when checking validity of a commit → https://git.io/JvN4C
<{^_^}> [ofborg] @grahamc pushed 2 commits to released: https://git.io/JvNBl
<gchristensen> cole-h: deploying
* cole-h wishes the "Clear All" button only cleared the already-displayed logs instead of the query
<gchristensen> heh
<gchristensen> you should see the processes restart here in a second
<cole-h> I'm really confused. Last night, all the new log output was at the bottom. This morning, it's at the top???
<gchristensen> heh
<gchristensen> I think I know why live logs are busted
<gchristensen> cole-h: they should work now if you reload the page and try again
<cole-h> Woo!
<cole-h> Indeed it does.
<cole-h> <3 gchristensen
<{^_^}> gchristensen's karma got increased to 254
<gchristensen> hrm
<gchristensen> a lot of tasks end with a SendError unwrap panic and I'm not sure why
<gchristensen> see that?
<cole-h> Yeah, just did
<gchristensen> I've seen those come through before, today
<cole-h> I ran into that with my pass-rs project when handling events in the UI...
<cole-h> I believe it happens because a/the thread died between ticks (or, that was it in my case)
<LnL> gchristensen: about <nixpkgs> references, I remember talking about using -I plaesedontreferencethis=./nixpkgs in ofborg to make restric-eval happy but catch bad references
<LnL> but I don't think that was ever added
<gchristensen> oh that is a nice idea! right!
<{^_^}> [ofborg] @LnL7 opened pull request #451 → rename nixpkgs entry in NIX_PATH → https://git.io/JvNRr
<cole-h> gchristensen: Is it cool to make ofborg re-eval some of these PRs that have gone untagged for 7 hours?
<cole-h> eg #84341 and #84342
<{^_^}> https://github.com/NixOS/nixpkgs/pull/84341 (by Emantor, 6 hours ago, open): drm_info: 2.1.0 -> 2.2.0
<{^_^}> https://github.com/NixOS/nixpkgs/pull/84342 (by r-ryantm, 6 hours ago, open): distgen: 1.4 -> 1.5
<gchristensen> yep
<gchristensen> LnL: since you have a monitoring account, you can see logs now:
<gchristensen> https://monitoring.nix.ci/explore?orgId=1&left=%5B%22now-5m%22,%22now%22,%22Loki%22,%7B%22expr%22:%22%7Bjob%3D%5C%22systemd-journal%5C%22,%20unit%3D%5C%22ofborg-evaluator.service%5C%22%7D%20%22%7D,%7B%22mode%22:%22Logs%22%7D,%7B%22ui%22:%5Btrue,true,true,%22none%22%5D%7D%5D
<gchristensen> let me know if you see any API keys go by :x
<LnL> neat
<LnL> where does that come from? never had logs in grafana
<gchristensen> loki
<gchristensen> and promtail which follows journald
<gchristensen> all grafana projects
<gchristensen> hexa- got me set up :)
<LnL> ah cool
<LnL> happy with it so far?
<gchristensen> ehh maybe
<gchristensen> it has been set up for about 12 hours :)
<LnL> ah, a bit early then :p
<gchristensen> yeah :P
<gchristensen> I set it up because I think I tricked cole-h in to debugging ofborg problems :D
<cole-h> >:D
<gchristensen> LnL: should this be un-drafted? https://github.com/NixOS/ofborg/pull/451
<{^_^}> ofborg#451 (by LnL7, 54 minutes ago, open): rename nixpkgs entry in NIX_PATH
<LnL> yeah, had some test failures locally but looks like those where probably darwin things
<gchristensen> let's put it out and see :)
<{^_^}> [ofborg] @grahamc pushed 2 commits to released: https://git.io/JvNEn
<{^_^}> [ofborg] @grahamc merged pull request #451 → rename nixpkgs entry in NIX_PATH → https://git.io/JvNRr
<gchristensen> easy to revert
<cole-h> Certainly not tricked into it. Helps me help you :^) And it's not like there's much debugging to do... yet.
<LnL> I'd deploy this when you have time tho
<LnL> not 100% sure this won't break somewhere
<gchristensen> LnL: hm, it doesn't seem to have broken it like we thought: https://github.com/NixOS/nixpkgs/pull/84381
<{^_^}> #84381 (by grahamc, 20 minutes ago, open): Revert "k3s: fix https://hydra.nixos.org/build/116132269"
<LnL> hmm weird
<gchristensen> maybe I'll try re
<gchristensen> evaluating it just to be sure it got the new code
<cole-h> "No attempt
<cole-h> "
<LnL> oh yeah, the builds did fail
<gchristensen> file 'nixpkgs' was not found in the Nix search path (add it using $NIX_PATH or -I), at /var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/packet-spot-eval-3/pkgs/applications/networking/cluster/k3s/default.nix:1:13
<gchristensen> nice
<gchristensen> so then why it passed eval I'm not sure
<LnL> eval should also be going through safe_command from what I can tell
<gchristensen> aghhh
<gchristensen> String::from("--arg"),
<gchristensen> String::from("nixpkgs"),
<gchristensen> nixpkgs_arg_value.clone(),
<gchristensen> String::from("./nixos/release.nix"),
<gchristensen> ofborg/src/tasks/eval/nixpkgs.rs
<LnL> --arg != -I
<gchristensen> rightright
<gchristensen> hrm
<LnL> this still fails for example, NIX_PATH= nix-instantiate --eval -E '{ nixpkgs }: <nixpkgs>' --arg nixpkgs ./.
<gchristensen> good
<gchristensen> LnL: I'm thinking it should be nix-env which catches this error, no?
<LnL> yeah, as well as possibly the outpaths diff
<gchristensen> right
<LnL> and the tarball build, but that basically just runs that same nix-env query
<gchristensen> right
<gchristensen> gosh
<gchristensen> adding centralized logging has really emphasized how terrible the logging is
<LnL> hold on
<gchristensen> cool
<cole-h> New purple tag, but seems to be doing fine now: #84384
<{^_^}> https://github.com/NixOS/nixpkgs/pull/84384 (by euank, 25 minutes ago, open): k3s: remove extra buildInputs
<LnL> nope
WilliButz has quit [Remote host closed the connection]
WilliButz has joined #nixos-borg
<LnL> gchristensen: am I missing something? EvalChecker::execute -> Nix::safely -> Nix::safe_command
<gchristensen> no... that is what I saw too, seemed like it should work
<LnL> hmm, nix-env is doing some shenanigans
<LnL> huh nix-build doesn't fail either
<gchristensen> wat
<LnL> I can still build that
<gchristensen> wtf
<LnL> alltho the pr should still fail because it's missing variables
<LnL> lazy imports
hmpffff has joined #nixos-borg
hmpffff_ has quit [Ping timeout: 272 seconds]
<cole-h> Does ofborg trigger if I edit my comment in which I was telling ofborg to do something?
<gchristensen> yea
<cole-h> Welp
<cole-h> I guess I will not do that anymore lol
<gchristensen> I use it to test ofborg without people knowing it takes so many tries sometimes :P
<cole-h> Might've wasted a few cycles on the gtk3 build 🙊
<gchristensen> hehe
<cole-h> Which has a purple label, but I saw no problems in the log
<cole-h> At least, around the time it was labelled
<gchristensen> do you know how to search based on the message?
<cole-h> `{unit="ofborg-evaluator.service"} |= "ofborg-internal-error"` right?
<gchristensen> yeah, cool
hmpffff_ has joined #nixos-borg