mirror of
https://github.com/ppy/osu
synced 2024-12-20 05:42:54 +00:00
c78b5112c6
This time for `SocketException`s. I seem to recall looking at this and deciding there was a reason to not catch socket exceptions, but on revisiting it seems sane to do so. This covers a fail case like reported: ``` 2023-10-06 03:24:17 [verbose]: Request to https://lazer.ppy.sh/oauth/token failed with System.Net.Http.HttpRequestException: No such host is known. (lazer.ppy.sh:443) 2023-10-06 03:24:17 [verbose]: ---> System.Net.Sockets.SocketException (11001): No such host is known. 2023-10-06 03:24:17 [verbose]: at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken) ``` Closes https://github.com/ppy/osu/issues/24890 (again). |
||
|---|---|---|
| .. | ||
| API | ||
| Chat | ||
| Leaderboards | ||
| Metadata | ||
| Multiplayer | ||
| Notifications | ||
| Placeholders | ||
| Rooms | ||
| Solo | ||
| Spectator | ||
| BeatmapDownloadTracker.cs | ||
| DevelopmentEndpointConfiguration.cs | ||
| DownloadState.cs | ||
| DownloadTracker.cs | ||
| EndpointConfiguration.cs | ||
| ExperimentalEndpointConfiguration.cs | ||
| HubClient.cs | ||
| HubClientConnector.cs | ||
| IHubClientConnector.cs | ||
| ILinkHandler.cs | ||
| OnlineViewContainer.cs | ||
| PersistentEndpointClient.cs | ||
| PersistentEndpointClientConnector.cs | ||
| PollingComponent.cs | ||
| ProductionEndpointConfiguration.cs | ||
| ScoreDownloadTracker.cs | ||
| SignalRDerivedTypeWorkaroundJsonConverter.cs | ||
| SignalRUnionWorkaroundResolver.cs | ||
| SignalRWorkaroundTypes.cs | ||