#metabrainz

yvanzo ?

ROpdebee, bitmap: any idea what could cause https://twitter.com/LatDorian/status/1389971318... ?

nelgin: IIRC yvanzo said he wouldn't be around a lot today, but leave the question and he might be able to help when he does appear :)

I did and still waiting.

Here it is again - https://pastebin.com/48HYrZPB (2nd attempt)

yvanzo: ^ when around

alastairp: https://github.com/metabrainz/listenbrainz-serv... any reason we run mkdir prior to WORKDIR. my understanding is that WORKDIR creates the directory if it does not exist.

>If the WORKDIR doesn’t exist, it will be created even if it’s not used in any subsequent Dockerfile instruction.

_lucifer: mmm, interesting. I guess I always just assumed that you had to create it before switching to it

I had a dream last night that I was hosting all participants in the MeB summit, because I had 7 bedrooms in my house, but when we got home I remembered that I already had guests and there wasn't enough space for everyone

Good evening everyone. First of all I want to congrats for the musicbrainz project. Finding such a big and detailed open database was pretty unexpected ahah.

Anyway, I'm working on a small project for my uni. As a starting point I need to place on a nice map artists and albums, but I don't want to annoy with details. The whole thing should work on nodejs. Now, I set up the local dev version of musicbrainz, it works, but now I'm really starting to think if interacting with that server and some of the

community api is more or less convinient that setting up the database on its own.

I'd like to hear what are the advantages of interacting with the server in spite of the direct database, and I guess that this is the best place to ask that. Otherwise tell me simply to go away ;3

calendaring is hard. even whle asleep.

mrtriad: depends on what you want to do

mrtriad: welcome! and thanks!

The database is always going to be more powerful

(since you don't depend on the specific combinations of data the API offers you)

But on the other hand, you need to maintain a database copy :)

If you don't care about keeping the data up to date and are happy with just a static snapshot, you might as well use the database you already have, I guess :)

That's not a big deal luckily. But yay, thanks for the confirmation.

A few more question since you are so quick ahah. First of all, I installed the dev version during the server installation, though it's not so clear what's the difference from the normal one. (it's not a slave, so it's not up to date, though there are also a few other version to choose and the dev one is much smaller than the others)

it has a tiny test database.

which won't be useful for your purposes of collecting data. useful for development and not waiting a long time for data to download.

do you have a list of artists for whom you want releases? how big is it?

Yeah, it's basically taking a bunch of big artists and the data connected to them, so that there's enough to play with

So, it'd work for you to test, maybe, but it won't help much otherwise

oh, k. Clear clear.

(also because if you want countries, that's missing some area to country connections)

Also to get the db as a stand alone should I download the big one as I set up the server or should I follow this git https://github.com/lalinsky/mbdata?

(hope that posting link is legal)

Sure, why wouldn't it be :) luks is a friend

Assuming mbdata is up to date, the question is: do you want to be able to use the website too, or do you just need the DB

I just need the DB

If the DB is enough, mbdata is probably all you need. If you want to have a copy of the website locally to view the data with and whatnot, then use the main server

oh, ok. Perfect ^^

Welp, that's it for now. Thanks for your support and the quick replies

ruaok: I'm not missing any recent changes wrt mbdata, right? :)

mrtriad: are you talking about using the mbdata db loading/replication functionality?

Just to make sure

reosarevok: it should be up to date. we use it in brainzutils

but it's 2 things: an ORM for accessing the database from python, and some additional tools to set up a database without needing to use musicbrainz-docker or mbserver

Hmm what do you mean by "mbdata db loading/replication functionality"? I still have to take a look at the mbdata functionalities. I guess that at the end of that I'll have a local postgre with the musicbrainz db. Am I right?

I never used the orm, but I remember using it to just get a DB ready back in the day when I didn't want a local MB copy

But this was... well, a long time ago :D

Maybe by now just using the docker files would make your life easier

mrtriad: sorry, I may not have explained that clearly. let me read your backlog

mrtriad: I understand that you set up the database with musicbrainz-docker? Does that work well for you?

I set it up without docker. But yay, it works

ah, right.

mbdata does the same thing - if you've managed to set it up yourself then you don't need it

Yeah, I guess if you already have all installed, you could drop the sample data, and install the main data, and that would be the same

Oh, ok.

Welp, thanks again :3

Have a nice day and good luck at keeping up the project ^^

[musicbrainz-android] akshaaatt opened pull request #69 (master…update_barcode): Update Barcode Scanner Library to Google ML-Kit Barcode Scanning https://github.com/metabrainz/musicbrainz-andro...

Hi _lucifer so apparently since jcenter has served its end, the barcode scanner library that we used to use needed to be switched since its creator had stopped the support and even the repo was no longer available, I have made the switch to the Google ML-Kit Barcode scanning library.

Hi nelgin: Sorry for not responding earlier, this is a SEARCH bug (happened in prod too), it is not related to your settings.

[musicbrainz-server] reosarevok opened pull request #2093 (master…MBS-11643): MBS-11643: Don't disable links that haven't ended yet https://github.com/metabrainz/musicbrainz-serve...

akshaaatt[m]: we cannot use google ml library or for that matter any closed source library. otherwise we cannot publish on fdroid.

reosarevok: RE that tweet, no clue. there's not much to go off, could be due to recent changes, could be similar to MBS-11621, could be something else entirely

MBS-11621: can't upload cover art https://tickets.metabrainz.org/browse/MBS-11621

regarding the end of jcenter, they have recently decided to leave it as read only repository indefinitely so no urgent worry on that end.

I thought of MBS-11621 but they say it works for most files

So it's probably something else, but no idea what

<_lucifer "akshaaatt: we cannot use google "> Oh! I didn't know this.

<_lucifer "regarding the end of jcenter, th"> Okayy, so I'll close my pull request then and mark it stale.

thanks!

[musicbrainz-android] akshaaatt closed pull request #69 (master…update_barcode): Update Barcode Scanner Library to Google ML-Kit Barcode Scanning https://github.com/metabrainz/musicbrainz-andro...

alastairp: should i merge https://github.com/metabrainz/listenbrainz-serv... and https://github.com/metabrainz/listenbrainz-serv... ?

_lucifer: 1424 has some pending work on it - I found some other issues

alastairp, regarding zipstream i checked its GPLv3. GNU's website says that GPLv2 and GPLv3 are incompatible so indeed we cannot use it.

searching on pypi for other zip libraries also doesn't turn up much only xtract and reusables seem usable and xtract is GPLv3. reuseables is MIT license. i'll checkout reuseables and see if it serves our purpose.

_lucifer: ok, it's a quick fix on 1424, let me do it now. it was related to my question about the new spark image

_lucifer: the reason for using a streaming library is so that we don't have to load all items into memory, then compress it, then send it (that'll make a request take a long time, especially for a large dataset)

another option would be to only allow users to do it for small datasets, but that's annoying too

how about moving the task into background and asking the user to check back later on a page that will get updated once the zip is generated?

we could say retain the zip for a week or so.

yeah, that was the other other option, but it has its own set of problems

yeah right

this issue also comes up in LB in listens export.

1) backend processing system, 2) notification system, 3) DoS/file cleanup

so... if we need it for 2 services... should we just implement it in BU?

yeah, i think that's the right way forward.

LB-324

LB-324: the export data feature currently does all its work in the webserver view https://tickets.metabrainz.org/browse/LB-324

well, let's put that on the list some time :)

just checked reusables its just a wrapper around zipfile, no streaming support there :(

hah, right

in order to close this PR off, we could run some experiments and come up with a limit... maybe 1000 items? and do it in the view

then open a new ticket/plan for background processing

yeah makes sense.

thanks!

oh, looking at my last commits that's exactly what I did

so let's run some tests on bono (there's an almost full db there) and see what a good limit is

alastairp, i think i do not have the permissions for acousticbrainz directory on bono.

i am unable to run any git command there.

sudo su - acousticbrainz

iirc i do not have sudo permissions on bono

>lucifer is not in the sudoers file. This incident will be reported.

you're in the sudo group now. log out and log in again

works now thanks!

great

1424 is ready, I'm just doing it now

thanks, i'll merge 1430 after 1424 and so that https://github.com/metabrainz/listenbrainz-serv... can be tested

alastairp, i do not understand why we need to add PYTHON_BASE_IMAGE_VERSION twice in 1424.

ah ok, just saw that if its declared before FROM it cannot be used after it.

_lucifer: I've been digging some more around those typescript issues (#1429) but didn't find a better solution than the commit you added.

I tried removing preset-typesrcript to use only plugin-transform-typescript but ran into issue with tsx and with libraries.

These issues should go away when Babel v8 comes out.

In the meantime this seems to work fine, so I'm doing a last round of checking before merging.

cool, thanks!

i wanted to merge 1430 before it so that it could be tested but since its working for you as well. we can go ahead and merge it.

[listenbrainz-server] MonkeyDo merged pull request #1429 (master…monkey-fix-typescript-compilation): Fix typescript compilation https://github.com/metabrainz/listenbrainz-serv...

I'll now update #1390