-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Refresh realm before performing song select refetches following an online metadata lookup #34723
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…line metadata lookup Probably closes ppy#34716 Can't see any other cause, can reproduce the issue on master using manual db modifications via realm studio and it is not a consistent reproduction, so seems like an open-and-shut lack of refresh.
| // which prevents working beatmap refetches caused by changes to the realm model of perceived low importance). | ||
| var status = realm.Run(r => | ||
| { | ||
| r.Refresh(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important to note that refreshes will block the update thread pending all write operations, which can sometimes lead to multi-second pauses.
This is why we seldom use Refresh().
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aware. Unless I make the "online" beatmap set retrieval method also return the state of the database beatmap set model, there's not much room for maneuvering as far as I can tell.
|
as per discord conversation this is apparently unacceptable due to perceived chance of resulting performance regression, closing |
|
Reopening after extended discussion around #34737. |
Can't see any other cause, can reproduce the issue on master using manual db modifications via realm studio and it is not a consistent reproduction, so seems like an open-and-shut lack of refresh.