#metabrainz

lucifer: 👍 if there is enough time left after that, otherwise tomorrow :)

sounds good

I'm still provisioning changes for docker-server-configs atm.

yvanzo: "git tag -u CE33CF04 $version_number -m 'Upgrade MusicBrainz Server.'"

That good enough or do you want a different msg?

good enough, thanks

reosarevok: I reworded more than the first paragraph to avoid some redundancy.

yvanzo: ok, will check in a mo

Drafted docker release, please add the other ticket

(I know which one it is but you can word it better : ))

Can you do the docker jira bit when you feel it's ready?

The blog changes seem good to me

reosarevok: I completed the release notes

yvanzo: seems good to me. Publish that, publish the blog, and we're done, right?

Oh, I didn't check the docker link in the blog, dunno if you had already changed it when you drafted it

reosarevok: I added the MBVM version

Ok, publishing the blog

thanks, you did set the right link yourself at first

if I remember correctly I checked the link target on my first review

🐟

[musicbrainz-docker] release 03v-2023-05-22 has been published by 14reosarevok: https://github.com/metabrainz/musicbrainz-docke...

published ^

Thanks!

see the last 3 pages.

you can ignore the first set of pages.

lucifer: can you also please read the last 3 pages for accuracy of the technical data?

"Removing deleted listens from statsOn the 2nd and 16th of each month"

"Stats may not update for the 2rd or 16th day of the month."

I'm confused :D

"It may take up to an hour for a listen to be deleted at the top of the next hour"

I guess either "It may take up to an hour for a listen to be deleted" or "Any listens marked for deletion will be deleted at the top of the next hour" ?

the first 2 confusing issues are for lucifer to review.

Sorry kellnerd, I pushed it out of my head ! Fixed now with the help of mayhem

the second option for the latter issue is good, reosarevok. in case you'd like to edit it straight out.

The project page should now reflect the correct dates, but please do check I didn't flop up again

Sure

thx

Thanks monkey, I've just checked the project page and it shows the updated dates now.

👍

How come it's easier to add to spark than delete from it anyway? I haven't played with spark at all so it's probably obvious for those who have, it's just confusing as someone used to psql :D

First I had to logout and login again because Google was telling me that no GSoC account would we associated with that email 🙄

reosarevok: its not spark's fault. we just havent implemented letting spark know when a listen is deleted.

kellnerd: the gsoc site is known to be the worst site on the internet

After Renfe's, maybe - mayhem might have an opinion on that choice

renfe is for buying tickets. bahn.de is for finding trains.

so, yes, fucking terrible.

deichmans (norwegian library) website want's a word about that (worst website)

well it's not horrible, it's jsut really rally bad design

"It may take up to 4 hours for data entered into MusicBrainz to become available in the mapping system or for manual mapping."

How come it's 4 h rather than 1? Isn't it a normal mirror DB then?

reosarevok, mayhem: Listens are deleted from Postgres Database every hour, but removed from spark hence the stats reports bi-weekly.

"in the mapping system for both automatic and manual mapping" maybe?

reosarevok: not a mirror.

reosarevok: there are more steps involved then just propagating data.

Postgres and Timescale both are used for playlists?

yes

timescale stores the playlist data. and we query metadata of each recording from MB postgres.

Maybe we should expand on that? Right now it's a bit confusing if it just says "Postgres is our primary workhorse that serves user data (accounts, followers, likes/hates, etc) and Playlists. Timescale (an extended version of Postgres) is used to store Listens and Playlists"

Seems like they're stored in both places, but I guess it's parts and parts then

remove the first mention of playlists and we're good, reosarevok

Ok

lucifer: dumps happen on the 1st and 15th. importing happens on the 2nd and 16th, which is why we might miss stats calculation on those dates. is that correct?

mayhem: we usually don't miss stats calculations any day.

unless the dump generation or import failed.

Then I wouldn't mention the missing bit at all

Or at least, less gloomily than "Stats may not update for the 2rd or 16th day of the month." :)

when was the last time we missed stats because of this?

this 16th/17th because the postgres db was restarted during schema change that interrupted dumps

should we just leave this out then?

sounds good to leave out

ok, great.

Otherwise it all looks good, if technical

ok, thanks reo.

But I guess it's meant to be a "for technical people" read

yes.

(you could have a TL;DR version, I'm sure aerozol can write one)

the overview section is for that. and labeled as such.

lucifer: I'm not sure if this should be added as a wikidoc page on musicbrainz.org or if I should make a standard HTML page on lb.org? I'm leaning towards the latter.

mayhem: listenbrainz.readthedocs.io ?

sure, why not. good idea.

🐟

zas: I'll have a look at the query to see if it can be optimized at all. is it urgent to restart pink/floyd today or can it be done this week?

bitmap: it can be done later this week, but the sooner the better as usual ;)

servers remaining are: aretha clash floyd gaga kiss pink quest

mayhem: sure, ok, I was just thinking in case you want a sentence about having many interconnected parts

Something like "This complicated schedule is caused by ListenBrainz having a lot of interconnected parts that work at different scales. For more details, read on!"

But with aerozol's "make it simple and not-stupid" wording maybe :p

where would you put that?

At the end of the Overview under the list of update times I guess?

[bookbrainz-site] 14MonkeyDo merged pull request #983 (03master…add-placeholder-text): BB-721: Add placeholder text for empty sections https://github.com/metabrainz/bookbrainz-site/p...

lucifer: Hey!!

How currentUser data is going in globalAppContext

jivte_: hi! this function obtains the data from session and database, https://github.com/metabrainz/listenbrainz-serv... and it is then injected into the html template of the page at https://github.com/metabrainz/listenbrainz-serv....

reads the JSON data from the html and creates a globalAppContext for it

okk thanks!!

reosarevok: I might join the meeting a bit later today, so please don't call me first :)

kellnerd: go!

Oh, wait

Ok :)

lucifer: Would tomorrow 10 UTC work for you moving RMQ from/to clash?

yvanzo: yes

Ok

Welcome to Modify your Musings Monday!

(aka, you can now edit recent edit notes in MB, mess up with confidence!)

(?)

After a break for last week's schema change, which went, as the song goes, surprisingly ok

We're back with a standard meeting

🐟 !

We have one mailed in review

lolol.

as the song goes.

Our usual sleeper says:

'''

Atā mārie (good morning) from NZ.

The main thing I worked on was templates and systems re. making noise about news/updates/events - putting in the time now so we can quickly and confidently get news out in future.

Still in progress, with mayhem and Rassami having input, but in the meantime could you all please have a look at this fillable template? https://drive.google.com/file/d/1CsSLER5LbkC0KM...

Can you imagine quickly filling one of these out if you have done something cool (or see something cool)? If not, how could I tempt you or make it easier (including ideas that don’t involve a form)?

I also finally did the first round of mockups for the ‘proper’ rollout of the LB recommendations/jams feature!

Other than that, I did the usual, some guideline updates, and helped drag a Picard ticket to the seventh level of hell. Good times.

In nicer news, my other work deadline has passed, so I am able to do more on MeB again! Woooo

'''

(that was aerozol, for clarity)

We have the usual list for today:

reosarevok, bitmap, zas, mayhem, yvanzo, monkey, lucifer, akshaaatt, atj, CatQuest, Pratha-Fish, riksucks, jasje, jivte, kellnerd

usual sleeper was clear as a crystal

usual slacker would've been clearer

yeh. and also the "Atā mārie (good morning) from NS" part

except no. confusion with reosarevok

(if any GSoC students for this year want in on our meetings already, let me know!)

lucifer: wanna start? :)

sure

hi all!

Hi Everyone!

last week, i did some more experiements to process MLHD on the existing spark cluster but no success

so had a discussion with mayhem on adding more resources to it.

also did some progress on MeB Oauth stuff.

that's it for me. bitmap: next?

hey

last week I helped with the schema change release (thanks yvanzo and reosarevok for doing most of the work) and upgraded the json dumps DB on aretha

I also did code review and spent time profiling the JSON dump script to better document the performance bottlenecks

!m you three with a smooth schema change

You're doing good work, you three with a smooth schema change!

that's about it, go zas!