Closed joseph-ireland closed 3 years ago
out of curiosity, why do some osu files in the dump error / what do they throw?
Here's a log for the latest dump: library_log.txt
thanks - the dump seems to conveniently double as a stress test for slider. We've seen a few of these before:
OverflowError: Python int too large to convert to C int
is #83
ValueError: cannot convert float NaN to integer
is #84
(these may in fact be caused by the same underlying issue; I haven't investigated). The rest are new.
I think a lot of them are files that break the spec but just happen to parse in osu. There's one that has no new line after [TimingPoints], there's a load which have floating point values where there should be an integer, and a few that are invalid UTF-8.
as an aside, since you've made a few PRs to this repo, I'll mention that the standard convention for naming git branches is with dashes instead of underscores: allow-library-parse-errors
.
…, which allows creating a library using beatmap dumps from data.ppy.sh