#metabrainz

<aerozol[m]> "Hemang Mishra: I reviewed your..." <- Thanks!

I'll make the updates and get back to u asap.

HemangMishra[m]: jasje: would love reviews from your side as well !!

I restarted mb-mail-service-prod on selda, it was apparently doing nothing but using 100% cpu

Also keydb on selda is still very busy.

<zas[m]> "I restarted mb-mail-service-prod..." <- Me on some days

zas: same for the mail service container on yamaoka and its also currently marked as unhealthy. restarted it.

bitmap: about keydb on selda, since it is used, it should be running on 2 different hosts, and also I noticed it is using only one thread (https://github.com/metabrainz/docker-server-con...) I guess using 4 would make more sense

[mb-rngpy] 14amCap1712 opened pull request #11 (03master…actions-publishing): Add GitHub Actions workflow for PyPI publishing and simply update.sh script https://github.com/metabrainz/mb-rngpy/pull/11

<zas[m]> "bitmap: about keydb on selda..." <- makes sense, I don't think I set those up but it was probably configured to use fewer resources when it was on aretha and never updated after the move

is keydb still maintained? last commit was over a year ago and there's also https://github.com/Snapchat/KeyDB/issues/895 :\

valkey seems to be the most followed and reliable fork of redis so far

i genuinely wonder why people even want to have redis forks

or redis, in the first place (postgresql covers all use cases pretty well IMO)

there was a licensing issue IIRC

<zas[m]> "I restarted mb-mail-service-prod..." <- Ooh, interesting. I wonder what caused that

oh? haven't seen that

Jade[m]: Probably to do with html2text tbh

re "mb-mail-service-prod", sounds like mb-mail-no-service-prod ;o)

:-?

<yvanzo[m]> "there was a licensing issue IIRC" <- yes, there was a big one; in march of last year, redis relicensed its core code from BSD to two non-free licenses, at which time the linux foundation forked the last BSD-licensed version to valkey

but with the release of redis 8 some or all of the core code is now under the AGPL

valkey is still prominent in the key-value DB space though, and redis & valkey are probably truly competitive (or at least closer to it) at both of their respective latest versions now

* but with the release of redis 8 at the beginning of this month, the core code is now under the AGPL

[mbsssss] 14yvanzo merged pull request #69 (03master…SEARCH-739): SEARCH-739 (schema): Add mediumid for release https://github.com/metabrainz/mbsssss/pull/69

SEARCH-739: Allow searching releases by medium MBID https://tickets.metabrainz.org/browse/SEARCH-739

[mbsssss] 14yvanzo merged pull request #57 (03master…barcode-spaces): SEARCH-637: Trim spaces in barcode search https://github.com/metabrainz/mbsssss/pull/57

SEARCH-637: Ignore spaces when parsing barcode in search query https://tickets.metabrainz.org/browse/SEARCH-637

so, valkey isn't really relevant anymore?

nah, valkey still is. for example redis still has proprietary extensions and it's still sponsored/developed by a private company

forks with different licencing situations are inevitably gonna diverge over time

from a risk standpoint, if there are no features/functionalities MeB relies on specific to keydb and unavailable in other key-value stores, sticking with keydb long-term does not seem likely to be a sustainable choice. of the remaining options, valkey is probably the best candidate due to its development and sponsorship model (nonprofit foundation), as well as its performance & general quality

julian45[m]: along this line, snapchat was (perhaps still is, but unclear) the apparent sponsor of keydb

Jade[m]: Both are going to develop features as needed by their customers/community and it won't necessarily be obvious what the differences are

[mbsssss] release 03v-2025-05-18 has been published by 14yvanzo: https://github.com/metabrainz/mbsssss/releases/...

[mb-solr] 14yvanzo opened pull request #66 (03master…docker-command): Set the default command in the Docker image https://github.com/metabrainz/mb-solr/pull/66

[mb-solr] 14yvanzo merged pull request #50 (03master…search-690): SEARCH-690 (writer): Add artist credit MBID to output https://github.com/metabrainz/mb-solr/pull/50

SEARCH-690: Set artist credit's MBID in XML/JSON search results https://tickets.metabrainz.org/browse/SEARCH-690

[mb-solr] 14yvanzo merged pull request #66 (03master…docker-command): Set the default command in the Docker image https://github.com/metabrainz/mb-solr/pull/66

[sir] 14yvanzo merged pull request #163 (03master…gh-actions): Move SIR tests to Github Actions https://github.com/metabrainz/sir/pull/163

[mb-solr] 14yvanzo merged pull request #63 (03master…SEARCH-738): SEARCH-738 (writer): Support medium MBIDs https://github.com/metabrainz/mb-solr/pull/63

SEARCH-738: Set medium's MBID in XML/JSON search results https://tickets.metabrainz.org/browse/SEARCH-738

[mb-solr] release 03v4.1.0 has been published by 14yvanzo: https://github.com/metabrainz/mb-solr/releases/...

[sir] 14yvanzo merged pull request #160 (03master…SEARCH-738): SEARCH-738 (idx), SEARCH-739 (idx), SEARCH-740 (idx): Support and search by medium MBIDs https://github.com/metabrainz/sir/pull/160

SEARCH-738: Set medium's MBID in XML/JSON search results https://tickets.metabrainz.org/browse/SEARCH-738

SEARCH-739: Allow searching releases by medium MBID https://tickets.metabrainz.org/browse/SEARCH-739

SEARCH-740: Update mbdata / Sir to MBS schema 30 (2025 Q2) https://tickets.metabrainz.org/browse/SEARCH-740

[sir] 14yvanzo merged pull request #157 (03master…search-690): SEARCH-690 (indexer): Add artist credit MBID in indexes https://github.com/metabrainz/sir/pull/157

SEARCH-690: Set artist credit's MBID in XML/JSON search results https://tickets.metabrainz.org/browse/SEARCH-690

[sir] release 03v4.0.0 has been published by 14yvanzo: https://github.com/metabrainz/sir/releases/tag/...

Should be all the releases for the schema change.