Skip to content
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

Ensure qualified beatmaps are never looked up on stale cache source #32329

Merged
merged 3 commits into from
Mar 11, 2025

Conversation

peppy
Copy link
Member

@peppy peppy commented Mar 11, 2025

As i proposed here.

I experimented with nuking the local database immediately, but this seems cleaner and less prone to fail.

@peppy peppy added the area:beatmap-change-tracking sync of local-online metadata and status label Mar 11, 2025
@smoogipoo smoogipoo requested a review from bdach March 11, 2025 08:35
Copy link
Collaborator

@bdach bdach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than the blocker below I guess in principle this works.

One thing I'll remark on is that with this if you try and import a qualified beatmap while not being logged in it won't get an online status at all, which I guess is a foregone conclusion anyway given the online.db changes have rolled out, and it's a long-standing concern anyway (really need to make the lookup endpoint accessible without auth at some point)

Co-authored-by: Bartłomiej Dach <dach.bartlomiej@gmail.com>
@bdach bdach merged commit a2966d9 into ppy:master Mar 11, 2025
6 of 10 checks passed
@peppy peppy deleted the local-cache-nuke branch March 12, 2025 04:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:beatmap-change-tracking sync of local-online metadata and status size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants