I mostly did support, editing, and trying to enjoy the last days of summer (e.g. more camping)
2018-08-20 23258, 2018
reosarevok
I also helped CatQuest a bit (with a delay)
2018-08-20 23200, 2018
Dr-Flay
You can't tell if an experimental musical instrument will become more than an oddity, until it is no longer experimental and more people use it. eg the Theramin
2018-08-20 23214, 2018
reosarevok
Dr-Flay: hence "demonstrate actual usage" :)
2018-08-20 23229, 2018
Dr-Flay
by their nature an experimental instument may be unique
2018-08-20 23234, 2018
reosarevok
That's about it for now, but summer is finishing sadly so I'll be back to staying at home looking at the rain
2018-08-20 23239, 2018
reosarevok
slash screen
2018-08-20 23246, 2018
reosarevok
So you'll see me more, probably!
2018-08-20 23252, 2018
reosarevok
Freso: you? :)
2018-08-20 23212, 2018
Dr-Flay
well, youtube has some weird experiments, like the dude that made a guitar from old 8bit kit
2018-08-20 23213, 2018
Freso
See you more, or see more you? ( ͡° ͜ʖ ͡°)
2018-08-20 23217, 2018
Freso
Anyway.
2018-08-20 23217, 2018
reosarevok
Dr-Flay: agreed, but let's continue after the meeting (so, in like 30 min maybe? :) )
2018-08-20 23218, 2018
Freso
🙋
2018-08-20 23223, 2018
Freso
Yes plz.
2018-08-20 23256, 2018
Freso
So I herded and reviewed a number of final GSoC blog posts.
2018-08-20 23234, 2018
Freso
I haven't been much involved with GSoC otherwise, so it was great to get this chance to get a slightly more in-depth look of what y'all've been up to the last few months. Great stuff. :)
2018-08-20 23230, 2018
Freso
I also registered myself as attending the GSoC mentor summit as our designated GCI mentor/admin, so after seeing iliekcomputers and yvanzo in Barcelona in 1½ months, I'll be seeing them again in ~2 months. :p
2018-08-20 23241, 2018
iliekcomputers
Freso: <3
2018-08-20 23248, 2018
iliekcomputers
looking forward to that :))
2018-08-20 23215, 2018
yvanzo
See you soon!
2018-08-20 23219, 2018
Freso
Other than that, mostly being around and about, handling spam, etc.
2018-08-20 23232, 2018
Freso
fin; yvanzo, go!
2018-08-20 23250, 2018
yvanzo
Hi!
2018-08-20 23202, 2018
yvanzo
Released a MusicBrainz server update along with a new slave server virtual machine.
2018-08-20 23226, 2018
JaredCE has quit
2018-08-20 23227, 2018
Freso
(Only bitmap and zas left on my list. So few people now all the GSoC'ers are no longer obligatorily giving reviews. :'( Remember that you're free to give reviews regardless!)
2018-08-20 23232, 2018
yvanzo
Reviewed GSoC project SpamBrainz by Leo__Verto, and pull requests by bitmap.
2018-08-20 23244, 2018
yvanzo
Worked towards JIRA SSO, boosted by legoktm's own work towards Wiki SSO. :^)
2018-08-20 23254, 2018
Freso
yvanzo: NicE!!!
2018-08-20 23255, 2018
yvanzo
Continued converting UI code to React, and updated guess case/guess featured artists.
2018-08-20 23257, 2018
Freso
*e
2018-08-20 23209, 2018
Freso
!m yvanzo & legoktm
2018-08-20 23209, 2018
BrainzBot
You're doing good work, yvanzo & legoktm!
2018-08-20 23227, 2018
yvanzo
Acabado, go bitmap?
2018-08-20 23234, 2018
bitmap
hey
2018-08-20 23209, 2018
kartikeyaSh
Freso: i'm up
2018-08-20 23227, 2018
bitmap
mostly worked on some prs for the react migration, submitted one for the artist merge ui and converted some knockout bits
2018-08-20 23244, 2018
bitmap
fixed some bugs related to the recording video icons and standardized where it's displayed
2018-08-20 23255, 2018
Leo__Verto is now known as Leo_Verto
2018-08-20 23241, 2018
bitmap
looked into some memory spikes with the webservie containers and found an issue with the /ws/2/discid endpoint, submitted a pr to limit the amount of data it returns
2018-08-20 23251, 2018
zas
\o/
2018-08-20 23226, 2018
bitmap
just code review other than that. fin, zas?
2018-08-20 23232, 2018
zas
Hey
2018-08-20 23206, 2018
zas
we had issues with burnside, which was replaced by a better server, most of the hassle handled by ruaok & hetzner techs
2018-08-20 23246, 2018
rsh7
Freso: i'm up for the review.
2018-08-20 23249, 2018
zas
also we had issues with diskspace on prince, due to some obscure bug in docker, fixed now
2018-08-20 23258, 2018
zas
renewed *.mb.o cert and deployed
2018-08-20 23235, 2018
zas
migrated all domains to gandi V5 (and what they call LiveDNS)
2018-08-20 23254, 2018
zas
Picard PRs reviews & patches
2018-08-20 23209, 2018
zas
merged and deployed picard plugins fixes
2018-08-20 23236, 2018
zas
plus usual stuff, upgrades, and a lot of MB edits
2018-08-20 23243, 2018
zas
fin. kartikeyaSh ?
2018-08-20 23248, 2018
kartikeyaSh
hi
2018-08-20 23206, 2018
Freso
(Only rsh7 left on my list now. Last chance for anyone else to speak up!)
2018-08-20 23212, 2018
kartikeyaSh
This week I didn't do anything on MessyBrainz. But I read a lot of data structure problems for the interviews. Now I can create a linked list from a binary tree (without using extra space). I can convert stack into a queue blah blah. Don't know why on earth I'll do that. Once I'm free I'll work on MsB PRs to get those merged.
2018-08-20 23213, 2018
ruaok also prods LordSputnik and yvanzo about gsoc evals
2018-08-20 23217, 2018
kartikeyaSh
fin
2018-08-20 23224, 2018
bukwurm
Freso: Me!
2018-08-20 23225, 2018
kartikeyaSh
rsh7: go
2018-08-20 23235, 2018
rsh7
Hey!
2018-08-20 23236, 2018
LordSputnik
ruaok: I'm writing my feedback now :)
2018-08-20 23245, 2018
rsh7
Last week I filled the final evaluation and completed the blog post.
2018-08-20 23204, 2018
rsh7
And then came back to work on open PRs (before gsoc). I would complete some left over work of AB-98 this week now.
And regarding the evaluation PR, after I get a review from iliekcomputers , we'll complete it soon.
2018-08-20 23242, 2018
rsh7
fin.
2018-08-20 23251, 2018
rsh7
bukwurm: ?
2018-08-20 23251, 2018
Freso
bukwurm: Go. :)
2018-08-20 23202, 2018
iliekcomputers
rsh7: asap, sorry. I totally forgot about that with the dump PR and the spark stuff.
2018-08-20 23207, 2018
bukwurm
Hey everyone!
2018-08-20 23222, 2018
bukwurm
This week I worked on the PR reviews.
2018-08-20 23243, 2018
bukwurm
Fixed some bugs
2018-08-20 23200, 2018
bukwurm
Working on some remaining features
2018-08-20 23218, 2018
rsh7
iliekcomputers: no issues 😅. Let's get it done this week.
2018-08-20 23232, 2018
bukwurm
Most of the PRs are merged now
2018-08-20 23245, 2018
bukwurm
Some changes are remaining on the site, part.
2018-08-20 23250, 2018
Freso wonders if Leo_Verto / Leo_Verto[m] wants to chime in with something too
2018-08-20 23258, 2018
bukwurm
Which I aim to finish off this week.
2018-08-20 23202, 2018
bukwurm
That's it for me.
2018-08-20 23207, 2018
Freso
Alright.
2018-08-20 23223, 2018
LordSputnik
bukwurm: did you see my comments about the memory leak? I managed to get stuff into the queue now, but the consumers are encountering lots of errors to do with the link_import table PK being violated
2018-08-20 23229, 2018
bukwurm
Yeah
2018-08-20 23233, 2018
Freso
No one else has said they want to give a review and we don't have any further items on the meeting agenda for tonight.
2018-08-20 23237, 2018
LordSputnik
I can go
2018-08-20 23255, 2018
Freso
So thanks for your reviews and for your time... alright, LordSputnik, go. :p
2018-08-20 23257, 2018
LordSputnik
Haha
2018-08-20 23200, 2018
LordSputnik
This week I worked on entity editing
2018-08-20 23209, 2018
LordSputnik
I managed to successfully add relationships between entities on my local test site
2018-08-20 23228, 2018
LordSputnik
So the new relationship editor stuff is finally working
2018-08-20 23259, 2018
LordSputnik
I then worked out how to get it to work properly for adding relationships at the same time as entities are created (rather than just for existing entities), so I'm working on doing that now
2018-08-20 23231, 2018
LordSputnik
As a result of the improvements to editing I've been doing, we can now cut about 200-300 lines of code from the entity editing logic
2018-08-20 23238, 2018
LordSputnik
Which is a nice side-effect :)
2018-08-20 23242, 2018
Freso
🙌
2018-08-20 23256, 2018
LordSputnik
Apart from that, I've been reviewing bukwurm's work and also talking to Mr_Monkey about his work on webpack
2018-08-20 23200, 2018
iliekcomputers
rsh7: 🤟🏽
2018-08-20 23202, 2018
LordSputnik
fin.
2018-08-20 23209, 2018
Freso
Okay.
2018-08-20 23216, 2018
Freso
No people spoke up during LordSputnik's review.
2018-08-20 23224, 2018
Freso
So I think we'll actually really be ending here. ;)
Am I free to suggest some experimental electronic instruments if wanted ?
2018-08-20 23221, 2018
reosarevok
Dr-Flay: rather on #musicbrainz, but probably? :)
2018-08-20 23203, 2018
Dr-Flay
sorry just dealing with a masterserver support case
2018-08-20 23224, 2018
Leo_Verto
Oh hey, I missed the meeting! :D
2018-08-20 23240, 2018
Leo_Verto
anyway, not much from me last week (spent most of it working on home automation) but it looks like there's already someone interested on working on SpamBrainz for GSoC 2019 :D https://blog.musicbrainz.org/2018/08/14/gsoc-2018…
2018-08-20 23212, 2018
Gazooo has quit
2018-08-20 23225, 2018
Gazooo joined the channel
2018-08-20 23227, 2018
bukwurm
LordSputnik: Ok, so primary reason behind the errors is perhaps due to the reimporting of the same record
2018-08-20 23249, 2018
bukwurm
i.e. the record still exists
2018-08-20 23230, 2018
bukwurm
So, to handle this - we can perhaps add a check to get the link import record before pushing into the db
2018-08-20 23202, 2018
bukwurm
That way we can also ensure the timestamp is the latest
2018-08-20 23237, 2018
bukwurm
The error probably should go away once the primary key is unique for the records we are importing
2018-08-20 23237, 2018
bukwurm
I've updated the config sample
2018-08-20 23254, 2018
bukwurm
For handling the memory leak, we need to have a discussion on how to approach it in the best possible manner
2018-08-20 23209, 2018
yvanzo
Leo_Verto: It looks like the blog post URL changed since you submitted it to GSoC, it used to be on 2018/08/13, right?
2018-08-20 23216, 2018
bukwurm
I had a small plan, which I mentioned couple of days back
2018-08-20 23213, 2018
bukwurm
It was to use confirmChannel instead of simple channel
2018-08-20 23213, 2018
bukwurm
in rmq
2018-08-20 23235, 2018
bukwurm
It basically returns promise which resolves when the data has finally reached the queue
2018-08-20 23214, 2018
bukwurm
In this way, we can either pause the stream while a single message or a bulk of specified size has reached the queue
2018-08-20 23214, 2018
bukwurm
And then resume it later
2018-08-20 23202, 2018
bukwurm
LordSputnik: If there's any other way to handle the primary key errors on the consumer side in your mind, let's have a discussion any time your free.
2018-08-20 23206, 2018
bukwurm
*you're
2018-08-20 23227, 2018
LordSputnik
bukwurm: yes, I think that's what has happened - it's violating the unique constraint, not the "not null" constraint
2018-08-20 23253, 2018
LordSputnik
as for the leak - having promises which resolve when the data reaches the queue sounds like a good start to a solution
2018-08-20 23222, 2018
Dr-Flay has quit
2018-08-20 23222, 2018
LordSputnik
I'm not sure though
2018-08-20 23234, 2018
bukwurm
The reason why pausing the stream when the buffer is full will not work is, by default the size of the stream is 1.5 G per process. It will wait until all available buffer upto 1.5 is filled before returning false for buffer availability.
2018-08-20 23240, 2018
LordSputnik
Ideally we'd have a pool of outstanding promises and then only read new lines once promises started being resolved
2018-08-20 23209, 2018
LordSputnik
The size of the "stream" that the library is mimicking for sendToQueue?
2018-08-20 23213, 2018
bukwurm
LordSputnik: Yeah, that's what I meant by awaiting for a bulk of messages.
2018-08-20 23249, 2018
bukwurm
The default nodejs stream size
2018-08-20 23200, 2018
bukwurm
I think they're using standard streams, no?
2018-08-20 23235, 2018
LordSputnik
Going back a step - are we 100% sure what the cause of the problem is?
2018-08-20 23258, 2018
bukwurm
Anyhow, it didn't work when I tried to pause upon sendToQueue returning false.
2018-08-20 23226, 2018
bukwurm
LordSputnik: I am not 100% sure, but I definitely think that's the problem.
2018-08-20 23243, 2018
LordSputnik
Is it easy to modify the producer to run in the main process? Then we can profile the memory usage much more easily, I think
2018-08-20 23245, 2018
bukwurm
Disk I/O using streams exceeds Queue I/O
2018-08-20 23202, 2018
bukwurm
Modify how?
2018-08-20 23212, 2018
LordSputnik
Or have a separate testing entry point which just calls the producer with some arguments from the command line in a single thread
2018-08-20 23244, 2018
Leo_Verto
yvanzo, ah damn, I forgot the URL included the date. can we get that changed somehow?
2018-08-20 23244, 2018
LordSputnik
Then we can run that with node --inspect, and view the memory allocation in Chrome Dev tools
