yvanzo: are you back from holiday today or tomorrow?
lucifer[m]
bitmap: done
julian45[m]
zas: jermaine seems to be down… perhaps a hetzner mainboard replacement, or something else?
darkstardevx joined the channel
darkstardevx has quit
zas[m]
weird, it is shut off. No mainboard replacement on those
and no message from Hetzner
there was a temperature increase before it was shut down, perhaps a thermal issue. I'll try to restart it.
jermaine is back in the game, I found nothing interesting in logs, it looks like an hardware failure to me. If it happens again I'll get this server checked by Hetzner.
reosarevok[m]
lucifer: since yvanzo doesn't seem to be back yet, have you tested sir and the like using mb-docker yourself?
rn it still uses python 2.7 so I wanted to tell it to use my local image of sir instead (with my own change to test on top of 2to3)
But I'm not quite sure how to do that, since it seems by default it builds its own image based on a branch
Pokey has quit
Pokey joined the channel
mayhem[m]
lucifer: oops. we broke all the cron job monitoring for LB.
can you please add credentials for accessing the cron-sentry instance in LB?
petitminion joined the channel
lucifer[m]
[@reosarevok:chatbrainz.org](https://matrix.to/#/@reosarevok:chatbrainz.org) I had tested sir a month or two ago with the python 3 changes yes. I can do another test with the latest branch later today.
reosarevok[m]
It's not about you testing it, I wanted to test my PRs for sir and mb-solr locally
I can (I think) just easily change the MB_SOLR_VERSION in the Dockerfile to use my local image
But sir seems to clone branches and I'm not sure how to use a local branch/image
(also, I see the second commit updates only sir-dev to 3.11 but not sir, not sure if intentional)
bitmap[m]
<dvirtz[m]> "Do you know why? Does it have..." <- I should add "anytime soon," it just doesn't seem to be a priority for them
<reosarevok[m]> "(also, I see the second commit..." <- those should both use the same image
reosarevok[m]
Yeah, I thought so
I pushed an update for 3.13, hopefully it will make sense and work
_BrainzGit
[listenbrainz-server] 14amCap1712 opened pull request #3264 (03master…fix-cron-monitor): Add CRON_SENTRY_DSN to use self-hosted sentry for cron monitors https://github.com/metabrainz/listenbrainz-serv...
lucifer[m]
reosarevok: yes that sounds right.
do you still need to run a test with the latest sir py3 version?
* still need me to run, * py3 version or is that done already?
reosarevok[m]
I'm trying to do some stuff locally with schema change stuff which would semi-test it too, but a proper full test would make sense I guess if you have the time
mebious has left the channel
ansh[m] has quit
kellnerd[m] has quit
outsidecontext[m has quit
pite_ has quit
lucifer[m]
reosarevok: sure, ran a full test using the sir-py3 mb docker branch on trille.
Gautam_coder[m] has quit
reosarevok[m]
Thanks
pite joined the channel
m1gr has quit
lucifer: ping
RashapGoyal[m] has quit
lucifer[m]
reosarevok: pong
reosarevok[m]
Figured out in the meantime that docker was running the wrong image. Sigh.
lucifer[m]
👍️
dabeglavins9 joined the channel
dabeglavins has quit
dabeglavins9 is now known as dabeglavins
Kladky has quit
julian45[m]
<mayhem[m]> "(yes, this sounds sensical, I'..." <- just created a separate admin account for you. email from google with sign-in instructions should be coming your way shortly
in the meantime, i'll also DM you an authentik setup link shortly so that your regular rob@ account can be set up with SSO (after google admin roles are migrated away from rob@)
zas: same for you on the above two notes; DMs coming shortly
zas and mayhem : now that new google admin credentials (w/ admin roles assigned) and authentik invites have been issued, please let me know once you've completed setup; at that time, i'll add you two into the SSO testing group & remove google admin roles from your regular accounts
not an immediate need, but hoping to square this away within the next couple of days
zas[m]
I set it up, but cannot connect to G workspace (displayed in My applications), expected?
julian45[m]
<zas[m]> "I set it up, but cannot connect..." <- expected, but result of poor choice of action flow on my part. one sec
prep finished on my end. might take a bit for google settings to propagate, but you should be able to connect to zas@ with your authentik account now