#metabrainz

[bookbrainz-site] MonkeyDo closed pull request #265 (master…Troubleshoot_errors): chore: updated the version of eslint dependencies https://github.com/bookbrainz/bookbrainz-site/p...

[bookbrainz-site] MonkeyDo merged pull request #373 (master…master): fixed margin issue of brand logo in mobile view https://github.com/bookbrainz/bookbrainz-site/p...

Project bookbrainz-site build #2663: passed in 2 min 10 sec: https://travis-ci.org/bookbrainz/bookbrainz-sit...

hommik!

mo’’in’

bitmap: I think https://tickets.metabrainz.org/browse/MBS-10652 is all yours!

MBS-10652: modbot notes containing links are not properly formatted when sent via email

$time_of_day everyone

\o reo

\ø

iliekcomputers: https://labs.spotify.com/2020/02/18/wrapping-up...

ruaok: interesting.

is there anything we can learn from the post (haven't read it yet)

success is scary. :)

good tips for operating at scale, which isn't our problem... yet/

I've skimmed it, but will read fully later.

>We processed ~5X the amount of data compared to the Wrapped 2018 campaign while spending 25% less overall for processing This was achieved by designing our system in a way that reduced group-by key operations, and reused the output of yearly jobs to produce top of the decade metrics.

that's pretty impressive

[musicbrainz-server] yvanzo opened pull request #1392 (master…fix-node-req): Document newly required version 10.15 of Node.js https://github.com/metabrainz/musicbrainz-serve...

totally makes sense -- good idea to design for.

iliekcomputers: so, good news. the upgrade to influxdb 1.7.9 seemed to work well. I need to make a few tests, to ensure that it did, but it seems so.

I also make a backup of the data and loaded the data back into a 1.2.4 instance, without problems.

the new version has more features for analyzing our data structure and ensure if we're doing things in a scalable way.

it will be good to use those tools to see what we need for greater scalability. and it appears that 1.7 is already more scalable than previous versions.

I'll prepare a migration doc today.

ruaok: how did you test it?

just a cursory query so far. I hope to actually load a full version of LB (including PG) on this test server so I can run tests and actually use the data.

ah

one thing to consider

the production version of LB is probably running an older version of the client

(when compared to master)

yes, indeed.

rough outline for starters.

looking sane to me

to upgrade the client, you'll make a pr against the production branch ?

ok, I'll flesh it out in the course of the day.

yes, currently doing exactly that.

okay.

the python bindings only changed from 5.2.1 -> 5.2.3

[listenbrainz-server] mayhem opened pull request #732 (master…upgrade-influx): Upgrade influxdb https://github.com/metabrainz/listenbrainz-serv...

[musicbrainz-server] yvanzo opened pull request #1393 (master…fix-tag-msg): Fix blog post link in generated git tag message https://github.com/metabrainz/musicbrainz-serve...

[listenbrainz-server] mayhem closed pull request #732 (master…upgrade-influx): Upgrade influxdb https://github.com/metabrainz/listenbrainz-serv...

[listenbrainz-server] mayhem opened pull request #733 (production…upgrade-influx): Bump version numbers https://github.com/metabrainz/listenbrainz-serv...

ruaok: the jenkins build will fail because listenbrainz_spark doesn't exist in production yet.

yep.

:/

but the regular two passed locally and I hope will pass online too.

hmm.

?

hmmms from you make me nervous. :)

oh no, what you say makes sense.

phew.

i was wondering what's stopping us from merging master into production.

two different branches is a bit painful.

it is, but is master ready to release?

I know that is our rule now, but we haven't done a release since putting that rule into place.

so technically, there isn't anything in master that should stop us from merging it afaik.

we have incremental dumps but the cron job runs in beta, so it shouldn't interfere.

however

I'm not really comfortable merging into production until we're ready for a release.

looking at the diff (https://github.com/metabrainz/listenbrainz-serv...), there's a merge conflict and it seems a good idea to do it.

if we need to hotfix something, we have a mess on our hands.

seems not a good*

ruaok: yeah, agreed.

however, we should prioritize it.

but I think this should be a top priority goal for us.

lol.

yep.

while we're at it, it might be a good idea to discuss ways to remove this toil when i'm in bcn.

in general I need to bug others about joining us that weekend...

iliekcomputers: also, do we want to focus on bog standard LB stuff and push to make progress there, or should we also see about having Mr_Monkey join us and focus on some of the recommendation tasks that could benefit from his help?

ruaok: haven't thought about it much yet.

what is the recommendation stuff?

iliekcomputers: I found libxslt1-dev is installed in many of our Python projects, do you have any idea why?

git log didn’t really help as it is present in initial commit of Dockerfiles.

I found it is a requirement of lxml which is not used anymore but with mb-rngpy.