#metabrainz

anyways, https://magicisrc-beta.kepstin.ca/ is coming along. It doesn't have the code to check or submit isrcs yet, but the login/logout functionality is in good shape and it'll load up a release.

just to confirm: test.musicbrainz.org is running on a copy of the db, so it's not an issue if I add some junk isrcs there while testing?

kepstin: yes, it is a separate db

Test OAuth Login https://usercontent.irccloud-cdn.com/file/oKrUz...

CatQuest , Freso: ^^

yvanzo, zas, ruaok, iliekcomputers, bitmap, reosarevok: ^^

moooin!

Mr_Monkey: `Access to script at 'https://unpkg.com/react-dom@16.7.0/umd/react-dom.development.js' (redirected from 'https://unpkg.com/react-dom@16/umd/react-dom.development.js') from origin 'http://localhost' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`

Moin moin! Also: drats!

if it wasn't for those meddling kids!

right?

Cor(s) ! I say!

afterall, scooby do taught me english. lol

I am scooby dubious.

as is my english, so fair point.

ruaok: Could you pull and try again? I've added some dependencies to static/js/lib instead of CDNing it.

I'm on aa840313b6 and I got loads of 404s.

babel-standalone_6-26-0.min.js:1 Failed to load resource: the server responded with a status of 404

Ah hang on.

Sorry, only half awake and hadn't realised the lib directory is gitignored. And off choice…

no worries.

backups are there, if you think about something that needs to be backup, provide node and path so i can configure it: https://docs.google.com/document/d/1uCmXs2Yx5ll...

There, better now ruaok. Please pull again.

that looks better.

YESS YESS. It worked.

Woop woop !

for the second go around it updated listening now, immediately, but the last listen took about 3 seconds to arrive.

not much to do about that, methinks.

Yeah, I've noticed some performance degradation. Not sure if it's on the front-end or back-end side

Not sure it's very important either.

I'm also thinking that for the play-multiple-users feature (needs a name. Inspiratron?) we probably only want to add listens, and not playing_nows.

not important now. part of it is that we're using this stuff on non-dedicated hardware without sufficient quantities of ram.

That way we don't need to deduplicate, and you're not forced to listen to random tracks that a user skipped after 10 seconds.

a proper server hosted infrastructure that is warmed up is likely going to give better performance.

yvanzo: /var/lib/docker/volumes/postgres-master-data on bowie isn't a dump, not sure it is worth to backup

Mr_Monkey: quite possibly.

this is all part of the semantics of the feature that are unclear to us. it will all be clear seconds after we release the feature. :)

:)

Those thoughts came after playing with it over the week-end

zas: right, removed

> Cannot perform operation; no list was loaded.

when I try to play a track.

401 error on calling spotify api

hi everyone! did anyone try installing the app.

ruaok: I get the "no list was loaded" when I first load (or reload) the page, and haven't yet clicked on a play icon in the list of recent listens

Basically, when you first load the page, the player is empty so clicking play on the playback controls begets that error. Something to improve upon.

understood. but I did first click on one of the rows.

so, its not just that case...

OK, just checking :) That's no good, then.

iliekcomputers, reosarevok: please ping me when you have a moment. (not urgent)

ruaok: ping.

ls

no match

whoops, wrong input box.

he, sorry.

lol

:P

first, the api-compat container is freaking out again.

yep, saw telegram, just looking at that.

did you just restart our redis container last time?

k.

and I chatted with bitmap about using the main redis. we should be able to do that now -- we were being cautious back then.

should I make a ticket for that?

yes, please.

we'll have to look if there's any data we want to move around... :/

i don't think there is anything but cache stuff rn.

you mean in order to preserve it?

yes.

also, what do you think of https://github.com/metabrainz/listenbrainz-reco... ?

even though the PR is small, it touches on a few points.

clearly using an ES mirror that drops older releases after one point release is useless.

but which mirror should we use?

the compat container is being problematic again.

no errors in the logs, this is a little weird.

ruaok: when back from lunch, let me know what you needed :)

the server seems to working in the container, but requests aren't reaching it...

it fixed itself just now. :/

weird.

"the brain seems to working in the container, but requests aren't reaching it..." new put down for absent-minded CS students

that hit closer to home than I'd like :P

>As new Spark releases come out for each development stream, previous ones will be archived, but they are still available at Spark release archives.

reosarevok: moved to email. See emails.

Seen then

I am not sure if the api compat thing is related to the code exactly.

amCap1712: hi tried installing the apk cna it wouldn't do it :(

"app was not installed"

also if I go to files it thinks it's a zip archive

CatQuest: did you uninstall the previous version?

CatQuest: I have tried on 4 different devices. it works on all.

alright i willremove the previous