Detailed error message for 'ConnectErrorKind' and 'ServerError'

[eschmidt-WI]

Proposed change

As a user I wanna see a detailed error message when something is wrong.

Currently the types ConnectErrorKind and ServerError doesnt contain detailed error messages just error types.

When the user has no access to the log of the nats-server he can't check what exactly is going wrong.

Use case

The user needs access to the log of the nats-server to check what is going wrong.
However, he may not have access to it.

At my setup I use the nats auth callout and the clients authenticate with an oauth2 access token (from client credentials flow).

When the auth service returns an error (e.g. Access Token expired, Invalid Token, ..) via the auth callout response it gots logged inside the nats-server. But the Client only got the error type "AuthorizationViolation". So the client can't decide if he needs to fetch a new token or something other went wrong (e.g. missing permissions).

Contribution

No response

[Jarema]

Hey.
First of all, you can always check source, even if the error is not explicitly nested. However, in this case, I'm afraid that that's all that server sends back - just Authorization Violation.