#metabrainz

mayhem: ready to discuss next tasks when you are.

remind me, what is currently on your plate?

my weekend plans didn't go as expected (was caring for a sick person), so I didn't get a chance to ponder all this.

looking at open LB PRs, I don't see any in progress tasks and can't remember any others off the top of my head.

ah okay.

so, right off the top of my head, there are two things:

1. Continue work on MeB/OAuth

2. LB radio needs an improved UI for a better testing experience.

for #2, I need a react page that has a query field and a generate button.

makes sense on #1

when the user enters a query and hits generate, the results should be shown in a playlist under the prompt.

for #2, do we want aerozol to do a mockup first?

and there should be a "save as playlist" button.

the target audience is beta testers, so lets skip that. for the final UI, which will be a lot fancier, we'll get a proper mock-up done.

oh and an export to spotify playlist.

button

makes sense.

interested in taking a stab at #2 or do you want to give into #1?

i'll start with #1 for now. and work on #2 if a blocker comes up

ok, then I'll probably start working #2 later todya.

sounds good

for the data for arsh's project, i think its best to add that on LB side at query time.

I've also spent time thinking about a notification system, I need to write that up.

LB side at query time? elaborate please

I mean we have popularity data store in timesclae and mb_metadata_cache in timescale as well. so join the two datasets for each API request.

ah I see. yes, perhaps that ought to be the first project to do, come to think of it?

yup makes sense. i'll add that first.

k

mayhem: https://test-api.listenbrainz.org/1/popularity/...

I'm seeing entries duplicated: https://test-api.listenbrainz.org/1/popularity/...

which ones?

at least the top 3. roads twice, sour times twice, mysterons twice

oh i see, everything is in there twice

i'll fix that. other than json looks fine?

yes, should be good. thanks!

[listenbrainz-server] release 03v-2023-07-31.0 has been published by 14github-actions[bot]: https://github.com/metabrainz/listenbrainz-serv...

monkey: I've made this codepen for the LB radio react page: https://codepen.io/mayhemchaos/pen/qBQLaKQ

not great, but good enough for what I need now.

except now I have no idea how to load the results....

maybe when you have a minute, steer me in the right direction, please?

lucifer: got another playlist that refuses to export to spotify: https://listenbrainz.org/playlist/33a03225-50d6...

mayhem: Can do, in 45 minutes or so maybe. The gist of it is you'll need a callback function that will be called when the generate button is pressed, in which you will call the API you need to call and set the results in the component state.

We do something similar here, but there's a certain number of gotchas to look out for which we can look at together: https://github.com/metabrainz/listenbrainz-serv...

thanks for the tips, 45 mins is great!

Hey

bitmap, mayhem, monkey: around for a bunch of server reboot?

I am here

Mayhem just left the office, will probably be a moment

ok, let's wait for them

I'll be around in 10. lucifer can help too

great

Lucifer you about?

hi yes

We're taking full downtime, yes?

If so, we can start tweeting.

Ok, since lucifer can help, let's get started.

[bookbrainz-site] 14the-good-boy opened pull request #1005 (03administration-system…relationshipTypeEditor): feat(Relationship Types): Relationship Types Editor and Relationship Types Page https://github.com/metabrainz/bookbrainz-site/p...

zas: I'm here (sorry internet was acting up)

zas: which servers have already been restarted?

none yet

Tweeted.

(For BB)

ok

i'll stop cron in mb containers

zas: i'm not sure jimmy is ready to be made primary today, should we do it another day?

so, what's the plan?

[listenbrainz-server] 14MonkeyDo merged pull request #2475 (03master…listening-now-tags-2): Listening now: allow users to vote on and add tags https://github.com/metabrainz/listenbrainz-serv...

bitmap: you mean delaying the move to primary, or the whole reboot session?

well, I thought the servers had to be rebooted because of some docker issue

just the move to primary

we mentioned before it might make sense to do the primary move at the same time (since both require downtime), but not sure it's ready yet

ah yes, no problem then, we need to reboot them in order to docker containers to be updated with fixed version

ok, cool

mayhem: can you tweet about MB downtime ? (let's say 1 hour or so to be safe)

I can do that too if needed :)

Unless mayhem is already on it

not yet.

Ok

that is why I was asking what the plan was. how long? when?

does it make sense to proceed so close to the meeting?

"We're going down for scheduled maintenance. We expect it not to take too long, we'll let you know when we're back" I guess?

i'll also be around after the meeting

I won't be available after the meeting

mayhem: the plan was to do it before the meeting, but it seems a bit short now

guys, what about delaying to tomorrow? same time? so we can have more time for it

Sounds ok

bitmap: what needs to be done for jimmy to be ready as primary?

well, I wasn't sure if any other zfs optimizations were needed, but other than that, I think just need to write some migration steps

Can we do any earlier tomorrow? I won't be available past 6.30 PM

zas: if you're around after the meeting we could reboot some non-critical mb servers? to save time tomorrow/later

bitmap: ok

monkey: which time would work for you (and bitmap)?

we need to budget more than an hour.

15:30 GMT ? (30 minutes earlier than today's plan)

Ah.

Then 15:00 GMT ?

we need an hour to prep and then we need a fixed time to tell people.

I could be around at 14 or 15 utc

this, we set a time and then the downtime starts 30 minutes later is confusing for users

mayhem: I agree, let's say 15 UTC and plan the downtime for 16UTC? and we'll start with BB stuff for Monkey to be free asap

Works for me. That'll be the clash server, for reference.

bitmap, mayhem: ok for that?

works for me

which day?

tomorrow right?

yes

sure. 17 CEST?

yup

in the calendar!

It is Monday, and you are likely to be eaten by a grue.

:C

We again have no mailed in reviews today, although I think yvanzo is off this week anyway, happy holiday!

!!!