#metabrainz

yes they have a customizable dialog for feedback

That's pretty neat, I must say

yup, https://docs.sentry.io/platforms/javascript/gui...

reosarevok: well, I did find a way to avoid a seq scan, but I overestimated how much it helps. for this artist, my "improved" query finishes in 37 seconds (rather than timing out after 60s :P)

bitmap: well, that's an improvement :p

But yeah, not great

So feel free to revert, and if you'd rather not revert between now and the schema change maybe apply the changes for now?

I guess we'll want to still make use of that *and* a materialized table eventually anyway

we can deploy the new tables before the schema change, though the triggers aren't quite ready yet so it'll have to wait for those

CatQuest, domra is featured on imgur today

with the materialized tables these has_by* functions are trivial and complete in under 1 ms

And the triggers themselves aren't slowing down stuff too much?

I haven't tested that yet, but it's something we should make sure of

slowing down writes by a little bit will be expected

uh great so imgur doesn't work on chrome either

oh os it's "we walue your privacy and I select "no thnks" to any cookie etc. and they showme gray box

hah

well if it's "agree to tackers or don't show anything" it's not really valid is it!

fuck thme i don't need imgur

found it on youtube for you

(I have a trick up my sleeve)

http://web.archive.org/web/20210318162745/http:... :D

jesus crist is tht what he web looks liek witouth adblockers

ah youtube viewo, cheers Lotheric

alastairp, ruaok: do we have somewhere to document things which might be useful while writing/reviewing code? for example, flask's treatment of `/` at the end of a route so on.

not yet. maybe a page on the wiki?

i was thinking we should probably have a document in the repo and add a note in the default issue template linking to that

which repo?

I like the link.

that's a good question. some things might apply to multiple repos other might be specific

which is why the wiki page might be good.

we can make sub-pages for python, perl, flask, etc.

yeah, that sounds good. let's do it with the wiki

wait, I think we have one of them already!

!m reosarevok for improving search help box

You're doing good work, reosarevok for improving search help box!

MBS-11374: Hide non-release level edits from release editing history https://tickets.metabrainz.org/browse/MBS-11374

alastairp, i did find https://wiki.musicbrainz.org/Development/Server... but that MB specific

chaban: I saw that, I thought I'd take a look at some point later. Not quite sure how that query would work, it should be doable I guess but it might be quite slow? bitmap might be better for it

can we just construct an edit search to link to?

No, because release linked edits include all those "non-release-level" ones

So I don't think there's a way to filter those. At least now

you can filter which edit types to include, doesn't that help?

Oh, I guess maybe in that way

Didn't consider that

[listenbrainz-server] amCap1712 opened pull request #1351 (master…add-missing-docs): Add missing api docs https://github.com/metabrainz/listenbrainz-serv...

_lucifer: haha, we stopped to have drinks just after I wrote that. sorry!