gotta love nerd-sniping myself: went from "hmm, i think i'll work on getting the kanidm test server up on running tonight" to "oh boy, the CI for this ansible role is woefully out of date, need to work on that before running the role against the server!" relatively quickly
2025-02-19 05044, 2025
julian45[m] has fallen victim to one of the classic blunders
From the editor perspective - but there’s a lot of mileage for just sharing preview images. I imagine artists might share summary cards too (x band has x songs/listens etc). It might be best to keep it basic but I think there’s heaps that could be done in terms of shareability (which in turns = growth), great thinking
2025-02-19 05049, 2025
BrainzBot
MBS-12791: Share edits to social media/other channels
2025-02-19 05048, 2025
aerozol[m]
Hurray, I’m not the only nerd excited about the little “automatically toggle tabs in the LB automatic submission tool” update
2025-02-19 05050, 2025
aerozol[m] uploaded an image: (15KiB) < https://matrix.chatbrainz.org/_matrix/media/v3/download/matrix.org/iAdCbroUbhRWMazDGXbjIxfu/image.png >
2025-02-19 05000, 2025
aerozol[m]
Shot monkey
2025-02-19 05009, 2025
lucifer[m]
mayhem: hi! let me know when you are around for a quick discussion on listen deletion stuff.
2025-02-19 05001, 2025
Kladky joined the channel
2025-02-19 05029, 2025
yvanzo[m]
Hi Jade, your idea #1 is very ambitious/thrilling and would fill a gap that was left after moving to Matrix.
2025-02-19 05019, 2025
yvanzo[m]
(Even though our IRC web logger is still running, it isn’t maintained and it doesn't handle Matrix-only stuff such as reactions and threads.)
Tickets will go offline in 5 minutes from now for maintenance.
2025-02-19 05031, 2025
monkey[m]
lucifer: something went wrong with the user stats.
2025-02-19 05032, 2025
monkey[m]
The stats I am seeing for myself (other users reported issue too, see forum link above) look like old stats, and switching between time periods doesn’t change anything.
2025-02-19 05042, 2025
monkey[m]
Also hello :)
2025-02-19 05041, 2025
outsidecontext[m
Interesting. On my account it looks sensible.
2025-02-19 05046, 2025
mayhem[m]
moooin!
2025-02-19 05058, 2025
mayhem[m]
lucifer: ready for a chat.
2025-02-19 05014, 2025
lucifer[m]
mayhem: yes, debugging stats right now. will ping you sson.
2025-02-19 05023, 2025
lucifer[m]
monkey: does this week stats look any better now?
2025-02-19 05028, 2025
lucifer[m]
artists this week
2025-02-19 05009, 2025
monkey[m]
lucifer: negative. Definitely stats from some time ago
2025-02-19 05006, 2025
monkey[m]
The top three artists for every rabge look suspicious, and don't change. The rest could be correct
2025-02-19 05045, 2025
monkey[m]
Almost looks like in interspersed some of my top artists from last year into every other range
mayhem: for listen deletion, we add listened_at, recording_msid, user_id to the `listen_delete_metadata` without checking if the listen actually exists. sometimes there can also be duplicate rquests for the same listen's deletion. at the moment, we try to delete all requests and record the max_id of the listen that was attempted to delete. then after deletion is complete we removed the requests until that max_id row. and if there
2025-02-19 05041, 2025
lucifer[m]
were any duplicate or non-existent listen deletion requests they would go away too.
2025-02-19 05042, 2025
lucifer[m]
however, with the latest PR i made yesterday this changes. we now do not clear the table immediately but set a deleted column to true and for invalid/non-existent requests deleted remains false, just like for a new request. after a full dump has been produced, we removed rows from the table where deleted is true. but since we can't differentiate between invalid or new requests, the table clutters with the invalid requests. i am
2025-02-19 05042, 2025
lucifer[m]
thinking about how to fix it and was wondering if i should add a new table to store just the actually deleted listens and restore the original cleanup method for existing table. but while writing this i realised i can change deleted from boolean to an enum and add a invalid state to differentiate.
2025-02-19 05007, 2025
Jigen
wait, wtf why is that question closed and downvoted? it seems clear enough? even to a guy liek me who don't code
2025-02-19 05026, 2025
lucifer[m]
>Post Closed as "Not suitable for this site" - lol
2025-02-19 05050, 2025
mayhem[m]
wow, just closed it.
2025-02-19 05011, 2025
mayhem[m]
fuck me. I better go ask someplace not run by community nazis. gees.
2025-02-19 05011, 2025
Jigen
god it's probably becasue this is the first post by mayhem. some sites liek this are very "u must be this experienced before we take u seriously"
2025-02-19 05012, 2025
Jigen
fuck
2025-02-19 05041, 2025
Jigen
maybe reddit 🤔
2025-02-19 05002, 2025
lucifer[m]
yeah maybe scikit reddit or some community channel is a better option
2025-02-19 05029, 2025
mayhem[m]
they specifically tell people to ask on SO. sigh.
2025-02-19 05034, 2025
lucifer[m]
lolol
2025-02-19 05052, 2025
mayhem[m]
> but while writing this i realised i can change deleted from boolean to an enum and add a invalid state to differentiate.
2025-02-19 05005, 2025
mayhem[m]
that was the first thing that came to my mind too. probably the easiest.
2025-02-19 05031, 2025
Jigen
i'venever seen an useful stackoverflow post tbh, most of the time i look up some thing. and like the guy explains it, and thne there are 30 mesgs saying "lol u are stupid for asking this slightly wrong" and thne one, highly usefull post that actually help (and aswers my question as well) in small it also has like atleast 4 "well ackshually" refuting comments underneath
2025-02-19 05041, 2025
mayhem[m]
"and the shortest code necessary to reproduce the problem." that was fully ignored. I guess I need to inline that.
2025-02-19 05029, 2025
Jigen
i signed up with github but i can't vote or comment becasue they want me to onboard or whatever. fack
2025-02-19 05037, 2025
Jigen
can't beassed right now
2025-02-19 05050, 2025
Jigen
yea i cant until i.. uh get 15 upvotes. i don't care to even bother with writing a post. god useless site
2025-02-19 05057, 2025
Jigen
monkey[m]: you around :)
2025-02-19 05002, 2025
monkey[m]
Jigen (IRC): Finishing lunch, will be back shortly
2025-02-19 05034, 2025
SigHunter has quit
2025-02-19 05036, 2025
Jigen
👍
2025-02-19 05001, 2025
SigHunter joined the channel
2025-02-19 05014, 2025
SigHunter has quit
2025-02-19 05041, 2025
SigHunter joined the channel
2025-02-19 05053, 2025
outsidecontext[m
mayhem: weird how your question was handled. But I'd suspect the low CPU usage is still somewhat related to Python's global interpreter lock. The assumption would be that the performance relevant parts of the nmslib calls run mostly outside the GIL, but still there might be enough Python code execution in build_index when preparing the data to have this slowed down by the GIL.
2025-02-19 05030, 2025
mayhem[m]
oh. GIL. feck, that might be it.
2025-02-19 05034, 2025
outsidecontext[m
Would be interesting to compare this when running the code with a Python 3.13 build with GIL disabled
2025-02-19 05055, 2025
pite joined the channel
2025-02-19 05000, 2025
mayhem[m]
indeed -- something worth trying. but... I think I may have found a workable solution.
2025-02-19 05007, 2025
mayhem[m]
be lazy.
2025-02-19 05012, 2025
SigHunter has quit
2025-02-19 05020, 2025
mayhem[m]
just build the indexes on demand, since it is very quick to build them.
I spent a bit of time on SO back in 2018 and did some questions and answers there, but haven't really come back to it because it's not been useful to me lol
2025-02-19 05031, 2025
Jade[m]
but even though I just logged on for the first time since like 2022 my reputation just kept going up
2025-02-19 05032, 2025
Jade[m] uploaded an image: (13KiB) < https://matrix.chatbrainz.org/_matrix/media/v3/download/ellis.link/e602WU6b6lohJ5wTfnE8fJvMhD63Ez02/image.png >
2025-02-19 05002, 2025
Jade[m]
because it's not about who engages in the site in a positive way, or gives useful answers, but who got there first
bitmap: LB just wobbled with a lot of "server closed the connection unexpectedly" errors from PG. I restarted the container and all seems well. could you have a look to see if anything odd is happening on the PG side of things?
2025-02-19 05035, 2025
bitmap[m]
mayhem: sorry that was almost certainly my fault since I'm moving some pgbouncer services in preparation for the switchover tomorrow
2025-02-19 05022, 2025
bitmap[m]
I'm not entirely sure why it affected LB and not MB though .. I put everything into maintenance mode and issued a PAUSE to pgbouncer first (which waits for all transactions / sessions to complete)
2025-02-19 05013, 2025
mayhem[m]
ah, ok. can you do me a favor and keep an eye out for more LB wobbles? If so, restart lb-web-prod on kiss, please.
