yvanzo: no, and unfortunately, neither did installing setuptools==65. same error in either case: setuptools.extern.packaging.version.InvalidVersion: Invalid version: '2.20201112.1-7-g711fb3b'
yvanzo: higher priority because of the translations :)
2023-12-05 33936, 2023
reosarevok
rdswift, yvanzo, aerozol: nothing we were talking about today is connected with wiki pages anyway :)
2023-12-05 33952, 2023
reosarevok
rdswift: so please don't be discouraged, I'd still love to move the stuff away
2023-12-05 33934, 2023
reosarevok
These "docs" are actually just existing admin interface for editing stuff, just made visible for users, not connected to the usual docs system (like relationships pages are)
2023-12-05 33912, 2023
reosarevok
aerozol: guidelines can (and IMO should) also be moved anyway - there's only stuff like "I, a user, wrote this quick guide" that IMO should stay in the wiki, plus any stuff that actually needs to be a wiki, like i18n pages that need input by translators
[musicbrainz-server] 14reosarevok merged pull request #3094 (03master…MBS-13368): MBS-13368: Properly compare series relationships if series is target https://github.com/metabrainz/musicbrainz-server/…
2023-12-05 33946, 2023
reosarevok
yvanzo: do you remember if we have any way to know how many pieces of cover art a release has using the MB API before calling the CAA one?
2023-12-05 33910, 2023
kilos_ has quit
2023-12-05 33917, 2023
reosarevok
I *think* there is not, but maybe I just don't know about it
2023-12-05 33936, 2023
reosarevok
(someone was asking in support about finding the release with the most images for a RG)
rdswift: reosarevok: if we do a shift them I don't know about having guidelines in the same docs tbh. Or maybe we can make the colors distinct for each section or something
2023-12-05 33933, 2023
aerozol
Seems like it might present an opportunity to make the different types of 'doc'/'help' etc clearer
2023-12-05 33959, 2023
aerozol
Not just because I think it's a bit confusing, the survey results I'm (still) working on show a lot of users are confused with the docs as well. It's in the top 10 'what's your biggest issue with MB' ranking (#10 but it counts!!)
2023-12-05 33940, 2023
akshaaatt
Why do docs need to have a theme though 😂
2023-12-05 33948, 2023
aerozol
A shift is better than nothing but I'd like to brain nstorm if we can get any extra, preferably easy, wins while we're at it
2023-12-05 33954, 2023
akshaaatt
Just made it doc doc stuff
2023-12-05 33957, 2023
akshaaatt
Make*
2023-12-05 33904, 2023
aerozol
akshaaatt: what are you replying to sorry?
2023-12-05 33902, 2023
akshaaatt
Ah, I was reading through previous chats and it said to have a theme for docs as well
2023-12-05 33910, 2023
reosarevok
akshaaatt: because read the docs by default is hideous and nobody would want to look at it unless they're a dev :p
2023-12-05 33922, 2023
akshaaatt
Makes sense reosarevok
2023-12-05 33932, 2023
aerozol
Ah right - didn't you tell me at the summit you hated the look of ReadTheDocs :p
2023-12-05 33941, 2023
reosarevok
(and our current user docs look like pages inside MB proper, so the closer we can get to that, the less of a clash it will be)
2023-12-05 33947, 2023
akshaaatt
Ik of a good paid tool called gitbook which is great for guidelines and product documentation
2023-12-05 33906, 2023
akshaaatt
An interface like that would be cool
2023-12-05 33920, 2023
akshaaatt
Don’t know of relevant oss solutions though
2023-12-05 33903, 2023
akshaaatt
aerozol: yus! For guidelines stuff, rtd looks bad
2023-12-05 33909, 2023
aerozol
My more recent message re. colors is to theme stuff to differentiate between the very different types of doc that MB has - dev documentation and editing guidelines are completely different things imo. If that helps explain it a bit
2023-12-05 33925, 2023
akshaaatt
Yus agreed
2023-12-05 33938, 2023
yvanzo
O’Moin
2023-12-05 33953, 2023
yvanzo
bitmap, lucifer: I found the core issue with mb-rngpy and pushed a tag as a workaround for testing sir in the meantime.
2023-12-05 33955, 2023
yvanzo
reosarevok: I’m just encouraging rdswift for now to not waste too much his time which I value.
2023-12-05 33938, 2023
reosarevok
Sure, I just don't think it will ever be a waste :)
2023-12-05 33922, 2023
reosarevok
There's no need to work super hard on it now but if aerozol wants to help, why not - it's not like either of them are going to update the search server:)
2023-12-05 33919, 2023
yvanzo
Just to clarify, the documentation has been among my top concerns for years, I’m not underestimating it.
lucifer: I keep being stuck with this build problem on listenbrainz. its not related to any branch. I've removed all images and all volumes and the problem persists.
2023-12-05 33949, 2023
mayhem
doesn't happen on any other machine.
2023-12-05 33958, 2023
mayhem
I guess I can try to uninstall docker and re-install.
2023-12-05 33907, 2023
mayhem
but I'm unable to work right now. :(
2023-12-05 33921, 2023
mayhem
any ideas at all? I'm stumped.
2023-12-05 33942, 2023
lucifer
mayhem: hmm weird
2023-12-05 33905, 2023
lucifer
try a no-cache build locally
2023-12-05 33917, 2023
mayhem
I deleted ALL images and ALL volumes.
2023-12-05 33936, 2023
mayhem
there should not be anything to pull from cache. and that no cache option was the very first thing I tried. :(
2023-12-05 33937, 2023
lucifer
`docker system prune -a` maybe?
2023-12-05 33957, 2023
lucifer
`docker system prune -a --volumes`
2023-12-05 33906, 2023
lucifer
to remove every bit of docker data.
2023-12-05 33906, 2023
mayhem
I can try that next time, just uninstalled docker, decalring total bankruptcy.
it was time to upgrade docker in any case. rebuilding now.
2023-12-05 33941, 2023
mayhem
lucifer: that fixed it finally.
2023-12-05 33952, 2023
lucifer
awesome great
2023-12-05 33900, 2023
lucifer
i would even suggest to start using docker compose v2
2023-12-05 33909, 2023
Lotheric_ has quit
2023-12-05 33914, 2023
lucifer
its faster, at least feels so
2023-12-05 33932, 2023
mayhem
is that docker compose vs docker-compose ?
2023-12-05 33945, 2023
lucifer
yes
2023-12-05 33954, 2023
mayhem
yeah, been there a while
2023-12-05 33917, 2023
lucifer
oh interesting
2023-12-05 33949, 2023
lucifer
did you alias docker-compose to docker compose? because every now then i keep encountering a meb project with develop/test script that barfs on docker compose
2023-12-05 33909, 2023
mayhem
nope
2023-12-05 33944, 2023
lucifer
i guess meb.org and lb were fixed sometime back so rarer for you to encounter it
2023-12-05 33929, 2023
Lotheric joined the channel
2023-12-05 33906, 2023
BrainzGit
[listenbrainz-server] 14amCap1712 merged pull request #2651 (03master…fix-playing-now-cover): LB-1371: "Playing now" does not show cover art on page load https://github.com/metabrainz/listenbrainz-server…
2023-12-05 33901, 2023
Rotab has quit
2023-12-05 33918, 2023
reosarevok
yvanzo: ping :)
2023-12-05 33935, 2023
yvanzo
ouch ;)
2023-12-05 33937, 2023
mayhem
why you gotta ping so hard reosarevok ?
2023-12-05 33936, 2023
reosarevok
yvanzo: if you merge the admin thing and I rebase the other string PR, could we still release beta tonight and freeze, what do you think? :)
2023-12-05 33944, 2023
reosarevok
I'll try to ping softer next :D
2023-12-05 33920, 2023
mayhem
monkey: after all those changes, I *finally* got the branch up. lolsob
[listenbrainz-server] 14amCap1712 merged pull request #2652 (03master…fix-follow): LB-1315: Attempting to follow a user while not logged in gives error https://github.com/metabrainz/listenbrainz-server…
in this query I want to fetch the release_group.artist_credit and explode that into a list of artist_mbids. I always get that query wrong and you always have to fix it. what is the correct query fragment to do that?
