Notes from #MetaBrainz Meeting 2018-07-09

[Freso]

MetaBrainz Meeting 2018-07-09

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Song of the week:

Rebecca Black - Friday

(s/Friday/Monday)

Agenda

• Reviews

Reviews

@Leo_Verto

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leo_Verto

as mentioned in my GSoC proposal, I won’t be around for the meeting this and next week as I’m volunteering at a sort of summer camp but here’s my review for last week:
This week I set up Celery as a task queue for SpamBrainz (thanks for the suggestion, samj1912!) as well as an API token system and then started writing tests for both.
After moving things around and renaming them way too much I’m finally happy with this setup and should be able to pretty much plug the machine learning and report writing code into it.
I’ve also spent some time working with docker and feel like I’ve got a much better grasp on it which helped quite a bit with making the config system ready for containers.

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

This week the biggest (or most expensive) bug I have written was uncovered.

I guess @Rob will have more to say on that.
Anyways, I’ve been dealing with the aftermath
Fixing logging and reporting more errors to sentry to make sure stuff like this doesn’t happen.
Other than that, the usual PR reviews for @kartikeyaSh and @little_rsh
GSoC second evals start this week and @little_rsh has a good PR up that im gonna get to soon.

@chhavi

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

Managed to be productive over the weekend make some components. Pinged people for reviews on mockups.

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

mostly spent the week relaxing, reading up on the new tasks and background solr management
Mostly enjoying life in Bangalore
I’ll be tackling PG load balancing next
Solr has had a few improvement requests over this last week. Am going through them and fixing the ones that are high priority.
Apart from that typical week

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I finished some prs for converting the event & series search results to react
fixed an i18n bug related to the search form options being mistranslated
worked on writing tests for the new i18n string parsing/interpolation code
fixed a couple strings (instrument/link type descriptions) in the DB that had broken html and couldn’t be parsed
ah, and created a gdoc to compare some pg load balancing options

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

Last week, I spent a lot of time going through reported (spam) editors and compiling them into a neat list for @yvanzo’s (and possibly @Leo_Verto’s) consumption.
A few more to go to clear my inbox of those, but far most of them are there.
Other than that, mostly being around and about and handling reported users and content.

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

This week I did support and focused on looking into Community Cleanup suggestion: Women's Composer Database
Luckily, it seems a bit more active than last week, and with @loujin’s new help (at the end of that thread) it should get a bit better still
Plan for next week is mostly more of the same

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

I did a lot of cleanup in SOLR/Zookeeper installation docs, and splitted scripts
Also a lot of work on matching graphs, we have a nice dashboard now, with almost all needed infos
I did a bunch of system upgrades too
Grafana
A short point about how SOLR is performing atm
it works well, we don’t have any error, but response times degrade quite quickly during peak hours, we are cpu-bound atm
@samj1912 and i are investigating ways to improve the situation (without spawning more cpus)
the whole system is very stable til now, and handle single node downtime well. The main issue is that a SOLR node down during peak hours will cause some slowdowns
i’ll experiment moving zookeeper on non-SOLR nodes this week
but overall, we can say “it works!”
FYI, i’ll be travelling on friday (to Malta)

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

last week was paying people, accounting (mostly transferwise accounting setup and writing data import scripts)
I helped build VMs for yvanzo and worked on the conflict resolution protocol.
more PRs on LB and MSB, on which I am behind yet again.
then on friday I ran off to Nowhere for a short 36 hour stint to make sure my world isn’t too calm and nice.
saturday evening got a wee bit strange, chaotic, sad, frustrating and just WTF.
never in my years or going to burning events has it gotten that far chaotic.
it was great.
oh yeah, and I had to do some cleanup on some monster BQ bill. lol.

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

I worked on updating MusicBrainz VM mainly, opened a Vagrant Cloud account for further releases.
Also reviewed some PRs (thanks @legoktm), and worked on usual React/Spam stuff.
FYI, I won’t be available on Friday either.

@little_rsh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@little_rsh

I spent the starting days of the week working on @iliekcomputers’ reviews on #280 and #281, data insertion in musicbrainz schema was taking a lot of time initially which I have fixed now and it’s pretty fast now.
Then, I worked on keeping musicbrainz schema updated with the actual MB db and used replication packets for that and I have opened a PR for the same (AB-350).
This all was the major part of the project. We would next work on testing both the methods and then to decide which would be better for implementing features in AB.

@shivamt

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@shivamt

I worked on setting up recent imports page, and finishing up writing functions to interact with the import schema and update records.
I worked on mapping and finished off import section.

@kartikeyaSh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@kartikeyaSh

Last week I worked on reviews of LB-372, LB-373 and created PR for LB-381. So, part 1 of GSoC project done, now part 2 starts