on servers which have ~/.shh/docker_server_configs_key, I separated them
yvanzo
zas: id_rsa on all hosts do match these deploy keys
("all" that I checked)
maybe not on newer servers
rdswift has quit
jasje
for example
the listen Small by Portishead
mayhem
That would explain it.
bitmap
I'm fine with having to specify GIT_SSH_COMMAND in any case, it was just unexpected
jasje
is 6.45 minutes long
mayhem
Do our docs state which is correct?
jasje
6.45/2 ~ 3 mints
mayhem
Gtg. Bbib.
zas
ah got it, I usually use a specific key and change config to have a shortcut
yvanzo
yeah, if you don't specify a shortcut, it uses id_rsa
monkey
Negative, here's what the LB docs say:
>The payload should also include the listened_at element, which must be an integer representing the Unix time when the track was listened to. The minimum accepted value for this field is LISTEN_MINIMUM_TS. playing_now requests should not have a listened_at field
zas
yes, the main issue with this approach is that you have to clone with the "shortcut" instead of github.com
so I guess we can't really avoid that (after it does what the user asks)
jasje
when should the ts be taken then?
yvanzo
Ok, I will review hosts listed in docker-server-configs at least
jasje
start seems good to me
yvanzo
bitmap: It's not needed on other hosts (which just have their identity file as id_rsa)
jasje
but doesn’t accurately represent when the actual listen was submitted
monkey
jasje: IMO at the start is correct
bitmap
yvanzo: ok, I thought I had created a separate deploy key on a few other servers too, but maybe it was for docker-postgres-cluster
monkey
Ingested listens will also have an `inserted_at` field added to them
perhaps there are better options, but basically it links a deploy key to a specific name (hence the "shortcut"), since the "Host" can be used in place of normal one (usually git@github.com)
mayhem, I’ve triggered a beta release of the app with new ui/ux which should fix the issue of configuring the scrobbler and ease the pain that user goes through
Do join the beta program for the app on the playstore
I’ll inform you and others when it’s available
mayhem
how do I join the beta program? I've got the app store page open
on the question as to when to submit the listens, we should do the same that last.fm does --that way scrobble programs need to have less customization
kellnerd
reosarevok (or whoever leads today's meeting): I won't be around at meeting time since it's a public holiday here and we're barbecuing.
I couldn't find the damn button, because I am already signed up. time to slow down and read. lol.
reosarevok
<BANG>
Welcome to Monday Mayhem with me, and I guess also mayhem
Today everyone is being lazy (good for you!) and we have not one, not two, but three mailed in reviews!
CatQuest
ara?
reosarevok
kellnerd says:
'''
Last week I've fixed two BB bugs before the release, one was caused by Safari's inability to keep up with browser standards, the other was my own ;)
mayhem
CatQuest: now
reosarevok
Time to fully get back into BBusiness this week by starting with my GSoC project, yay!
'''
CatQuest
?
reosarevok
atj said:
'''
mayhem
!
reosarevok
No he did not say !
Please, you two, let me post these :)
atj said:
'''
Last week I continued working on preparations for the consul migration with zas. This included writing a new role to install and configure unbound, resolving an issue that caused consul not to be started on boot and implementing new functionality to manage consul script checks. We also did a fair bit of testing and it looks like we're pretty close to being ready.
I also spent some time looking for summit accommodation and discussing options with mayhem.
'''
And our usual mailer aerozol said:
'''
Bits and pieces this last week.
Clarified the auto-editor election process with reosarevok. Drafted some dataset attribution guidelines with mayhem. Tweaked some Weblate colours and icons with yvanzo.
A bit of community stuff, some more MB guideline drafting.
A short review from me this week, who would have thought! Go… bitmap!
'''
so, go bitmap I guess? :)
bitmap
heh
hello
last week I was mostly working on improving our postgres cluster for high availability so we can perform switchovers with no downtime
I spent time testing and improving the (currently unused) haproxy container in the docker-postgres-cluster repo, plus the associated health checks for determining whether a node is primary or standby
this is still in the testing phase, but perhaps we could deploy it next time we ugprade pg (maybe in lieu of next schema change)
reosarevok
[insert "i know some of those words" meme]
bitmap
I also submitted a pr for MBS-13015 and did a small amount of code review
I spent quite a bit of time improving our JS tests
Still a lot to go
Other than that, tiny bit of code review, a fair amount of community management
Few small tickets
I also sat on the board meeting for Q2 which was uneventful
I think that's most of it - CatQuest, you?
CatQuest
Arararara~! hi!
Figured out some monkey stick/stump fiddle mess
Uploaded quite a few images with reo
working on adding another instrument right now
and tested the new ✨ Alias Locales!✨ ♉
reosarevok
CatQuest: now?
reosarevok hides
CatQuest
thanks yvanzo and reo for such fast deployment
reosarevok
Oh, yeah, I also helped upload some images ^ :)
CatQuest
I'll be a bit more afk in the coming weeks. But i'l be around.
and ya are jsut going to have ot get used to me going "ara"
ut it's JP not Ca
uh next can be ...
fin, go Pratha-Fish 🐟
hmm
zas then
mayhem
what does ara mean in your context? around here it means 'now'
CatQuest
uhm..
monkey: can explain better thna me i think
and if zas is not around, thne monkey can go
monkey
Hello !
Last week I merged some BB PRs, did a bunch of beta testing, some fixes, and deployed a new version of BB
Also reviewed PRs for BB, particularly working on the revision reverting
zas
I'm around btw
reosarevok
Oh, I forgot the list for today: zas, mayhem, yvanzo, lucifer, akshaaatt, Pratha-Fish, riksucks, jasje, jivte (GSoC students, if you're here ping me and I'll add you too)
monkey
On the LB front, I worked on improving and fixing playlists
Did some ticket triage, fixes tiny bugs
And talked more about the redesign and new recommendations page
That's the gist of it. zas can go now :)
zas
Hey
last week was mostly about preparing the most to new consul cluster
monkey
ara ~= "oh dear" I guess
zas
as atj said, we're getting very close, I expect to do it this week
monkey
OR "oh is that so?"
CatQuest
or waait? huh? i think or as an exlamation of surpise
reosarevok
Ok let's let zas continue :)
CatQuest
👍
zas
We had another problem after docker upgrade (this time minor version one) resulting in broken net stats
it happens last time (major version upgrade), so we thought it was because of that, but apparently something changed in docker that causes live-restore to not work well
that's very annoying, because the only way I found to fix it is to restart containers after the upgrade, and basically that nullifies the live-restore feature
this is something we need to investigate more deeply, I keep the focus on consul upgrade for now
apart that, I detected weird things about SOLR that yvanzo have (partially) addressed, concerning missing or duplicate replicas in our SOLR cluster
lucifer
reosarevok: can you please add pixelpenguin, vscode, shivam_, arsh to the review list?