Closed ghost closed 3 years ago
Could you please test again on the latest master?
@peppy It still got exit when timeout
I've uploaded full log output here: https://pastebin.com/QaX2K1NB The way I reproduce this issue is disconnect the wireless while downloading a beatmap from osu!direct.
Thanks. A slightly different case which I'll look into. Can you confirm the above behaviour is fixed though? ie. your network reconnects and starts working again after a failure
The above is fixed. I think now it's trigger from the different place.
It's wired, I am not familiar with C# but I just set up Rider to dig into this issue.
Seems like the Exception was not throw from the BeatmapManager
but the Scheduler
. Why the Exception instance is the previous one?
Yeah I have a good idea of why the new one you found is happening, should be fixed for today's release.
@BinotaLIU confirm if this is fixed?
Closing as probably-fixed.
Describe your problem:
Process exit due to request timeout.
Screenshots or videos showing encountered issue:
N/A. See stack trace below.
osu!lazer version: 4b0cad145581441cb44c41b2241c0b4352770ff6
Logs:
Computer Specifications: OS: Arch Linux 4.19.7-arch1-1-ARCH .NET Core SDK: 2.2.100