What to do with images during release merges

MusicBrainz
, ,
1

For some time now a banner is displayed at the top of the MB page:

Images are currently not being copied over after event or release merges. For now, please make sure to upload any images that should be kept to the merge target beforehand.

And indeed, after a release merge i only get empty “Image not available” boxes from the source release. However, it is not quite clear to me what course of action is now required of me. I did download the original images to my machine, so should I upload them now and delete the empty image boxes? Should I already have uploaded them to the target and am I too late? Something else?

3 Likes
2

I think you’re probably too late. I was among those who reported the problem when it occurred. I uploaded images after a merge was completed, and, as the banner suggests, they aren’t being processed correctly at the CAA. I tried replacing one of those images, but it didn’t work. We just need to wait for CAA to resolve the problem.

1 Like
3

You should be able to upload them to the target release and delete the broken images. @Beckfield can you link to the release you had trouble with?

I tried contacting the IA again earlier today to see if I can find out any new information…

2 Likes
4

Sorry if I misinformed. I haven’t re-tried any of this for a few weeks.

5

OK, so it’s just manually transferring the images by download and upload and deleting the broken image boxes from the source? I can do that :slight_smile:

Out of curiosity; What happens to the source images that are not transferred like that? Will they eventually re-appear or are they lost in limbo?

2 Likes
6

Alas, it seems I am plagued by the same problem as @Beckfield. Newly uploaded images to the target do not appear. All I get is a sad Image not available, please try again later box.

7

Sorry for the delayed response here. After some back-and-forth I finally got word from the IA that the issue with copying images between buckets has been fixed! :tada:

I just spent a few hours writing some gnarly queries to re-queue the broken image events. Unfortunately I did this at a bad time because the IA is currently experiencing other unrelated load issues (that is, the total number of tasks queued exceeds their global limit at the moment). So we won’t actually see things fix themselves until a bit later. :weary:

Out of curiosity; What happens to the source images that are not transferred like that? Will they eventually re-appear or are they lost in limbo?

Any image that wasn’t removed will eventually re-appear. (So, if you manually transferred the images to the target but didn’t remove the broken source images, those will have to be cleaned up still.)

No need to do anything for releases where the images weren’t copied. Those will fix themselves automatically.

12 Likes
8

Excellent! Thanks for your answer and your work.

1 Like
9

Amazing, thank you @Bitmap! It must have been annoying having to hassle a third party to get things moving, for so long. Success :partying_face:

1 Like
10

Thanks, @Bitmap ! I see the one I’ve been waiting on has fixed itself.

1 Like