Month: May 2021

MusicBrainz Server update, 2021-05-31

We’re back after our schema change with another release fixing mostly small bugs. The most welcome of these changes is probably that unrelated work relationships (such as arrangements, parodies, translated versions and whatnot) will now be hidden from the inline release view, meaning releases with popular songs that have lots of versions should be significantly less annoying to use!

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 chaban, fabe56, jesus2099, kellnerd, mr_maxis, mtrolley, psychoadept, ROpdebee and yindesu for having reported bugs and suggested improvements. Thanks to ffff23, jormangeud, outsidecontext and salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2021-05-31.

Fixed Bug

  • [MBS-11630] – JS error when submitting parallel release group name edits from release editor
  • [MBS-11631] – DNB validation wrongly blocks label and place links
  • [MBS-11637] – Event-Work relationships not shown from Work page
  • [MBS-11643] – URL that ends in the future is prematurely disabled
  • [MBS-11660] – Periods are not always ignored in admin e-mail searches
  • [MBS-11662] – Guess Case changes capitalization of [untitled] to [Untitled] if not the only word on title
  • [MBS-11663] – Release group headings missing when moving disc ID
  • [MBS-11671] – Dates displayed as 24:mm instead of 00:mm
  • [MBS-11676] – Regression: “Set track durations” is shown for all releases on cdtoc pages

Improvement

  • [MBS-9419] – Don’t show versions, medleys, etc for a work on the release page
  • [MBS-11628] – Accept and cleanup https “permalinks” for DNB
  • [MBS-11673] – Block smart links: myurls.bio

New Feature

MetaBrainz IRC migration

Due to recent changes in the administration of the freenode IRC network, all MetaBrainz IRC channels have migrated to the Libera.Chat network effective immediately.

The main channel names are all the same, #metabrainz, #musicbrainz, and #bookbrainz, though some special purpose channels were renamed in the move to better align with our project namespace (e.g., #brainzbot is now #metabrainz-bot).

Most of the MetaBrainz team will be around using the nicks you know already (e.g., bitmap, yvanzo, reosarevok, Freso, zas, …) but a few have had some changes: Mr_Monkey is now monkey and _lucifer is now lucifer.

Hopefully this will have minimal impact on users beyond having to update your IRC server in your client. If needed, Libera Chat provides a guide for how to connect to their network, including client specific guides for a number of IRC clients. They’re working on their own web client, but for now, Kiwi IRC can be used if you don’t have a local client running. For those of you relying on Matrix or Tor to connect: Libera.Chat staff is working on both of those and they should hopefully both be up within a week. Stay tuned on their Twitter: https://twitter.com/LiberaChat

As always, you can find information about our IRC channels and guidelines on our IRC documentation page. Wikimedia have also migrated to Libera.Chat and have written this handy guide which might also come in useful for migrating: https://meta.wikimedia.org/wiki/IRC/Migrating_to_Libera_Chat

As a last note (and I am admittedly biased being both former freenode staff and current Libera.Chat staff myself): it is my personal belief, as community manager, that freenode is no longer a safe network to be on for our users. The new freenode staff does not seem trustworthy, making policies to retroactively justify their own breaches of their policies, refusing to give a clear answer on “whether slurs, racism and transphobia are allowed on Freenode”, getting staff on board that were kicked from other networks for privilege abuse, and leaking staff-internal information (channel closure reasons) to non-staffers. I highly recommend disconnecting from the network ASAP and, if possible, overwrite your NickServ registered e-mail and password and possibly dropping your NickServ registration as well if you can and are able and willing to. If you have used your NickServ password for anything else, my recommendation is to consider that password compromised.

Congratulations GSoC 2021 students!

Congratulations and thank you to everyone who submitted a project with MetaBrainz for this year’s Summer of Code!

This year, the selected projects are:

Ritiek Malhotra
MusicBrainz – Complete Rust binding for the MusicBrainz API

Akash Gupta
BookBrainz – Implement a “Series” entity

Akshat Tiwari
Musicbrainz Android App – Dawn of Showdown

Jason Dao
ListenBrainz –  Pin Tracks & Review Tracks Through CritiqueBrainz

Yang Yang
MusicBrainz – Push the URL relationship editor to the next level

Welcome to the team, and congratulations!
In these troubled times it is all the more impressive that you all mustered the focus and determination to work on proposals, contribute to MetaBrainz projects and integrate with the community.

In our small and tightly knit team and community, communication is key!
If you run into any kind of issue (stuck in your code, starting a part-time job, health or family emergencies, etc.) don’t hesitate to contact your mentor as early as possible to find a solution; we’re here to support you.

We mentors all look forward to working with you before, during and after the summer, guiding you to success and helping you learn and improve your skills!

ruaok, yvanzo, mr_monkey, lucifer and oknozor

MusicBrainz schema change release, 2021-05-17 (with upgrade instructions)

We’re happy to announce the release of our May 2021 schema change today! Thanks to all who were patient during today’s downtime as we released everything to our production servers.

This is a fairly minor release as far as schema changes go, but please do report any issues that you come across, especially related to the display of recordings, releases and release groups on artist and release group pages.

New, user-facing changes with this release are limited to the new ability to merge collections (MBS-10208) and the addition of ratings for places (MBS-11451). Additionally, MBS-11463 adds a new view that is used to fix a couple small requests related to disc IDs (MBS-11268) and release length calculation (MBS-11349). Two other changes – adding a first-release-date field to recordings (MBS-1424) and support for PKCE in OAuth (MBS-11097) are more or less end-user affecting but were already released on the main MusicBrainz servers a while ago. All other changes are under the hood only.

We ran into a few complications while working on this schema change update, so we decided to postpone two changes to our October schema change to ensure only stuff we are more confident on is released. Those are MBS-11457, which involves dropping the ordering_attribute column for series and would have had no direct effect on user experience, and MBS-11456, which would have added MBIDs for artist credits.

A few of the released new features and improvements — namely the first-release-date field for recordings, and the performance improvements to artist pages — make use of new materialized tables. These tables aren’t dumped, nor are they replicated, since they’re derived entirely from primary table data. Rather, we’ve added a new script to build them (admin/BuildMaterializedTables, included in the upgrade instructions below), and triggers to keep them up-to-date once they’re built. These triggers are created on replicated servers, too. If you use the web interface or web service at all, just note the extra step of running BuildMaterializedTables after upgrade.sh below!

A new release of MusicBrainz Docker is also available that solves an issue for live indexing and matches this update of MusicBrainz Server. See the release notes for update instructions.

Now, on to the instructions.

Schema Change Upgrade Instructions

Note: Importing the latest data dump is always a valid alternative to running ./upgrade.sh on an existing database, if you’d prefer to also get new data in one go. Just follow the relevant instructions in INSTALL.md. The git tag is v-2021-05-19-hotfixes. The rest of the instructions here assume an in-place upgrade.

  1. Make sure DB_SCHEMA_SEQUENCE is set to 25 in lib/DBDefs.pm.
  2. If you’re using the live data feed (your REPLICATION_TYPE is set to RT_SLAVE), ensure you’ve replicated up to the most recent replication packet available with the old schema. If you’re not sure, run ./admin/replication/LoadReplicationChanges and see what it tells you; if you’re ready to upgrade, it should say “This replication packet matches schema sequence #26, but the database is currently at #25.”
  3. Take down the web server running MusicBrainz, if you’re running a web server.
  4. Turn off cron jobs if you’re automatically updating the database via cron jobs.
  5. If you’re using the live search indexing, stop it and, assuming sir is under the same directory as musicbrainz-server, run cd ../sir && python2.7 -m sir triggers && cd - && ./admin/psql < ../sir/sql/DropTriggers.sql && ./admin/psql < ../sir/sql/DropFunctions.sql
  6. Switch to the new code with git fetch origin followed by git checkout v-2021-05-19-hotfixes.
  7. Install newer dependencies Perl 5.30 or later and NodeJS 16 according to install prerequisites.
  8. Run cpanm --installdeps --notest . (note the dot at the end) to ensure your perl-based dependencies are up to date.
  9. Run ./upgrade.sh (it may take a while to vacuum at the end).
  10. Set DB_SCHEMA_SEQUENCE to 26 in lib/DBDefs.pm as instructed by the output of ./upgrade.sh.
  11. If you’re using the web interface or web service, run ./admin/BuildMaterializedTables --database=MAINTENANCE all to build new materialized tables. These will take several additional gigabytes of spaces and be kept up-to-date automatically via triggers. For more information, see INSTALL.md.
  12. If you’re using the live search indexing, assuming sir is under the same directory as musicbrainz-server, run cd ../sir && git fetch origin && git checkout v2.1.0 && python2.7 -m sir triggers && cd - && ./admin/psql < ../sir/sql/CreateFunctions.sql && ./admin/psql < ../sir/sql/CreateTriggers.sql and rebuild indexes (by running cd ../sir && python2.7 -m sir reindex && cd -) then start it in watch mode (with cd ../sir && git fetch origin && git checkout v2.1.0 && python2.7 -m sir amqp_watch)
  13. Turn cron jobs back on, if applicable.
  14. Restart the MusicBrainz web server, if applicable. It’s also recommended you restart Redis. If you’re accessing your MusicBrainz server in a web browser, run ./script/compile_resources.sh.

Here’s the list of resolved tickets:

New Feature

  • [MBS-10208] – Allow merging collections
  • [MBS-11451] – Support ratings for places
  • [MBS-11463] – Add view to easily access medium track lengths
  • [MBS-11652] – Add support for artist series (hotfixed)

Improvement

  • [MBS-10962] – Speed up listing artist’s releases
  • [MBS-11268] – Show “Set track durations” on release/discids page
  • [MBS-11460] – Add materialized tables to fetch release groups by artist or track artist

Database Schema Change Task

  • [MBS-10647] – Add [no label] to b_del_label_special trigger for labels
  • [MBS-11453] – Change entity0_cardinality, entity1_cardinality to SMALLINT
  • [MBS-11459] – Create the edit_data_type_info function on mirrors
  • [MBS-11464] – Drop table statistics.log_statistic
  • [MBS-11466] – Change language.frequency and script.frequency to SMALLINT

Previously Released Changes

  • [MBS-1424] – Add a ‘First release date’ field to recordings
  • [MBS-10821] – Edit changing medium tracklist and format is stuck
  • [MBS-11097] – Support PKCE (Proof Key for Code Exchange) by OAuth clients
  • [MBS-11431] – Speed up /ws/js/check_duplicates

MusicBrainz Server update, 2021-05-03

Hi! This time we have another small release with a bunch of minor fixes and small quality of life improvements. The latter include one small improvement to an error message requested over 10 years ago! It might take us time, but we get to things eventually, and that’s what matters, right? Right? Next release will be our May schema change – you can read what is coming with that one at the dedicated announcement post.

A new release of MusicBrainz Docker is also available that solves an issue for live indexing and matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to chaban, Cyberskull, Lotheric, nikki, salo.rock and Sophist for having reported bugs and suggested improvements. Thanks to mfmeulenbelt, outsidecontext and salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2021-05-03.

Fixed Bug

  • [MBS-11550] – Untranslated strings on Confirm Form Submission page
  • [MBS-11573] – Collection data missing on ratings pages
  • [MBS-11598] – Broken links generated for deleted artwork missing suffix
  • [MBS-11603] – DNB validation is too strict and blocks legitimate links
  • [MBS-11611] – OverClocked ReMix URLs shouldn’t have a trailing slash after the number.
  • [MBS-11612] – No link to genre/delete from genre index

Improvement

  • [MBS-1588] – More user friendly error when trying to add a CD with a bad TOC
  • [MBS-9251] – Display ended places differently on the map
  • [MBS-9259] – Document how the track list parser works
  • [MBS-9376] – Indicate that edit searches can be bookmarked to save them
  • [MBS-11546] – Allow Resident Advisor /exchange URLs for releases
  • [MBS-11559] – Specify tracklist is empty in Remove medium edits
  • [MBS-11571] – Warn about e-mail as a username
  • [MBS-11587] – Block smart links: hypel.ink
  • [MBS-11590] – Equalize display of empty fields in cover art edits
  • [MBS-11604] – Add genre name to genre index title
  • [MBS-11619] – Ignore periods and +tags in admin e-mail searches

New Feature

  • [MBS-10899] – Report for releases with catalog numbers that look like ISRCs