Server – Page 4 – MetaBrainz Blog

MusicBrainz Server update, 2023-12-20

Winter release is coming, with a lot of refactoring behind the scenes. In particular, we fixed a lot of text in the website user interface, to more closely follow the design guidelines concocted by Aerozol for a long time. See the below list of tickets for more functional changes.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to derat and jesus2099 for having contributed patches. Thanks to ApeKattQuest, chaban, chancey, lotheric, and mr_maxis for having reported bugs and suggested improvements. Thanks to goliv, kellnerd, mfmeulenbelt, outsidecontext, salo.rock, Vac31, and yangmouren for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-12-20.

React Q&A

If you are, like me, an avid follower of MusicBrainz server release notes, you will have been reading about a certain type of update for a number of years – React conversion tasks.

But, unlike me, you may know what React is! For the rest of you – happily drifting on the currents of ignorance with me – I have good news. The MusicBrainz team has sent a Software Engineer tugboat to pull us into the waters of knowledge. A tugboat by the name of yvanzo, who has agreed to answer some questions about React.

MusicBrainz Server update, 2023-11-27

For your Cyber Monday here is a free release of convenient improvements and bugfixes. It adds www.metalmusicarchives.com to the allowed other databases. It also paves the way for improvements in instrument search.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to derat and Maxr1998 for having contributed patches. Thanks to Brian Cassidy, chaban, Gal Lalouche and HibiscusKazeneko for having reported bugs and suggested improvements. Thanks to Early6431, itodouble, kellnerd, salo.rock, and Vac31 for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-11-27.

MusicBrainz Server update, 2023-11-13

As announced two months ago to mirrors’ administrators, MusicBrainz Server is now requiring Node.js 20.

As part of that move, we’ve also upgraded our required version of Yarn (used to install JavaScript dependencies from npm) to v4. Unless you’re using musicbrainz-docker, which manages Yarn for you, the Yarn upgrade will require some manual steps. These are to be executed from the musicbrainz-server directory:

sudo corepack enable # Installs yarn to /usr/local/bin
rm -rf node_modules
./script/compile_resources.sh

For more information about corepack, see INSTALL.md.

Also as promised two weeks ago to the same people, it is now possible to rebuild indexes using ICU collations by running:

admin/RebuildIndexesUsingCollations.pl

It has to be run whenever the versions of libc/icu have changed on your system. Auto-detecting this situation will also be implemented soon.

For editors, the most important fixed bug is likely the search for edit by relationship type that was timing out. There is otherwise a fair amount of fixed bugs, improvements, strengthened security, and small new features.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to derat for the couple of UI/UX improvements he coded. Thanks to BestSteve, chaban, DontMindMe, Freso, jesus2099, sammyrayy, and yindesu for having reported bugs and suggested improvements. Thanks to bbiirrdd, claybiockiller, Jaken264, joysriram.sarkar.56, julian45, kellnerd, outsidecontext, portik, reosarevok, salo.rock, SoundwaveUwU, suming, Vac31, wileyfoxyx, yurirhsilva, and Водка665 for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-11-13.

CritiqueBrainz update, 2023-10-31

This is a maintenance-only release of the CritiqueBrainz server. It fixes a potential security vulnerability (unexploited so far) and tests. It also updates a bunch of important dependencies to their latest version (Node.js…).

From the users’ point of view, it fixes the preview feature of the text editor in the critique submission form, thanks to the new Markdown text editor, EasyMDE, an actively maintained fork of the abandoned SimpleMDE.

The git tag is v-2023-10-31.0.

This update is delivered to you by ansh, lucifer, and monkey, to keep CritiqueBrainz alive. As a reminder, this project has currently no dedicated developer. Code contributions, even small ones, would be more than welcome!

MusicBrainz Server mirror-only fix update, 2023-10-24

If you are running a mirror, you may have seen replication packet #162718 fail to apply with the following error:

Failed query:
'INSERT INTO musicbrainz.tag (id, name, ref_count) VALUES (?, ?, ?)'
(259975 girl group 0)
23505 DBD::Pg::st execute failed: ERROR: duplicate key value violates unique constraint "tag_idx_name"
DETAIL: Key (name)=(girl group) already exists. [for Statement "INSERT INTO musicbrainz.tag (id, name, ref_count) VALUES (?, ?, ?)" with ParamValues: 1='259975', 2='girl group', 3='0']

This occurs because the index tag_idx_name was temporarily corrupted in production after yesterday’s database switchover, due to an ICU collation version mismatch. This allowed people to enter tags with duplicate names.

Since then we’ve fixed the broken packets, and published the fixed versions.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

The git tag is v-2023-10-24-hotfix.

Notes

If you encountered the error above, you’ll have a “previously aborted load,” and must update your MusicBrainz Server to v-2023-10-24-hotfix. After that, replication should operate smoothly without any further action being needed.
If you haven’t replicated up to packet #162718 yet, then no action is needed.

We apologize for the inconvenience. We’re improving our database upgrade process to always rebuild indexes using ICU collations.

Fixed Bug

[MBS-13333] – Replication is blocked by tag duplicates

MusicBrainz Server update, 2023-10-02

At the dawn of the Summit 23, here is a comfort release with some improvements, a few bugfixes, and even some small new features.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to CatQuest, chaban, HibiscusKazeneko, Kurumi, Mark Bakker, Q_FDB, and yindesu for having reported bugs and suggested improvements. Thanks to emiguel1960, salo.rock, Vac31, and Yllelder for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-10-02.

MusicBrainz Server update, 2023-09-18

A tiny release this time. The main change if you are hosting your own server is that we’ve upgraded to Node 18 since Node 16 is EOL. For everyone else, now you can see if someone has been blocked from editing or leaving edit notes before you report them (look for “Restrictions” in their profile); this can also help explain why some user is not answering your notes.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to HibiscusKazeneko, jesus2099 and kakawup for having reported bugs and suggested improvements. Thanks to claybiockiller, mfmeulenbelt, outsidecontext, salo.rock and Vac31. for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-09-18.

MusicBrainz website mirror will require Node.js 20 starting from November 13, 2023

This announcement is uniquely intended for administrators having installed any mirror of MusicBrainz website with manually installed dependencies instead of using the Docker Compose project musicbrainz-docker.

MusicBrainz website is rendered using Node.js whose minimum required version was 16 so far. This version is reaching end-of-life next week according to their Release Working Group. Therefore MusicBrainz Server will switch to the active LTS Node.js 18 for a transitioning period of two months. It will still support Node.js 16 for previous installations during this period. After that, Node.js 20 will enter its active LTS phase and be required by MusicBrainz website. It has already been used locally in development for a long time, so we don’t expect any major issue when switching mirrors to it.

MusicBrainz Server update, 2023-08-28

On the menu of the day there are some improvements to the editing interface thanks to derat! It’s accompanied with a mesclun of changes (additions, fixes, improvements and updates) related to external links, especially some other databases and new relationship types for art gallery and ticketing. It’s spiced with a pinch of new icons (for collections, genres, and tags) and condiments.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks also to HibiscusKazeneko, Lotheric, Trevor, wonder_al, Xythium, yindesu, and yyoung for having reported bugs and suggested improvements. Thanks to chaban, outsidecontext, RandomMushroom128, and salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-08-28.