Notes from #MetaBrainz Meeting 2021-10-11

[Freso]

MetaBrainz Meeting 2021-10-11

Meeting start: Making sure you're not a bot!

International Monday of the Girl Child

Girl Child Song - Afghanistan National Institute of Music

Agenda

• Reviews
• MeB Summit Planning
• Sentry upgrade
• syswiki
• Next meeting

Last meeting: 2021-10-04
Next meeting: 2021-10-25

Reviews

@yyoung

Making sure you're not a bot!

@yyoung

• Last week I opened a few tickets and looked at some others related to URL cleanup.
• Apart from that, I set up a local replication database of MusicBrainz to get a better view of the URL relationships, and improved my PR #2296.
• After spending some time exploring the data, I found a couple of issues and came up with several cleanup projects, now I’m considering writing a bot for them.
• That’s all, thank you.

@lucifer

Making sure you're not a bot!

@lucifer

i was afk for ~half of the week due to college work. other than that i worked on some small LB tasks. an improvement in LB recommended tracks, issue triaging, small UI bug fixes
and earlier today helped alastairp in completing the sentry migration.

@alastairp

Making sure you're not a bot!

@alastairp

I finished my work to convert JS in AB to typescript, thanks to monkey for answering all my questions about that. This is now deployed
We decided to deploy a new version of sentry (more about this after reviews), and it’s now running - just need to do a dns change, everything else will remain the same. @lucifer has already started to use some neat new features like tracing and it looks cool!
I responded to some old threads on the forums, and made some updates to the readme in troi
we finished discussions on updates to the suggested listen format. I need to turn these discussions into documentation. I also took some time to analyse the format of data submitted in listens to see what people are submitting
In short: l.fm and spotify importers have submitted the most listens, other file-based submitters tend to send all metadata tags, there are really not many other submitter tools, and most of them only submit the bare minimum
I also reviewed a PR by @bitmap to update the base image for our python projects, that looks fine and we should be able to start using it soon

@reosarevok

Making sure you're not a bot!

@reosarevok

So, this week I mostly worked on updating all the PRs for this milestone based on feedback
And on debugging a few issues with my PR removing unused variables and imports in our Perl files, where it turned out I removed a few variables too many at first because they used a specific perl wrapping technique that made them look unused to Perl::Critic
So the debugging of that took quite a bit and was confusing
Working now though
Today I did nothing because my laptop hinges were being replaced, more tomorrow!

@ApeKattQuest_MonkeyPython

Making sure you're not a bot!

@ApeKattQuest_MonkeyPython

Made mb work for me again!
Worked on instruments!
will continue with this this week!
also please check this community post to help some language alias if you can!
Call for help on an Instrument alias!

@Freso

Making sure you're not a bot!

@Freso

I mostly poked at reports last week and was around and about for a bit, but I was also not feeling super great, so. :\ Feeling better but have an achy throat.

@rob

Making sure you're not a bot!

@rob

last week I finished migrating the MBID mapping to include artist_mbids and a few other changes.
then I worked on adding MBIDs in listens, so many listens should soon have MBIDs, which is quite exciting.
I prepped for the board meeting happening in just under 2 hours and talked to a few potential new users.
and then I ran off to Francalunya for hiking and roman baths and amazing food.

@zas

Making sure you're not a bot!

@zas

Apart usual supervision, upgrades, etc… I tuned our nginx in-memory caching
traffic to backends (CAA redirects) is actually divided by 5
then we released Picard 2.6.4 and 2.7.0beta1
I also spent some time tuning mb ws / website containers and related load balancer weights, since we moved quite a lot machines recently
I manage to reduce response time overall, plus equilibrate response time among machines
I investigated an issue related to consul/openresty/spurious config reloads
which led me to go back to gitzconsul (git2consul replacement) coding
I deployed it today
it will rule out one cause of problem

@akshaaatt

Making sure you're not a bot!

@akshaaatt

I had an explosive week. Loved the work totally this time around!
MusicBrainz Web Homepage 2021 everyone please checkout the post and do share your thoughts on this
I want to wrap up this work soon, hopefully this week so that I can focus on more stuff
I have even prepared a design mock for LB, which I’ll be sharing soon
Things are going great and life is at peace currently.
I will be finalizing things this week, so if you have any major updates regarding the code or the design, do make sure to voice your thoughts

@yvanzo

Making sure you're not a bot!

@yvanzo

Last week I reviewed some PRs, tickets, and updated beta with a patch by @yyoung.
(Not much to report as I was still mostly off otherwise.)

@bitmap

Making sure you're not a bot!

@bitmap

last week I worked on some changes to prevent 50x errors from occurring when we deploy new MBS containers (though they’re not merged yet) - Try to eradicate 5xx errors during deployment by mwiencek · Pull Request #2297 · metabrainz/musicbrainz-server · GitHub
and made a minor fix to the replication scripts in dbmirror2 support by mwiencek · Pull Request #2248 · metabrainz/musicbrainz-server · GitHub
later I released some new versions of base-image, consul-template-base, and docker-python using focal & a newer consul-template - Add a 3.9-focal Dockerfile by mwiencek · Pull Request #13 · metabrainz/docker-python · GitHub
I’m using those to base the artwork-indexer Dockerfile on, so we can deploy that to replace the CAA-indexer soon
other than that I worked a bit on some edit page changes to make them ready for React, mostly for the artist credit editor to use the new Autocomplete2 component and work in the release editor
I discovered https://recoiljs.org/ which I’ve been testing and it’s made state management infinitely easier for what I’m doing. might be worth checking out if you need to share a lot of state between components in React. the video on the homepage is a good intro for when it might be useful

@mr_monkey

Making sure you're not a bot!

@mr_monkey

Last week I continued on the past month’s theme of refactoring the ListenBrainz front-end components.
The two main projects were making the charts pages playable (see here: https://listenbrainz.org/user/mr_monkey/charts/?page=1&amp=&range=all_time&amp=&entity=recording)
And refactoring the BrainzPlayer entirely to decouple it from other components, with a view to make a standalone BrainzPlayer library that can be embedded in our other websites
I also continued with refactoring the next page on the list: the recommendations page
I also reviewed some PRs, and spent some time looking for memory leaks and performance issues with BrainzPlayer

MeB Summit Planning

@lucifer

as you all know, the summit is this weekend. @rob has updated the wiki page Making sure you're not a bot!
and created a spreadsheet to track schedule and topics here:
MeB 2021 Summit Timetable - Google Sheets
we have added some topics already. others also please add to this list.

Sentry upgrade

@alastairp

this is mostly just a notification: we tried to upgrade sentry to a new version but it failed, so we installed a new version from scratch. Config is the same, so user accounts still exist and DSN config endpoints won’t change. however issues won’t be migrated
@lucifer has gone through and done most of the ones that he’s directly related to
we see some other projects: caa, MB, sir, picard-web, that neither of us are directly involved with
if one of these are yours, please either tell me that we can delete the old data, or tell me that you need time to revise it

syswiki

@alastairp

another notification: this afternoon we experimented with moving syswiki to github wikis, and @rob spend some time deleting some very old pages
this does mean that we’re in a situation where there are docs in both the wiki and the git repo
we have a pending task for the summit to see if we can clean up this more. until then, please be careful with where you edit

Next meeting

@Freso

So, we usually take the meeting directly after the summit off.
Any objections to doing that again this year?
(That would make the next meeting be Oct. 25th.)

No objections, so next meeting will be October 25th.