MBID recording merges are not applied

[phw]

It looks like since a while merged recordings in MB don't get followed up on the AcoustID side. There are now many instances of unresolved merges. Some examples:

https://acoustid.org/track/b1eb0783-f5f3-4428-9733-2fbfd8e30d93
https://acoustid.org/track/91684050-2987-48e9-807a-4f7354305511
https://acoustid.org/track/1cc7cd8a-50c7-4951-a8fa-557c6b2b41e6

Maybe there is some issue with running the merge code from

acoustid-server/acoustid/data/track.py

Line 149 in 5c05072

def merge_missing_mbids(fingerprint_db, ingest_db):

.

See also the discussion at https://community.metabrainz.org/t/why-does-acoustid-sometimes-not-show-merged-recordings/659454

[Echelon666]

Thousands of people are waiting for it.

[Echelon666]

See also the discussion at https://community.metabrainz.org/t/worse-results-in-picard-2-10/663668

[Echelon666]

See also the discussion at https://community.metabrainz.org/t/picard-scan-still-returning-new-acoustid-submissions-as-standalone-recordings/603676

[jesus2099]

After recording merge (in 2022):

• The AcoustID page will show an italic link with the old MBID (here fa9c940c-408b-41f0-b746-997e50e36d72), alongside the merged recording with its metadata, instead of merging old and merged MBID metadata
• Merged MB recording Fingerprints tab will not show fingerprints that used to be linked to old MBID, only target’s (here 0 fingerprints), instead of showing them all

Is it only an AcoustID problem or an MB plus AcoustID problem?

See Italic AcoustID topic.

I’ve read in some IvanDobsky edit note, that this problem has been there since at least 2021 recording merges.