alastairp: you told me I should use v2.1_beta2 for AB compatibility. How essential is that, and could I use a later tag? I had to apply some patches to fix build bugs, and I think this would not be possible with beta3. And there are even beta4 and 5.
*not be necessary
zas
hey, outsidecontext, I'll have more time starting next week, would you be available for Picard releases?
outsidecontext
zas, yes, I think so. I had not much time for MB stuff the last weeks. Still don't know if it really will get better, but I'll take some time
Getting a running macOS streaming extractor for macOS would be something I'd like to have finished for the release, so we can ship it with the macOS builds
But actually it looks good now
zas
good timing :)
so we target both 2.6.4 and 2.7b1 perhaps first one on tuesday, second one on thursday ? or?
outsidecontext
yes, I'd say something like that. I would not do them exactly on same day
tandy[m]: I'm only working on getting a more up-to-date build for it for macOS, because the old one is build with very old SDK and we cannot ship it with Picard (which we'd like to do in the upcoming 2.7 release). Apart from that I basically know nothing about the code :D
outsidecontext: yes, 2.6.4 tree looks good, only fixes, nothing to add
outsidecontext
tandy[m]: yes, that's actually a very nice PR that should be merged IMHO. What we do with Picard is actually an alternative approach, were we make Picard a submission client, so with that there will also be a cross-platform GUI.
The Picard implementation was also done by gabrielcarvfer (who did the PR you linked)
tandy[m]
outsidecontext: coool that makes sense
im just waiting on an ARM build so i can submit acousticbrainz features from my music server
outsidecontext
the essential thing for this is to get that essentia extractor binary compiled. From my side there will likely be no ARM build for now, but maybe later
tandy[m]
outsidecontext: i see, maybe il have a look into it one day
outsidecontext
for now I just want to have automated builds for (x86) macOS at https://github.com/phw/essentia-extractor-builds/, because that's what we need to ship the current Picard package. But ideally this would end up to produce builds for different platforms and architectures
I'm sooo glad that we have UI experienced people on our team now!
also, mooooin!
zas
mooin ruaok
ruaok
zas: I've pretty much stopped paying attention to the wall of notifications that are coming. that is really less than ideal.
how soon can that be improved so that we split them into two channels: critical and non-ciritcal alerts?
zas
well, most alerts are critical, like disk space < 10%, but I will tune them to not trigger when those are meant to be transient. The /boot alert is due to the small separate partition, so it happens when upgrading kernels, I think I'll just make a separate alert for those, with longer delay to trigger
unusual disk write latency alerts are due to uncontrolled processes, and I already tuned them, I'd say that's the core problem that needs a fix, not the alert
ruaok
ok, let me put it in another way: the current setup is broken and I turned off notifications.
zas
?
broken? how?
ruaok
every time I look at a notification, and there are many many, I look at the impacted service and everything is fine from an outsider perspective. if the public facing services are not impacted, I dont feel that I should get a notification. You, yes. But me? I'm looking for critical things, not diskwrite latency issues on our FTP server. so, I stop notifications.
for me the current setup is broken. and you telling me it isn't broken doesn't improve things for me.
zas
actually disk latency issues have a very significant impact on FTP service, it takes up to 1 minute to connect to server when it happens...
ruaok
ok, in that case, what is my course of action to react to the notification and stop this from happening?
zas
well, I asked to move the concerned processes elsewhere, or to ensure they don't eat all resources, changes were made for that, but for now, without enough impact
ruaok
ok, so there is nothing I can do in the short term? I must put up with spammy messages until this problem is resolved?
zas
we can silence alerts for some time
I'll tune some (like clock skew alerts we got recently)
ruaok
and how do I stop getting spammed when this happens in the middle of the night?
exactly. clock skew is not something worth sending me a message at 4 in the morning.
zas
for that, you have do not disturb mode
ruaok
ok, we're clearly not communicating. lets leave this be -- in the meantime I've disabled all notifications for all time.
zas
I tuned some alerts, they'll not trigger if the problem doesn't persist long enough
it's up to you, I'm also annoyed by alerts, but those trigger when an actual problem appears
ruaok
the thing is, I want to help you monitor our site, but if this is the way to do it, then I'm really not interested in helping.
@lucifer: Should we merge the username search functionality now?
lucifer
akshat: sure, once ruaok has re-reviewed the PR.
ruaok
I can do that in a bit.
lucifer
great, thanks!
akshat
Cool
ruaok restarts tests on that PR
zas
yvanzo: I'm thinking about upgrading solr cloud VMs, likely by creating a new set of VMs with upgraded system & apps, it would be a good time to upgrade solr itself, can we discuss this matter this week? It will require few changes in installation scripts to adapt to netplan & new versions of apps used in the (complex) setup
also we need to ensure dns names are used on mb side (if IPs are used, we'll likely need to change this first)
ruaok
lucifer: "Oh sorry. I should have added more context. I have implemented actual user search in a different PR. Let me finish that up and see how we can fix this up."
is that still relevant on #1627?
lucifer
that's fixed up now.
search box has now been added to 1628.
ruaok
the conversation with monkey on listenbrainz/webserver/templates/user/base.html hasn't been resolved it seems.
lucifer
i think we are not on the same page. we were talking about 1628. that's the PR to be re-reviewed.
[listenbrainz-server] 14MonkeyDo merged pull request #1608 (03master…monkey-brainzplayer-scrobble): LB-606: Submit listens when playing music with BrainzPlayer https://github.com/metabrainz/listenbrainz-serv...
lucifer
time to release :D
uh, i forgot the thing about websockets PR.
it needs zas to update LB nginx prod config.
zas: could you please apply the socket.io mapping you made on LB beta to LB prod as well?
BrainzGit
[listenbrainz-server] 14MonkeyDo opened pull request #1634 (03master…monkey-fix-long-track-names): LB-952: Improve ListenCard layout with long track names https://github.com/metabrainz/listenbrainz-serv...
