Notes from #MetaBrainz Meeting 2025-01-27

[aerozol]

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs
Meeting wiki page: MetaBrainz Meeting - MusicBrainz Wiki

Agenda

• Reviews
• Hetzner mainboard repl

Last meeting: 2025-01-20
Next meeting: 2025-02-03

@reosarevok: Welcome to another MetaBrainz Monday Meeting!

Reviews

@julian45

[mailed in] Hi all! I unfortunately had another meeting conflict and take precedence over this one : (
This week, I did some research about some particular infra security improvements we might do and discussed them with zas. After fleshing them out some more, I will likely add them to the agenda for next week or the one after that

@derat

[mailed in] I’ve started thinking about MBS-13711 some more, although it’ll probably be a week or so before I can start writing any code for it.
[MBS-13711: Prompt beginner users about likely capitalization mistakes]

@ApeKattQuest_MonkeyPython

[mailed in] Worked with Monkey on figuring out a setup for how we’re going to work things; biweekly meetings.
Have worked on the TOC of our style-documentation, will continue making that better.
This week I hope to finish that and also the gopichan if I get time (heh, it’s complicated so I keep pushing it off, lmao.)
Otherwise I’ve done a fair bit of offline stuff.
Winter is still wintering here and I sorta wish I was still on Lembongan

@yvanzo

Last week, we almost had a meeting about MusicBrainz search development.
Occasional contributions still helped with making small progress.
At this slow pace, upgrading will surely be delayed again.

@rob

[mayhem] last week was finally back to technical work, reviewing PRs and picking up other things.
the cron monitoring PR is up and another stats monitoring check will go live this week.
I’ve started looking at the fuzzy search indexes, playing with new features in typesense since we implemented the search at first. we’ll see how that turns out.
I’m so happy to finally be caught up from the new years stuff and am happy to see so many volunteers floating about right now. : )

@mr_monkey

[monkey] Last week as mentioned I had a chat with MMonkeyPython and on the heels of that did some updates and changes to the BB user docs.
Also had a chat with the LB team about our upcoming work and potential GSOC projects
A lot of PR reviews
And doing some trials to improve the timeline indicator on the fresh releases page
And finally some triage of Sentry issues, which I now call Sentriage

@reosarevok

Last week I spent quite a bit of time (hopefully) improving the alias guidelines, which was prompted I guess to some degree by the new aliases display
I worked on some more open PRs to make them mergeable
And worked with bitmap to get more docker monitoring stuff looked at
Oh, and reviewed and thought about the new docs pages
Plus the usual small fixes, user admining, etc

@Gautam_coder

[Gautam Shorewala] Last week i got some of my pr merged
Also fixed some bugs in LB

@jasjeet

[jasje] Last week was fun
Lots of PRs merged and quality of the app has been improved
Thanks to all the contributors that are doing such a great work
Brainzplayer has been improved, login flow has been improved and a new created for you tab is also coming to the app in next release

@shreyassp002

[Shreyas] Last week, I figured out a couple of bugs from the Brainzplayer tabs
Implemented onClick logics for AtistsOverview and AlbumsOverview
Got some PRe merged

@anshgoyal31

[ansh] Last week I worked on almost finishing generating playlist cover arts.
I picked up my PR for BrainzPlayer Mobile View, and made some final fixes.
Had a discussion with the LB team regarding projects for GSoC 2025.
And reviewed a couple of PRs.

@lucifer

last week, i was busy attending some family functions and also got sick for a few days so didn’t get much done. looked into a couple of disk space issues on the spark cluster and some work on incrementalizing popularity data generation.

@zas

Last week I upgraded docker-rsyncd container (sec issue)
Plus usual supervision, user support, PR reviews, and blocking some abusers (we got a recurring heavy flood on MB, solved now).
Also planned the move to a new dns provider.

@bitmap

last week I did code review, worked on Solr metrics for musicbrainz-docker, reviewed the RTD questions doc from rdswift, and worked on finishing some old code to reduce the amount of JS that gets loaded on every page - Optimize webpack bundles by mwiencek · Pull Request #3457 · metabrainz/musicbrainz-server · GitHub
oh and started trying to update our deployment scripts to allow running multiple MB prod containers on the same machine, as recommended by zas

@kellnerd

Last week Harmony’s Tidal support broke because Tidal turned off their v1 API without any prior notice : (
Turns out they replaced the API documentation for v1 by v2 six months ago, merely a few weeks after outsidecontext implemented support for it…
I haven’t properly fixed it yet because that is effectively an almost complete rewrite using the v2 API.
I haven’t properly fixed it yet because that is effectively an almost complete rewrite using the v2 API.
Instead I finally tested and released the latest improvements I’ve been working on around new year (to get them out of the way).
And the initial provider test infrastructure is finally ready, now a simple specification can be used to test URL extraction/reconstruction and release lookups.
For the later I stubbed fetch with an implementation which loads the raw data from a local cache (rather than spamming API requests every time the test suite runs) and compares the converted release against a snapshot.

@outsidecontext

not much really. early last week I fell sick, and was mostly useless for the rest of the week.
ok again mostly since yesterday. I looked a bit what we need to do to get a picard 2 release out.
also yesterday started looking into the harmony tidal issue kellnerd mentioned. I have it mostly working, with some cases being a bit annoying with their changed API.

@aerozol

Things heating up with work and life this week, so just got the usual stuff done. My misc tasks have built up so it still ends up being a bit (comms, discussions, tickets, style…)
I checked in on CB spam for the first time in ages and might have found an early contender for review of the year
Review of "Sound of Nature - Ocean Waves" by riwood - CritiqueBrainz
Nothing else that stands out!

Hetzner mainboard repl

@zas

We got a notice from Hetzner, they’ll start to replace mainboards on AX102, AX52 servers
But since they’ll have a lot to do, they’ll just alert us 4 hours before [to make an appointment?], and it starts in Feb
more details on https://docs.hetzner.com/robot/dedicated-server/general-information/mainboard-replacement-for-several-dedicated-servers/
For us, it means we have to handle that on 4 servers: hendrix, jimmy, yamaoka, randy
That is rather critical ones.
We can order new servers (but we aren’t certain about delays to get them)

A bit of server/technical discussion, please read the logs for more.
In brief, it is likely we will accept some downtime, rather than buying new servers (which will be a lot of work for the team and the servers likely wont be better/faster).