Notes from #MetaBrainz Meeting 2023-11-20

[aerozol]

MetaBrainz Meeting 2023-11-20

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

Agenda

• Reviews
• uWSGI error

Last meeting: 2023-11-13
Next meeting: 2023-11-27

@reosarevok: It’s time for our Monday meeting, aerozol’s favourite part of Tuesday!
[for context, these meetings are quite early in my timezone… - aerozol]

Reviews

@rob

[mayhem] [mailed in] Last week was all about the summit. Prepare for the summit, travel to the summit and hold the summit.
I haven’t had a chance to summarize the event, because India. Hopefully, lucifer and the others can actually do a better job. But it was a great summit with great people.
Here is our photo album

@zas

[mailed in] I’m going to listen Jeff Mills in Lyon, so I can’t be there for the meeting.
Last week:

• fixed an issue with LE certs and obsolete root certificates
• improved local IP detection for hosts not on 10.2.2.0/24 network
• handled a network issue with flobot (it was inspected, nothing found, but the issue disappeared, perhaps due to reboot), another issue just appeared on this node (an hard drive to replace, it will be handled tomorrow).
• plus usual PR reviews, user support, upgrades (discourse was upgraded), MB edits

@CatQuest

[MonkeyPython] added INST-1094: cobla
now working subtickets on INST-773: Bagpipes
(could someone be a dear and add a jiraticket for the french cornemuse? eg French bagpipes - Wikipedia)
been doing some needed afk stuff today but this week I hope to be adding plenty bugpipes : D

@Yvanzo

Last week I did some maintenance, one day moving MB Redis, another day preparing the move of MeB.o and its dependencies.
Also I drafted a patch to drop hundreds of MB admin-only messages from translation.
Last I reviewed a fair amount of pull requests, plus some tickets and support.

@bitmap

last week I was looking into some MB fullexport failures and found out it was due to lack of disk space on trille, so I helped move services to hendrix (thanks atj, yvanzo, zas), as yvanzo mentioned, which went fine
after that I was looking into some warnings/errors in our hourly/daily cron logs, and fixed a few issues -
MBS-13300: Empty release group with manually set cover art is not deleted
MBS-13372: Unused URL with gid redirect cannot be deleted
MBS-13310: Artist not automatically deleted
fixed another issue with our incremental sitemaps script, MBS-12239: “Too many URLs” error on building incremental sitemaps for release group aliases
fixed some issues with the musicbrainz_ro (missing GRANTs mostly) and worked a bit more on a branch to make MBS use our PG standby
opened a PR for improving the instrument attribute search in the relationship editor (MBS-13055: Regression: Instruments as attributes can’t be found by alias, MBS-13340: Instrument attribute search is case-sensitive)
other than that I think I was mostly working on some misc. React stuff for the add-cover-art page and artist credit editor, and doing code review

@mr_monkey

[monkey] Last week I continued rewriting the LB test suite to react-testing-library. I do like RTL’s philosophy of “don’t test internal implementation”, but I have to say it’s a huge pain in the ass once I got to testing how some LB pages react to websockets messages. Faking a socket.io websocket server and also a client is a big headache. Finally made some breakthrough just 30 minutes ago.
I also did a bit of CSS magic for the fresh releases page helping ansh out, and continued work on the entity pages a bit
I also looked into some smaller LB API tickets and improvements, and reviewed aerozol’s designs for YIM
Aaaaaand some PR reviews.

@anshgoyal31

[ansh] Last week, I attended the Delhi Summit and had a blast meeting with everyone. Had some great conversations regarding couple of features.
Other than that I continued working on adding play queues to BrainzPlayer.
Did some UI fixes to fresh releases and reviewed a PR.

@reosarevok

Last week I did a bunch of code review, fixed a few minor bugs (including MBS-13368: New series rels falsely detected as duplicate when numbers differ) and merged quite a few PRs
Also fixed a few tests that had broken in the PR lowercasing stuff (turns out Selenium tests looking for specific text don’t like it when the test changes, who would have thought)
And dealt with a lot of user reports and the like

@snaekboi

[Pratha-Fish] I don’t even know where to start with this one lol
Had a TON of fun with the team in India!
Discussed some LB user feedback in my slides
Wait I’ll paste some photos in while we’re at it lol [1] [2] [3]
Since it’s common to touch feet of teachers and respectable people in India, here’s me touching lucifer’s feet lmao
I could go all day with these lol, but I’ll keep it for the time we all meet in India summit if the logistics for it works :))
Reaally looking forward to seeing you all in person some day

@jasjeet

[jasje] last week was all about summit if it isn’t obvious by now
apart from meeting all the really great peeps and having fun with them
we did work too wink wink
For LB Android, we discussed on how we should market the app
right now, I was more keen on focusing on how to market the app to developers to induce contributions
These are some of the solutions I presented which are very doable
akshaaatt and I brainstormed on how to do the re-write of scrobbler and have the basic idea laid out but still stuck with few edge cases.

@akshaaatt

Apart from the usual, I was busy with work stuff since I am attending a conference in Japan in December
So yeah, not much. It was good to meet everyone and I hope the discussions we had then turn out to be fruitful

@aerozol

The usual socials and whatnot, but mainly did a big push to finish off the plans for YIM 2023
I would say that the visuals are ‘functional’, but I was able to address more edge cases and scenarios this year, so it’s a logistical improvement this year, at least
(but hopefully people still enjoy the style)
One thing I made that I really want LB peeps to look at is a timeline/checklist doc. Last years launch was a bit of a nightmare, but I feel like people may have forgotten
The link can be found at LB-1178: Year in Music 2023
Or direct link: Google doc
So now if anyone is stressing on the 1 Jan I know I did my best to help!
Made another YouTube tutorial to try keep that channel fresh-ish
And finally started work on a good quality illustration for the LB home page
Oh, almost forgot, made a doc for Delhi summit notes
Let’s do an awesome blog post/all other channels as well, so once you’ve recovered please fill in the doc attendees (or use your own medium/however you’d prefer)
[added later] There’s been new posts on the twatter, which is awesome! Go for it, whoever that was! Wanted to make a quick note that if it’s a ‘casual’/informal message it’s good to sign off with your username, so we can keep track of things, and it makes it look friendlier for readers as well
I’m happy to copy things to the other channels as needed so no need to worry about that

@kellnerd

Not much to report this week, I only did some MB voting and editing (more data cassettes… and using the new broadcast relationship, yay!)
Other than that I was busy with university and baking lots of Plätzchen (christmas cookies) : D

@atj

last week I did some ZFS set up on hendrix and other minor tasks to assist bitmap with the MB data dump migration.
I also reviewed a couple of PRs.

@lucifer

last week, i helped in organising the india mini-summit. it was very awesome meeting all the attendees. we had lots of fun discussion lots of stuff and exploring delhi.
had an extended discussion with rob and param about the data pipelines in LB.
other than that worked on fixing some bugs in LB.

uWSGI error

@atj

when I was helping bitmap with the MB cron migration I noticed the logs were being spammed with several messages per second: Snippet | IRCCloud
this was on trille and hendrix, didn’t check any other servers
the cause was the uWSGI issue that (I think) only started happening recently: Snippet | IRCCloud
[…]

What followed was technical discussion and explanations of the issue, with a few participants. For the full discussion check the IRC logs, here.

Absent: -