Notes from #MetaBrainz Meeting 2024-02-12

[aerozol]

#MetaBrainz Meeting 2024-02-12

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

Agenda

• Reviews

Last meeting: 2024-02-06
Next meeting: 2024-02-19

@reosarevok: Hi and welcome to another Monday!
And good Carnival for anyone who likes wearing fancy weird clothes

Reviews

@CatQuest

[ApeKattQuest] As expected didn’t get to do a lot last week.
but I did manage to close [INST-1079: dūdas] as well as finally managed to untangle the greatest floke (tangle)
so expect SEVERAL dudes in the database Soon™

@mr_monkey

[monkey] Last week i mostly worked on the BB search indexing, we’ve had some issues with a release last week
hotfixed for now, but working on a solution.
And I reviewed PRs for LB

@zas

Last week, spent some time with system reboots and a docker upgrade issue
it was to apply important security fixes: kernel, ssh, glibc and docker
Also worked a bit on Picard plugin API V3 with outsidecontext
I fixed an issue with mbstats: some stats were missing due to unremoved lock file after system reboot
plus usual supervision, upgrades, user support, PR reviews and MB edits.

@bitmap

Last week I worked on updating [pull 3130] based on review feedback, then deployed it on Friday, and subsequently had to write another patch due to a scenario I didn’t think of : )
(which was deployed with the release today)
I worked a bit more on the artwork-indexer, testing and fixing a few minor things
helped with the multi-day server reboot project, but mostly on the PG side
we enabled logical replication and increased max_connections in the PG configuration
other than that I mostly did code review and spent time trying to debug OOM kill issues in the musicbrainz-website-test container

@anshgoyal31

[ansh] Last week I worked on migrating the more [ListenBrainz] pages to SPA and added SEO tags to the existing pages
Almost every page has now been migrated to SPA
I also spent time on some final changes for BrainzPlayer queues.
Also refactored User Dashboard pages PR and spent time researching about optimising the frontend to reduce page load times by using lazy loading and caching.

@lucifer

last week, i tried to debug the weird load peaks on kiss and an overload of database connections. nothing substantial yet, but have a few hunches about it.
fixed some bugs like export listens button leading to deletion of listens and helped out a user restore their listen history who was affected by it.
reviewed some PRs about merging content-resolver in troi and the nmslib fork.

@rob

[mayhem] last week was the usual biz dev stuff and keeping the lights on.
then I mostly worked on merging the content resolver into troi and packaging one of its depedencies.
the package is amazing, but its been abandoned with a lot of people clamoring for a new release.
so, forked it and released it. soon we’ll have builds for mac as well and then the world can use these packages again.
thanks for everyone who made that happen! outsidecontext (IRC) lucifer (IRC) gcrk (he/him)

@aerozol

Finished off the blog post for the LB 2023 recap - thanks everyone who helped check and proof it!
Made a few new tickets, e.g. [MBS-13480: Show cover art thumbnails on Artist and Release Group pages]
Apart from that just the usual, nothing exciting sadly

@yvanzo

Besides helping with server maintenance operations, I mainly worked on MB Solr search.
For GSoC org application, I redacted an MB idea based on aerozol’s suggestion of links page.
Also I relisted the idea of Rust binding for MB SQL schema as yellowhatpro has shown some interest.
Got lucifer in a call to test deploying an MB dev setup and an MB database mirror on Windows 11 with WSL 2.
Plus some PR reviews, a couple of MBS beta updates, support, and tickets triage.

@honvegee

[geetika] I worked on the bpm tracker and finding max beat project
so i started out by exploring what current system does, and its fallacie with different sorts of genres and music
i read some repos and papers on it, and planning to implement a basic skeletal neural network based system for the same

@reosarevok

This week I dealt with the usual support and community issues, plus I reviewed a bit more of the Spanish translation of MBS (and found more strings that needed further context)
And I worked on a few small URL tickets plus updated a bunch of React ones to hopefully merge soonish

@kellnerd

I was working on elbisaur a bit more to polish a few rough edges and document its current features (as I plan to pause that project in a good shape).
Still not there, but hopefully this week.
Also I was annoyed that every time when I’m working with cuesheets, chapter and tracklist formats and want to convert between specific formats, I am writing a new one-off script and forget about it afterwards.
So I’ve started to put a small library of parsers and formatters together and wrote a simple CLI which can convert between any two supported formats.
If anyone has a better name than cueshit (short for “cuesheetify it” ), now is the time to enter your suggestions.

@akshaaatt

I released a beta for the android app recently
We made many bug fixes and should finalize things for a prod release asap

@atj

last week i worked on some changes to the docker and consul roles to significantly improve the method with which we lock those packages to specific versions.
i then also implemented/updated our playbooks for performing consul and docker version upgrades
following that i upgraded the docker version on all servers
that led to some very odd intermittent connectivity issues being reported after servers were rebooted
the following day i spent several hours working out wth was going on, only to discover that Docker had decided MAC addresses no longer needed to be unique
fortunately i managed to resolve the issues on jimmy by restarting various containers
i then wrote a script to parse the docker inspect output of all containers to determine which had mismatched MAC addresses.
zas found the relevant Docker bug and we were able to upgrade to a fixed version and then schedule downtime to reboot the impacted servers and resolve the issue once and for all.
lots of fun was had by all involved.
thanks to yvanzo, zas and bitmap for their help in getting that issue resolved

@jasjeet

[jasje] [who was late, everyone make tutting sounds!]
last week was slow
i have been looking at what is causing the bug
that submits repeated listens for some user/s
but to my testing
everything is working fine
so I’m thinking of implementing stricter policies for listen submission in the near future.

absent: Pratha-Fish [1]