#metabrainz

lucifer: nothing at all. all the good stuff has already been talked about (e.g. akshat)

Apart usual supervision, upgrades, etc... I tuned our nginx in-memory caching

ah makes sense.

traffic to backends (CAA redirects) is actually divided by 5

wow!

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

fin. akshat ?

I had an explosive week. Loved the work totally this time around!

https://community.metabrainz.org/t/musicbrainz-... 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

That's about it for me. Thanks!

yvanzo next?

hi!

(Only monkey and bitmap left on my list. Last call for anyone else wanting to give review!)

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.)

Go bitmap!

hey

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) - https://github.com/metabrainz/musicbrainz-serve...

and made a minor fix to the replication scripts in https://github.com/metabrainz/musicbrainz-serve...

later I released some new versions of base-image, consul-template-base, and docker-python using focal & a newer consul-template - https://github.com/metabrainz/docker-python/pul...

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

fin! go monkey

Hello !

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/...)

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

And that's mostly it for me !

Back to you Freso

Alright.

Thank you everyone who gave reviews. :)

We have a number of items on the agenda, so let’s try and be somewhat speedy. :)

lucifer: MeB Summit Planning

hi again!

hi

as you all know, the summit is this weekend. ruaok has updated the wiki page https://wiki.musicbrainz.org/MusicBrainz_Summit/21

and created a spreadsheet to track schedule and topics here https://docs.google.com/spreadsheets/d/15GKraub...

we have added some topics already. others also please add to this list.

i don't have anything else to discuss. if someone else wants to discuss something about the summit, let's do that otherwise proceed to next topic on the agenda.

Is there someplace that shows the starting time each day?

yes the first sheet

rdswift: yes, there is a schedule.

Perfect! Thanks.

6am Chicago time

bitmap agreed to it last year. its the same schedule.

that still ok, bitmap ?

yup, I'll be fine

k.

onward, Freso

Alright.

alastair: Sentry upgrade

hi

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

that's it. Freso: next?

alastair: syswiki

:D

hi

hi

another notification: this afternoon we experimented with moving syswiki to github wikis, and ruaok 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

that's it

Alright! Thanks alastairp :)

Freso: next meeting

So, we usually take the meeting directly after the summit off.

Any objections to doing that again this year? :)

none

Negative

i plan to take monday off

(That would make the next meeting be Oct. 25th.)

Alright. Seems like motion carried then.

Aaaaaand… That’s all for this meeting. :)

Thanks!

Thank you !

Thank you all for your time. Stay safe and not too cold out there!

</BANG>

[listenbrainz-server] 14amCap1712 merged pull request #1651 (03master…playing-now-controls): Fix playing now listen controls https://github.com/metabrainz/listenbrainz-serv...

we are doing the same apps and stuff lie klast year right?

A good part of syswiki is actually code, this is something we should address (but not sure how yet)

zas: yes, that came up. perhaps syswiki repo can be code, and syswiki wiki can be wiki

yvanzo: some sir issues in sentry, please tell me if you need time to revise these: https://sentry.metabrainz.org/organizations/met... (or lucifer?)

I wish I was involved in this move before... but ok.

bitmap: only a few caa bugs: https://sentry.metabrainz.org/organizations/met...

zas: its just an experiment for now. and nothing has been actually moved/removed from the repo itself.

ruaok: monkey: alastairp: fine if i do a release. a few UI fixes in there.

Yuss !

lucifer: go for it, but I'm not around until wednesday morning so I hope nothing goes wrong!

-> gone

👍

alastairp: thanks, I will revise them and ping you when done.

yvanzo: thanks, I expect we will update DNS on wednesday, as I'm not here tomorrow

[listenbrainz-server] release 03v-2021-10-11.0 has been published by 14github-actions[bot]: https://github.com/metabrainz/listenbrainz-serv...

👋

lucifer: I got it, still nobody's asked me what I was thinking about this experiement (or I missed the discussion), while I'm the top contributor to syswiki... weird feeling.

that said, any improvement is welcome, this thing is a mess for sure

lucifer: I had another look at why `user_name` is not present on listens page props, turns out I had the right idea but was looking at the wrong code:

We're manually creating a listen format that is not the same as the API listens (curcially, missing user_name)

crucially*

zas: agreed, makes sense. will take care in future.

monkey: ah right! will fix.

Thank yuo !

hm. the summit had a scheduled socila time for game palying after the main meeting part. as well. shan't we add this too

CatQuest: sure. i suggest to add to topics. we'll probably dicuss and finalize the schedule on summit day itself.

While you're in there making that change, this one should also probably be formatted by a common utility: https://github.com/metabrainz/listenbrainz-serv...

CatQuest: like last year :D

alastairp: bitmap lucifer : given that I want to add album cover art predominant colors somewhere so I can add the HueSound feature to LB, I the question: Where should that data live?

in the CAA schema of MB? a table in LB?

it doesn't really fit anyplace.

hrm. if it's dervied data that'd be useful to publish dumps for, caa schema might make sense

dunno if it would ever be useful for anyone but us.

any one better for better queries?

or simpler code.

I can't think of a reason why we shouldn't share it, I guess

Maybe people will find a use for it :)

if it lives in CAA, then we would need to provide RW access to LB to CAA.

or write the code in per in MB...

I'm inclined to stick it into LB and people ask for it, we can move it to CAA. thoughts, bitmap?

sounds alright to me, the feature is only useful to LB for now, so :)

if someone wants the data they'll ask

k, lets do that then.

ruaok: intending to work on this tomorrow?

lucifer: damselfish and I are trying to game the LB similar users alg. we're upset that we are no longer each other's top. so we're listening to each others top tracks today to try and fix it. I hope we won't get banned for it.

lucifer: yes, a tread for working on a holiday. :)

hehe lol.