#metabrainz

Hi.... I seem to be having some trouble with the live indexing. I'm getting: amqp could not commit tx mode on broker 1, reply_type=2, library_errno=4 in the replication.log.... The server isn't under any great load and there's plenty of memory available, so I can't really figure it out

Running the musicbrainz docker btw

I couldn't really find any information about it

Also just out of curiosity, what happens when the index_limit is exceeded? I tried to look through the code and it seems like the message is requeued? Sorry I'm still trying to understand how this all works. Maybe I can try to help if I can wrap my head around it

Good morning

atj: thanks for the ticket

ruaok: do web sockets for listens work on both beta n prod?

jasondk: Hi welcome :). Thanks for the contributions so far.

Good morning!

:o

\o/

👏 🎊 👏

shivam-kapila: they do work on both, but only if you submit your listens to the relevant API endpoint

e.g. if you submit listens to beta the WS updates on beta and not prod

I had to change my submission host in order to test if the issue occurred on beta

atj: oh cool. I will try to trace out the bug today itself after classes. I will ping you in case I need something. Till then can you share your LB profile?

_lucifer: that's awesome :D

(I still remember you as amkap thoguh :D)

thanks CatQuest :D

CatQuest: that's still his github :)

hench why I recognised it :D

_lucifer: tell me when you want to talk

I have about an hour this morning available

Hm 1712. 🤔 Is your bithday on 17 dec _lucifer

shivam-kapila: it's the year that he was born

:O

Oh. He looks so young

december kids unite?

alastairp: shivam-kapila: neither, that of that actually :)

aw

alastairp: how about now?

Looks like he got capt america's formula

_lucifer: give me 10 minutes

👍

shivam-kapila: nah, you are welcome to talkk mess with e.g me (I no work officially either :single_tear:)

shivam-kapila: i am almost sure its the same ws bug fixed a few days earlier or at least related to it.

CatQuest: haha thanks

_lucifer: i am also sure. Hence the first step would be tracking the ws message

(though i have to go make food and do the dishes right now :P)

shivam-kapila: actually the ws message would be the same. the fix was done on client side

I know. The ws message would be helpful to know where is the msid in the dict (if it exists). I will disturb you for sure (but I have to attend online class :/ )

ah makes sense. 👍

alastairp: is it fine if i enable "Code scanning alerts" for cb repo?

sure, we can check it out

what does it do? Is it "potential security issues in the way you've written your code" ?

this is not the same as dependency upgrade alerts?

"Automatically detect common vulnerability and coding errors"

I have not tried it out previously for python projects but it has proven useful in my java projects

yeah, let's give it a go. it looks interesting

shivam-kapila: sure

[critiquebrainz] amCap1712 opened pull request #346 (master…code-scanning): Setup code scanning https://github.com/metabrainz/critiquebrainz/pu...

_lucifer: sorry. I'm here now

no worries, let's start then :)

yvanzo: hi, please let me know when you're around

[critiquebrainz] amCap1712 merged pull request #346 (master…code-scanning): Setup code scanning https://github.com/metabrainz/critiquebrainz/pu...

ruaok: what servers should _lucifer get access to? all of them?

_lucifer: MBH-549 for now, open a ticket like this

MBH-549: Give alastair access to all servers https://tickets.metabrainz.org/browse/MBH-549

generate an ssh key-pair and attach the public key

I think for starters we should let him have access to lemmy, frank and trille?

on it

by then we'll know what servers you need

I'm thinking access to application containers, but not DB just just yet.

ok

boingo (ab prod) and frank (ab labs, ab beta) too?

frank also has ab db though

we could always move beta to boingo

alastairp: should i attach the public key to the ticket or send it to zas?

a public key can be freely shared, so I don't think there's a problem to attach it on the ticket

👍

I think when I got mine set up I just pasted it in here

done

atj: hey, CatQuest (FF 44, so also not supporting new URL) is seeing issues with pasting a specific url in beta that works in production

Or any url, not sure :D

Do you think maybe there's something borked in your try catch?

prod works fine

CatQuest: you're ruining it

what's the console log say? you should see an unhandled error

Apparently it just... hangs the browser, they said

So not sure how easy it will be to check console :D but :)

alastairp: the right thing to do is to add the public key to syswiki. hang on.

oh, interesting. I'm not sure if I ever added a key to syswiki :)

zas did.

...

_lucifer: can you see that repo?

well sorry then

CatQuest: :)

basiclaly it worked fineand now it doesnt, I'm not the one.. oh wait not serious

ruaok: yes

also, can you see this repo? https://github.com/metabrainz/docker-server-con...

yes, i can see both of those

_lucifer: add your key there and open a PR for it.

i can't tell you any logs because the entire browser just segs

CatQuest: come on, you really thought that was serious!

sorry but onlyine

segs as in segfaults?!

the docker server configs one is all about deployment stuff that we'll toss you into soon.

ruaok: neat. I don't think we have a HowToSetUpNewContractor.md in syswiki, right? sounds like a good thing for _lucifer to start work on, given that he's going through these steps now

it just hangs and has to be force quitted

ruaok: yeah, I've given him an outline already, we'll do a CB deploy togehter once he has access

Anyway, atj, any chance you can manage to test this a bit in either an old FF or IE or something?

I can try to figure it out myself, but :)

Probably easier for you if you have time

reosarevok: you can ask many things of me but using IE is a step too far

I mean, for testing only :) But I assume you're on Linux and that's not too doable

FF 44 might be

I'm on MacOS and Linux

https://ftp.mozilla.org/pub/firefox/releases/44.0/ :)

(and that's the one we know struggles atm)

I think it's fine if it doesn't do all the url magic in FF44 anyway, but it should at least not crash :D

yeah, that's why I added the try/catch!

I know! :D

But were you able to test it? I know I didn't test it... :)

for all we know it's probably *that* that breaks it :D

I know bitmap had it dl but

I did test it yes

🙏 thank you for humouring my old browser

Hmm. Wonder if *that* depends on something that still doesn't work on 44 :D

according to MDN try/catch was added in FF 1!