Problem details:
https://osu-ppy-sh.zoneani.me/beatmapsets/1649315#osu/3379930
The BeatmapID obtained in the url is 3379930, but the BeatmapID in the ed file content is 3384601, no check before entering the ranked queue?

Yes this happens a lot because mappers do weird stuff for reasons that aren't entirely clear to me, and it also breaks lazer (maps will show as unranked there because of this) and it's not super easy to fix without losing people's local scores on stable. This is what happens when you allow manual editing...

New submission in lazer will probably prevent this from happening. Not sure about existing maps, or old BSS.

This issue will prevent you from using bids to search in the stable.

Can this be avoided by forcing content checks when ing a Beatmap, or by doing additional checks when the Beatmap is about to enter the Ranked queue?

spaceman_atlas wrote: 5s2kx

it's not super easy to fix without losing people's local scores on stable.

The local score record is recorded using the file's hash string as the key, so I think changing only the bid will not cause score loss.

-Spring Night- wrote: 5x25n

Can this be avoided by forcing content checks when ing a Beatmap, or by doing additional checks when the Beatmap is about to enter the Ranked queue?

Maybe. Something we'll look at when reimplementing bss for lazer maybe.

-Spring Night- wrote: 5x25n

The local score record is recorded using the file's hash string as the key, so I think changing only the bid will not cause score loss.

Except every score replay contains the hash of the beatmap inside. Change the beatmap file post-rank to fix the beatmap ID (which will be in there for newer maps), and the hash of the beatmap changes, and thus the replay disassociates from the beatmap. And that's not the only thing retroactive action on all ranked beatmaps breaks now - trust us, we have tested this on a small group of maps.

spaceman_atlas wrote: 5s2kx

Except every score replay contains the hash of the beatmap inside. Change the beatmap file post-rank to fix the beatmap ID (which will be in there for newer maps), and the hash of the beatmap changes, and thus the replay disassociates from the beatmap. And that's not the only thing retroactive action on all ranked beatmaps breaks now - trust us, we have tested this on a small group of maps.

The value recorded in the .osu file is not occupied by other Beatmaps
Modify the Beatmap ID value recorded in the osu web backend so that it corresponds correctly
Is this operation feasible?

It's not as simple as changing a single beatmap ID 'somewhere in the backend' and I'm not exactly willing to go into the ugly details why at this point. We've tried the simple method in production and it verifiably broke stuff.

spaceman_atlas wrote: 5s2kx

It's not as simple as changing a single beatmap ID 'somewhere in the backend' and I'm not exactly willing to go into the ugly details why at this point. We've tried the simple method in production and it verifiably broke stuff.

Ok, Lastly, I would like to ask, if stable is completely phased out, is it possible to fix this?