mayhem: If we’re not updating reports then shall we remove this link from the menu? It makes MetaBrainz looks like it’s not being maintained if it happens to be one of the first pages you visit: https://metabrainz.org/reports/2017
bukwurm joined the channel
aerozol: that apiseeds lyrics question is odd. They say they registered an API key on apiseeds.com, but this has not been available since 2 years, the Picard plugin also got removed 2 years ago. 🤔
outsidecontext: Yeah I clicked to that after looking at the Google translate results a bit closer. Maybe someone wants to tell them they’re out of luck in French :D
There was happi.dev as the successor, and even that shut down earlier this year
Yeah, lyrics sites aren’t worth putting heaps of effort into supporting imo, unless they’re some ma$$ive outfit like Genius
aerozol: indeed. there have been several lyrics plugins come and go. everything with an open API will have a short time span :)
I reactivated my old reddit account and answered in English
Hey reosarevok would the codebase for the bot be on MetaBrainz's GitHub profile, or my own GitHub profile? Just confirming
Probably MeB, I can open a repo at some point
Then you can work on your fork and send PRs against the MeB one as needed
BrainzGit has quit
BrainzGit joined the channel
aerozol has quit
aerozol joined the channel
Hobbyboy|BNC joined the channel
pbryan8 joined the channel
Hobbyboy has quit
DjSlash has quit
KassOtsimine has quit
yvanzo has quit
pbryan has quit
riksucks has quit
pbryan8 is now known as pbryan
kgz has quit
KassOtsimine joined the channel
yvanzo joined the channel
Hobbyboy|BNC is now known as Hobbyboy
DjSlash joined the channel
riksucks joined the channel
KT03 joined the channel
reosarevok: Do we have a media at metabrainz email? Just making a generic comms/marketing form to fill out, and need a default email. I know you check the community manager email but not sure if that’s quite right
KT03 has quit
kgz joined the channel
antlarr has quit
antlarr joined the channel
mayhem: hi! I had filled the Soundcloud form to change redirect uri about 8-9 days ago but haven't received any response. should we reach out to the person we had a meet with the other day? also, can we request him to make one more application for us that we can deploy on test.lb for testing.
About one hour of downtime is expected starting from 5pm UTC to upgrade to the MusicBrainz database to its latest schema.
i prefer to pivot and then touch base to make sure we're in lockstep
everyone: I’m putting together a list of news sites to send news to - where do you get your tech/open source/music information from, that might suit us? Especially smaller nerdy outfits. New-fangled podcasts and youtube channels, etc, qualify just fine.
mayhem: maybe those docs are a good start re. stuff for Rassami to look at and feed back on or add to
okay, bed time for me. Hope the schema change goes well all!
release_first_release_date is identical to a query that computes it from scratch, which is good
I did notice that some first-release-date data in release_group_meta and recording_first_release_date is wrong/inconsistent, but then checked the production DB, and those problems already exist there. so it appears to be unrelated to withdrawn releases or the upgrade script
and I think I know why the recording ones are wrong, but it'll have to be a future schema change
Oh, it's that bad? :/
well, I'm pretty sure we're missing a trigger for medium updates - when releases are merged using the append strategy, some medium.release columns are updated, which affects all of those mediums' recordings' dates
Fortunately this can be changed in production ahead of the next schema change release since it doesn't require any change on mirror side.
bitmap: Why is it recommended to restart Redis for the schema change (last year at least)?
I guess it was related to some change but couldn't find it. Not sure it is still needed this year.
I'm guessing just in case there are any code changes that affect cached entities (like changing the Moose entity models)
right, it may not be needed this year
Do mirrors get the date info from us or do they calculate it with their own triggers? I forget
Good question, not sure.
release_group_meta is replicated, but the other two materialized tables (release_first_release_date, recording_first_release_date) are not and are updated by triggers on mirrors.
we could rebuild recording_first_release_date as part of our upgrade steps and recommend mirrors do too. though it will lengthen upgrade process by a little bit and won't fix the underlying issue, just existing data.
Yeah, that's what I was thinking
How hard is that fix?
(as in, is there any chance we can offer a way to fix it for schema change users if they want to fix it as part of this SC even though it was not announced, or is it hard and we should wait with it anyway?)
well, I don't think writing the trigger will be hard, but would rather wait to test it properly. we could always mention the upgrade script in future MBS/docker release notes
I would just wait with it, we can probably come with a workaround to fix existing first release dates before the next schema change.
I'm sure we can, it's just they'd need to run it repeatedly :)
But I guess there's no reason we can't say that we'll publish an updated trigger later
And they can install it outside the schema change themselves