Entity merging tools “mb. MERGE HELPOR 2”

MusicBrainz
,
28

True but maybe all these good things were linked to an MBID that recently disappeared in favour of a brand new MBID (into which it is no longer good to merge, benefit of age is already lost).
It very often happens that people adds duplicates then merge existing into their duplicates.

It’s why older row ID is more sure about which MBID is actually older, not amount of data.

29

Exactly this. If a quick look you don’t see any difference, then oldest wins.

Now you are off on an odd edge case. Constantly flipping MBIDs would not be good. In that rare example it would not really matter which one was chosen.

30

It’s often the case with the merged recordings I see.
Because people tend to merge to newer and more complete recordings. :wink:

31

Not sure if it’s due to the same issue as the one @chaban wrote on the topic of the MASS MERGE RECORDINGS script, but this one stopped working for me yesterday. Searching through recent merge edits of others (and not just recording mergers) it seems like this may not be just me. :thinking:

1 Like
32

Basically same issue :

Remove [action*='/merge'] and it should work.

3 Likes
33

Thanks very much again, @chaban!
New bug ticket filed:

Update

It’s fixed.

2 Likes
34

Not sure whether it’s just me but it looks like this script stopped generating the ‘‘Merging into oldest [MBID]’’ text that goes at the bottom of each note for merger edits. At first I thought it might be just me having recently re-installed my browser and there might be some default setting that I forgot changing. I even tried using it with all other userscripts disabled but it didn’t change anything.

On the other hand, I also noticed that no merging edits have been entered with this autogenerated bit in the notes for the last few hours, so maybe there’s some general issue instead.

https://musicbrainz.org/search/edits?auto_edit_filter=&order=desc&negation=0&combinator=and&conditions.0.field=open_time&conditions.0.operator=%3D&conditions.0.args.0=2023-07-13&conditions.0.args.1=&conditions.1.field=edit_note_content&conditions.1.operator=includes&conditions.1.args.0=oldest&conditions.2.field=edit_note_content&conditions.2.operator=not-includes&conditions.2.args.0=mass&conditions.3.field=type&conditions.3.operator=%3D&conditions.3.args=4&conditions.3.args=153&conditions.3.args=14&conditions.3.args=74&conditions.3.args=24&conditions.3.args=223%2C225%2C311&conditions.3.args=143&conditions.3.args=44

2 Likes
35

Wow nice search!
It seems to work for some editors.
What are your OS, browser and userscript extension, names and versions?

36

Interestingly, it started working for me too again. Here are two very recent edits that I just entered:
Edit #101574543 - Merge recordings
Edit #101574769 - Merge recordings

Not sure if it’s any factor for things going back to normal, but the only thing I did in the meantime was re-enabling all my other userscripts.

Windows 10 Pro 22H2
Firefox 115.0.2 (64-bit)
Violentmonkey 2.14.0

1 Like
37

Same here, it stopped writing this note already long ago, didn’t bother to make noise about it til now.
So today it’s Ubuntu 20.04.6 LTS, Brave v1.56.11, Tampermonkey 4.19.0; tried also Chrome 115.0.5790.110 & Firefox 115.0.2, both with Violentmonkey 2.15 and only “mb. MERGE HELPOR 2” 2023.5.17 enabled. Similar story on Win10 which I rarely use. ¯\_(ツ)_/¯

1 Like
38

I tried it here and it worked.
I think it works on Windows also for me.

I’m wondering if it’s another React Hydrate problem, maybe.

Does the userscript work when you are still on merge page, before submitting (showing info and pre-selecting oldest MBID)?
Is it only an edit note problem?

39

This exactly:

image
image809×428 58.1 KB

1 Like
40

I have reproduced this bug on a new PC with Edge 115!
It seems to be a problem with Chrome version 115.
I will hopefully fix that soon…

41

@DenizC and @spUdux, could you test newer version of your browsers, based on Chromium 116 instead of 115?

  • Brave v1.57.49 (Chromium 116.0.5845.96)
  • Firefox 116.0.3

It seems to be a problem with Chromium/Chrome version 115… :thinking:

42

Quick check here on a Win 10 and it’s still the same blank note with Brave Version 1.57.49 Chromium: 116.0.5845.96 (Official Build) (64-bit).

1 Like
43

@DenizC and @spUdux, could you update the script to latest version 2023.8.20 and tell me if the bug is fixed for you?

44

Sorry, updated to 2023.8.20 but the blank note issue persists :frowning: Brave 1.57.49 Chromium: 116.0.5845.96 & Tampermonkey 4.19.

And it’s the same here with Firefox 102.14.0esr (64-bit) & Violentmonkey v2.15

1 Like
45

Firefox 116.0.3 and Violentmonkey v2.15.0 here.

It worked fine for me: https://musicbrainz.org/edit/102911599

2 Likes
46

Can you please try again in test.musicbrainz.org (password is mb) then give me the link to your edit?

Here is a test from me: https://test.musicbrainz.org/edit/100290493
Your latest merge edit still says version 2023.5.17 (It’s just what you typed but I’d like to make sure): https://musicbrainz.org/edit/102770246

47

That’s because I haven’t actually done any edits last few days, too busy with other stuff in my life.
Just a few merge tests to see if I could somehow get the note appearing is all I’ve been doing.
The latest https://test.musicbrainz.org/edit/100290494 was still a failure, no other add-ons/extensions/scripts. Bummer. Can’t test more today.

Edit1: “Merging into oldest” line is added after all, it’s just not visible in the edit note box before submitting ! Now I cannot recall was it always like that?

Edit2: And it appears also now with Brave: https://musicbrainz.org/edit/102933568

Thanks a ton for your time! And I really gotta bugger off for today

1 Like