(just skipping the now dupe commit should be fine)
2023-08-01 21359, 2023
reosarevok
bitmap: what are the plans for release editor reactification?
2023-08-01 21327, 2023
reosarevok
It would be nice to implement something like MBS-13200 but it might be worth waiting for it if it / alternative tracklists in React are coming soon rather than doing the work twice
mayhem: For the form event, there is a gotcha I forgot that makes typescript unhappy. it should be: `const form = event.currentTarget;` instead of `const form = event.target;`
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | BookBrainz: #bookbrainz | Channel is logged; see https://musicbrainz.org/doc/IRC for details | Agenda: Reviews
2023-08-01 21306, 2023
reosarevok
zas: what time was this server update today?
2023-08-01 21343, 2023
mayhem
in 1 hour and 17 minutes.
2023-08-01 21329, 2023
reosarevok
Ok, when is the announcement happening? on the hour?
2023-08-01 21305, 2023
mayhem
I suggested that we take the first hour and tweet and then prep all of our stuff. ideally finish before the end of the first hour, then wait until the top of the hour.
2023-08-01 21318, 2023
mayhem
16:00UTC. then start the update.
2023-08-01 21344, 2023
mayhem
anyone with some react knowledge available to help me with (hopefully) a quick question?
2023-08-01 21347, 2023
mayhem
lucifer, akshaaatt ?
2023-08-01 21341, 2023
akshaaatt
Sure mayhem. Ask
2023-08-01 21314, 2023
mayhem
thx
2023-08-01 21304, 2023
mayhem
in the template for serving a react page there is this block:
lucifer: is that a specific config you did recently on spark servers?
2023-08-01 21310, 2023
lucifer
zas: nope it predates ansible.
2023-08-01 21331, 2023
lucifer
that repo needs to be replaced with a newer one.
2023-08-01 21342, 2023
zas
ok, so I guess you can fix it, but we'll have to manage this with ansible later
2023-08-01 21359, 2023
bitmap
zas: hip ready
2023-08-01 21308, 2023
zas
ok, rebooting hip
2023-08-01 21345, 2023
zas
bitmap: I'll do moroder too, that's mainly metrics / alerts server, so users shouldn't be impacted
2023-08-01 21306, 2023
bitmap
👍
2023-08-01 21320, 2023
zas
let's wait for hip to come back first
2023-08-01 21333, 2023
zas
hip is back
2023-08-01 21307, 2023
zas
rebooting moroder
2023-08-01 21308, 2023
zas
bitmap: can we reboot sentry next?
2023-08-01 21304, 2023
zas
moroder is back
2023-08-01 21305, 2023
zas
reosarevok: can you tweet about downtime?
2023-08-01 21310, 2023
bitmap
sure, I guess sentry is on the cloud?
2023-08-01 21312, 2023
reosarevok
I can!
2023-08-01 21319, 2023
reosarevok
How long, and starting when?
2023-08-01 21322, 2023
reosarevok
On the hour, right?
2023-08-01 21326, 2023
bitmap
zas: you can reboot ludwig too
2023-08-01 21331, 2023
zas
reosarevok: yup
2023-08-01 21356, 2023
mayhem
reosarevok: on the hour for an hour.
2023-08-01 21301, 2023
reosarevok
Ok
2023-08-01 21302, 2023
mayhem
I'll tweet LB
2023-08-01 21317, 2023
reosarevok
Really expecting it to be that long, or is that just a very conservative estimat?
2023-08-01 21319, 2023
reosarevok
*e
2023-08-01 21337, 2023
mayhem
somewhere in between.
2023-08-01 21351, 2023
mayhem
if we promise 20 minutes, we take an hour.
2023-08-01 21307, 2023
zas
rebooting sentry
2023-08-01 21315, 2023
zas
next will be ludwig
2023-08-01 21340, 2023
reosarevok
"We're going down for maintenance at 15 UTC (in 15 minutes or so). We're expecting to take at most an hour, but we'll let you know when we're back. Sorry for the inconvenience!" ?
2023-08-01 21314, 2023
mayhem
sure
2023-08-01 21310, 2023
reosarevok
Done
2023-08-01 21324, 2023
mayhem
done for LB.
2023-08-01 21332, 2023
zas
sentry is back, ludwig rebooting
2023-08-01 21314, 2023
zas
bitmap: I think we can do zappa too, I think everything is redundant on it
