You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding MySqlErrorCode.UnableToConnectToHost in many more places, except when the client connection string is clearly bad (e.g., specifying a client key file that doesn't exist); these seem like "more fatal" errors that can't be fixed by retrying. There didn't seem to be an existing appropriate MySqlErrorCode value for these exceptions.
When
SslStream.AuthenticateAsClientAsync
fails, aMySqlException
with error code 0 is thrown. It should beMySqlErrorCode.UnableToConnectToHost
.Note that this will break some clients that are currently detecting error code 0: #621 (comment)
In general, all exceptions along the connection path should use
UnableToConnectToHost
.The text was updated successfully, but these errors were encountered: