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

fix: catch pp wrong due to both acc and judgements specified #627

Merged
merged 7 commits into from
Feb 26, 2024

Conversation

minisbett
Copy link
Contributor

Describe your changes

PP breaks on catch if both the accuracy and the 50s are specified. In VC we argued the best way to solve this is raising an exception in the usecase, and dropping specifying acc where possible, since it's a useless info.

This PR fixes catch PP, meaning bancho.py hosters will need to re-calculate all PP. Before doing this, I'd suggest looking into #573, as it improves the functionality of the recalc script and might be significant with this change.

Checklist

  • I've manually tested my code

app/usecases/performance.py Outdated Show resolved Hide resolved
@tsunyoku
Copy link
Contributor

bug fixes like this are really good candidates for adding unit tests to cover imo

@NiceAesth NiceAesth changed the title fix: catch pp wrong due to both acc and jdugements specified fix: catch pp wrong due to both acc and judgements specified Feb 19, 2024
tools/recalc.py Show resolved Hide resolved
app/usecases/performance.py Outdated Show resolved Hide resolved
cmyui
cmyui previously approved these changes Feb 26, 2024
@cmyui cmyui enabled auto-merge (squash) February 26, 2024 13:36
@cmyui cmyui merged commit 6b64b8b into osuAkatsuki:master Feb 26, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants