#metabrainz

[musicbrainz-android] 14dependabot[bot] closed pull request #190 (03master…dependabot/gradle/androidx.compose.material3-material3-1.1.0-alpha04): Bump material3 from 1.1.0-alpha03 to 1.1.0-alpha04 https://github.com/metabrainz/musicbrainz-andro...

I'll remove the entry for frank

thanks zas

I removed few other obsolete entries (yehudi, prince, williams & frank), all corresponding IPs point to new servers.

I did a test for new discourse, and I was able to restore backups to new setup (running latest version). Though it isn't complete yet, I still need to set up a frontend nginx so we can run more than one website on this server.

I think we'll be able to migrate tomorrow afternoon.

It will require to set the current forums on read only, the time to do a backup, and restore it on the new server, then I'll do required DNS changes to point traffic to it.

lucifer: hi, how are you? I was thinking of trying to address this bug from yesterday. We discussed the failure queue, but another fix would be field length validation on data going into LB/MsB, what do you think?

bitmap: thanks, I approved the database PR in syswiki

yvanzo: hi, regarding per-project rabbitmq notes. I see that the sir notes are directly in the public sir repo. For LB I want to add some troubleshooting notes with private data, so I guess we could add these directly to syswiki? (in the same RabbitMQ doc, or maybe a separate one per project). Do you have a suggestion?

reosarevok: thanks I'll check it, and yeah I'd still like to put stuff on beta today

hi alastairp: The doc in SIR/LB repo is public indeed, addressed to everyone who want to deploy these; troubleshooting notes with private data specific to our infra rather goes to syswiki.

thanks for the confirmation, yvanzo

alastairp: It has a doc for RabbitMQ but that is rather about the instance. It also has an AlertDiagnostics/ which could fit if it is LB specific.

yes, that's exactly the perfect place to put it

[listenbrainz-android] 14dependabot[bot] opened pull request #43 (03main…dependabot/gradle/androidx.compose.material3-material3-1.1.0-alpha05): Bump androidx.compose.material3:material3 from 1.1.0-alpha03 to 1.1.0-alpha05 https://github.com/metabrainz/listenbrainz-andr...

[listenbrainz-android] 14dependabot[bot] closed pull request #26 (03main…dependabot/gradle/androidx.compose.material3-material3-1.1.0-alpha04): Bump material3 from 1.1.0-alpha03 to 1.1.0-alpha04 https://github.com/metabrainz/listenbrainz-andr...

[listenbrainz-android] 14dependabot[bot] opened pull request #44 (03main…dependabot/gradle/androidx.compose.material3-material3-window-size-class-1.1.0-alpha05): Bump androidx.compose.material3:material3-window-size-class from 1.1.0-alpha03 to 1.1.0-alpha05 https://github.com/metabrainz/listenbrainz-andr...

[listenbrainz-android] 14dependabot[bot] closed pull request #27 (03main…dependabot/gradle/androidx.compose.material3-material3-window-size-class-1.1.0-alpha04): Bump material3-window-size-class from 1.1.0-alpha03 to 1.1.0-alpha04 https://github.com/metabrainz/listenbrainz-andr...

akshaaatt: help needed

[listenbrainz-android] 1407jasjeet opened pull request #45 (03main…fix-sharedTestDir-jasje): Converted sharedTest to library https://github.com/metabrainz/listenbrainz-andr...

fish

reosarevok: i think i had checked in the database and the email there had been updated by then.

alastairp: hi! i am doing fine. i think we can add valiadtion at api level for clarity but having a reject queue would prevent such unforseen issues in future.

because we'll always miss some validation case it seems.

so i'd say do both.

Hi jasje!

How can I help?

akshaaatt: nvm i sorted it out and made that pr above ^^

you remember i shared that duplicate roots connected problem?

CatQuest: is the "fish" just a general-purpose word or is it like a call for me lool

yes

*confused fish noises*

🎉 https://test-chatlogs.metabrainz.org/ finally!

hello?

bah, fine. the actual logs page doesn't work. but css does! that was a mission

:D

!m alastairp

You're doing good work, alastairp!

It’s Draw a Dinosaur Monday!

I have received one mailed in review, so…

monkey: Go!

monkey says…

"""

Hello everyone,

I did’t do a whole lot last week as I’ve been AFK.

I did finish up on some docweek tasks on Monday, closed a couple more SEC tickets and reviewed some PRs.

On Tuesday on the train I opened a couple of PRs for the very first tasks of the ListenBrainz redesign (only structural for now, combining some of our tabs).

I’m still in Paris dealing with a lot of family drama, grief and funeral. That’ll be the case for at least another week. Please hold the line.

"""

If I could go on the list too please Freso!

lucifer: Go!

hi all!

I was mostly away last week. did a couple of PR reviews and small bug fixes for LB. that's it for me.

aerozol: next?

Mōrena!

Others up: mayhem, alastairp, yvanzo, atj, akshaaatt,reosarevok, bitmap, monkey, zas, vibhoo_24 , riksucks, jivte, yellowhatpro, Pratha-Fish,CatQuest (on vacation until jan), jasje, Freso – anyone else who want to give review, let me know ASAP. :)

I'm not on vacation!

I spent a little bit making my late contribution to the doc sprint, creating a bunch of tutorial videos, which was going to take a day

[narrator: it did not take a day]

:D

Turns out I knew much less than I thought about Picard, so those videos are still happening

That’s me, go reosarevok

Hi!

No review from me Freso. Hope u all had a great week :)

aerozol: the most important is to participate, not to arrive first ;)

Where are these tutorials aerozol? Planning to upload them somewhere?

Youtube akshaaatt, maybe on the MetaBrainz account, or on mine

Trying to hit the common search phrases

guys

Awesome!

theres a metabrainz youtube?

it's reo's turn

It's fine!

dang

reo can go :)

I spent most of last week looking into the documenting the artist API thing

Which is now kinda done at the basic level? I think? :D But more to go to make the schema and examples better

jasje: https://www.youtube.com/@metabrainz

subscribed!

I also worked a bit on small patches for the relationship editor

And on improving my PRs by following the actual PR template to make them clearer and easier to review

(some done, a lot to go)

CatQuest, who is not on holiday anymore: go?

Meow! `😺`

continued looking at backlogs and such.

I've added several bagpipes and will continue doing that.

Another reminder to everyone that if you are interested in a bagpipe (esp ones listed under "IROM") now's your chance to create a (sub)ticket: https://tickets.metabrainz.org/browse/INST-773

make sure it's not already in mb or already has a ticket in jira

INST-773: Bagpipes

also don't add novelties or ones with no info available, but else. go wild! ♑

♑

fin ΦωΦ, go Pratha-Fish 🐟

Hi all,

(Others up: mayhem, alastairp, yvanzo, atj, akshaaatt, bitmap, monkey, zas, vibhoo_24, jivte, yellowhatpro, jasje, Freso – anyone else who want to give review, let me know ASAP. :))

I tried updating the IRC logs this week, but nothing more than that unfortunately 🥲

Trying to balance a ton of things at once, but I'll be back soon :D

fin 🐟

alastairp: would you like to go next? :))

helo

(Still up: mayhem, yvanzo, atj, akshaaatt, bitmap, zas, vibhoo_24, jivte, yellowhatpro, jasje, Freso – anyone else who want to give review, let me know ASAP. :))

helo alastair.person.com?

last week I was continuing on some docsprint things which turned into yak shaving. I wanted to write some sysadmin docs about brainzbot and chatlogs, and noticed that we didn't have any backups for the logs database, and after a quick discussion with zas decided to go ahead and migrate the chatlogs app to the main metabrainz infra

along the way I pinged bitmap and he wrote a nice guide about how to create a new db in the main postgres cluster (thanks bitmap!), and Freso also wrote a brainzbot admin guide from the point of view of a moderator/admin (thanks Freso!)

that's mostly done, and I should finish tomorrow. also on the weekend we had a dodgy listen break the LB queue, which I debugged with lucifer's help, and started writing a help document to follow in case it happens again

that's it, zas next?

Hey

last week, I did an attempt to upgrade discourse, which ended in an heavy mess, causing a downtime for few hours

I managed to restore the forums

but I couldn't achieve the upgrade

so, I ordered a new server (mingus), in order to move discourse to it

the server is now configured, and I did a test today, which was successful.

With the help of bitmap, we cleaned up the production postgres db used by discourse, which had various issues preventing the full upgrade (many inconsistencies)

“couldn’t achieve the upgrade.... so, I ordered a new server” Dunno why, but that is very funny out of context :D

XD

also I got rid of unused plugins that are incompatible with new version (those also caused a lot of issues)

moving stuff away from google saves us money, so good move.

yes, sorry, the reason for the new server was to be able to test the new version upgrade, and move discourse to it afterwards to save money, and because current VM struggles at peak times since a while

apart that, I did usual supervision, PR reviews, user support, etc..

!m zas

You're doing good work, zas!

I plan to move to new discourse & server tomorrow

fin. mayhem ?

hey ho.

(Still up: yvanzo, atj, akshaaatt, bitmap, vibhoo_24, jivte, yellowhatpro, jasje, Freso – anyone else who want to give review, let me know ASAP. :))

I spent time learning react and working on troi daily jam improvements.

I also started working on artist radio style recommendations -- I think we have enough data now.

and the usual background MeB tasks.

akshaaatt: go!

Hi Everyone!

Last week we fixed some bugs on the LB android app and recently made a release.

I would like to test things a bit more internally before we have the blog out about the progress made on the app.

https://play.google.com/store/apps/details?id=o... Android users, do use the app and let us know your initial thoughts!

jasje: and I have been discussing things. Looking out on that front. I would also like to take some time in the next few days to finalise the scope of the app for the next few months

Atleast for this year, I don’t want to bloat features in the app, rather improve the UX and existing functionalities.

That’s pretty much it. Go bitmap!

hey

last week I finished writing the React state management docs for musicbrainz-server & submitted a PR for that

I also documented in syswiki how to add/configure a new database in our postgres cluster, which was tested by alastairp

other than that I worked on resolving the issues/improvements people reported in MBS-11847, plus a few other related tickets (MBS-12834, MBS-12849, MBS-12850)

MBS-11847: Port the relationship editors to React https://tickets.metabrainz.org/browse/MBS-11847

MBS-12834: Beta: Relationship type dropdown interferes with editing a relationship https://tickets.metabrainz.org/browse/MBS-12834

MBS-12849: Allow seeding the relationship target entity credited-as field https://tickets.metabrainz.org/browse/MBS-12849

MBS-12850: Seeding a backward relationship does not work https://tickets.metabrainz.org/browse/MBS-12850

hoping to release all that to the beta server today

oh, and also briefly helped clean up some broken indexes in the discourse database

that's all for me. go yvanzo