Wait for score submission before processing quick play scores#394
Draft
smoogipoo wants to merge 1 commit intoppy:masterfrom
Draft
Wait for score submission before processing quick play scores#394smoogipoo wants to merge 1 commit intoppy:masterfrom
smoogipoo wants to merge 1 commit intoppy:masterfrom
Conversation
Member
|
What's the case here where it takes over 10 seconds? It's just going to fail as previously? Is there any better direction we can drive things in such a case? |
Contributor
Author
Yeah that's kind of what I want comments on. I'm out of ideas of how to handle this case :( My idea with 10 seconds is that it's the default o!f web request timeout, though I see now that |
Contributor
Author
|
Don't merge this yet, just realised I forgot a sleep delay. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes https://osu.ppy.sh/community/forums/topics/2160029?n=1
RFC. I'm not sure of a better way to handle this...
Normally, the server knows score submission completed by way of users getting into the
FinishedPlay state, but this is not the case in the failing scenario.The failing scenario is, that when a user quits gameplay score submission runs asynchronously in the background while the server thinks that it's complete by way of the user no longer being in the
Gameplaystate.This diff accurately reproduces the fixed issue:
Which now behaves like this:
2025-12-08.19-51-29.mp4