#metabrainz

:D

o/

That's about it really :)

samj1912: go!

Hello :D

go sam go!

this week *finally* announced solr beta

🙌 🎉

the blog if anyone wants to read https://blog.musicbrainz.org/2018/06/15/musicbr...

🎆🎇

week was mostly spent on getting solr prod ready

making it keep up with reqs/s other optimizations etc etc

fixed a LOT of things this week

opening up solr to beta also allowed our SOLR ticket tracker to get a bit more active

and I have been chasing inconsistencies in old search server for the past 2 days

!m samj1912

You're doing good work, samj1912!

they are mostly fixed and I will be announcing a consistent search syntax soon

👏 👏

apart from that, currently working on making the index more efficient, removing un-needed parts

and adding other things that were requested - aliases for rg,releases, recs. and being able to search for accented chars and punctuation

oh, also made some patches upstream to telegraf to fix our solr metrics

fin from me

chhavi_: go

Hiii, I added a few more components to the system. Will do the same the coming week :)

fin! bitmap go

hey

(People still up: Freso, zas, yvanzo, iliekcomputers, bukwurm, Leo_Verto, kartikeyaSh – anyone else, please let me know ASAP.)

was ill last week so I didn't make huge progress on any PRs, but I helped migrate containers off (and then back onto) serge, tried setting up a rabbitmq cluster (but ran into a snag), and code-reviewed chhavi's work and the LB user ID stuff (and probably not helping :))

god bedring bitmap!

that's a fin... Freso next?

🙋

CatQuest: thanks :)

I reviewed samj1912's blog post about the search beta and handled some reported editors and was otherwise around and about.

FresoBot keeps chugging along.

fin; Leo_Verto Leo__Verto: Go!

Thanks!

I updated my GSoC timeline, did my review, started work on building SpamBrainz' API and started working on comparing the spam data to the live one.

!m fresobot for fixing urls

You're doing good work, fresobot for fixing urls!

fin.

yvanzo, go!

!m Leo__Verto

You're doing good work, Leo__Verto!

Last week, I submitted the first evaluation of Leo_Verto’s project SpamBrainz to GSoC.

I finished reviewing bitmap’s PR and worked on React rewrite of editor account forms and small recent issues.

Fin, go zas!

hey

(In reply to dragonzeron: removing WP links by hand is not a thing.)

most of the week working setting up haproxy/solr cloud/metrics/grafana etc..

plus a lot load tests on solr

which should be ok for prod

*kill it with fire* tests :P

also dig reason of performance differences betwen identical VMs...

found out it comes from IBRS cpus, asked hetzner about this shit

no answer yet

(yvanzo: dragonzeron has been removing WP links by hand for quite some time now…)

plus usual upgrades, and fixed disk space issue on discourse server

fin. iliekcomputers ?

hi!

I did work on all three projects this week.

(Only bukwurm/bukwurm_ and kartikeyaSh left on my list – anyone feeling left out, now's the time to let me know!)

Did some work on LB restreaming our data to BigQuery, also kinda sorta started writing code for stats with the new schema on BQ, but need to discuss it more. Also, trying to import musicbrainz row ids into LB.

Finally merged a bunch of Pull Requests on CB and deployed them to beta. These included some schema changes that I had been putting off for long. Also, made a post about it on discourse. (go take a look). Also, been working on allowing users to delete comments.

Reviewed and merged Rashi's PR on AcousticBrainz, we're making progress on her project, i think. Still need to find a way to test this with prod data. I think import will probably be slow, but I'd like to see how slow. I think it'll be best to do after AB moves to hetzner?

Also, MessyBrainz code review: I read the clustering artists PR, it is a bit to take in. Will post comments today.

fin.

kartikeyaSh: go

hi

Last week I created a PR for LB-372 and wrote tests for the same. I did start working on creating release clusters, I'll create PR for it in a day or 2. This will conclude part-1 of the project. Now things seem clear to me and I believe I can speed up the work and get part-2 done at a faster pace.

LB-372: MessyBrainz: Create artist_credit clusters using artist MBIDs in database https://tickets.metabrainz.org/browse/LB-372

fin bukwurm /bukwurm_ go!

Last week I completed import process.

Presently cleaning up and working on commits.

Out of three classes, two dumps can be handled now.

There needs some work on the mapping and extraction of as much data as possible, which requires some manual working.

I have started work on tests and improving dumps mapping.

I have also started looking into second phase work onwards.

That's all for this week. :)

Thanks bukwurm and everyone else for your reviews!

No one's left on my list, so let's move on to…

Freso: Amazon cover art

🙋

Last week dragonzeron asked about getting our Amazon cover art fixed for some releases, which reminded me of a discussion we had at a meeting *ages* ago, about dropping Amazon cover art support entirely in favour of only displaying CAA images on MusicBrainz.

(Sadly, I couldn't find this meeting in our chatlogs. :()

This was discussed at some length in the forums since last meeting though, and it seems like there is a fair amount of our editors who wants to keep it for now:

So unless anyone else has something to add, I move for not doing anything for now. :)

And I don't see anyone peeping up…

I am generally for just slowly depreciating

So moving on in 3…

it

2…

1…

CatQuest: Quick question about instrument ticket decisions

me work

so Hi!,

In addition to the things I stated in my review, I also closed some tickets as invalid/nofix as they weren't possible to find any information about, and noone seemed to care/be interested.

I was wondering if I could, in the vein of the "decision required" for certain tickets we did some time back, occasionally, that is //occasionally// ask in the meeting about some instrument tickets I feel I need more consensus/feedback about before deciding?

How does people feel about that? yay or nay?

this would not be an often thing (I have one for next meeting perhaps but)

CatQuest: yay

samj1912: ok

CatQuest: If there's enough time at a meeting, sure. :)

obviously :)

(Tonight would have been excellent. Looks like we'll be done soon. :p)

oh becasue i have one

but it *can* wait until next time

Let's just get it done now.

hmmm

If you don't have any more for this topic?

not at lal, jsut wnated peopel to say yay on nay

but i mena it requires peopel reading https://tickets.metabrainz.org/browse/INST-24

INST-24: Backwards electric guitar

som aybe jsut put it in the topic

so peopel cna read it at their leasure first

Alright.

CatQuest: So no more for this topic?

not at all. just wanted people's oppinion

eh. attention :)

:'D

Looks like the people that had one has given it. :)

Alright!

Thanks for your time people!

Clocking in just under half an hour! :o

Thank you freso :)

</BANG>

thanks Freso :D

the encoding problem seems to be a MusicBrainz bug.

lol :P

freso: what should i call it: instrument decision INST-24 or full url?

INST-24: Backwards electric guitar https://tickets.metabrainz.org/browse/INST-24

silly bot

so, due to the move to Solr, WS/1 search will break

CatQuest: "DR: INST-24"?

not full url? alright

on the original blog, we announced we will remove it in August

bitmap: the data I get for this user is

CatQuest: making forum/poll post to get interest/information about an instrument request might be another option

so the first question - do we wait till august to gett solr to prod?

I put in full url to make people easier to click

or do we let it break ws1 search

CatQuest: That was the format "back in the day", IIRC, and the "INST" part let's people know right off the bat that it's an instrument ticket.