Ensure that multiple BeatmapSetInfo
with same OnlineID
don't cause import failures
#19121
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This really shouldn't happen but I managed to make it happen while working on re-downloading already present beatmaps. Realm doesn't provide any kind of unique restrictions, so I figure this is a better way of handling the edge case where things are in a bad state.
Until this comes up again in a way that matters, let's just fix the LINQ crash from
SingleOrDefault
.