Fix issue in handle_get_user_music_api_request for Chunithm where songs would not always return all scores #92
No reviewers
Labels
No Label
aimedb
bug
chuni
chusan
cxb
database
diva
doc
duplicate
enhancement
frontend
help wanted
idac
idz
invalid
maidx
ongeki
pokken
question
seen
system
testing
wacca
waiting
wip
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Hay1tsme/artemis#92
Loading…
Reference in New Issue
No description provided.
Delete Branch "Kumubou/artemis:develop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally reported in issue #91:
I think I managed to find the source of the issue, in titles/chuni/base.py -- there's seemingly a block of code that goes over the resulting song list and then insert scores:
Except the current code only looks at the last song in the list, when it really needs to be checking every song, as the entries in chuni_score_best are not guaranteed to be in any order (they're IDed as they happen on profiles).
I managed to fix this on my local instance by instead iterating over every song and every entry in chuni_score_best after the last one checked:
I haven't tested this beyond my local profile and a couple of test profiles, so this may still lead to things exploding.
This pull request is to have that change applied.
Fix issue in handle_get_user_music_api_request where songs would not always return all scoresto Fix issue in handle_get_user_music_api_request for Chunithm where songs would not always return all scoresHi Kumubou
I should be able to have this tested by the end of the week if not earlier, I'll see if this fixes one of the issue i've noticed with scores that randomly disappeared and reappeared after a card-in.
Thanks
PR tested working, merging!