include additional context in the error message.

[walkinggo]

(If this PR fixes a github issue, please add Fixes #<xyz>.)

Fixes #<1315>

(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)

Master Issue:

Motivation

New error to provide more detailed information, you can include additional context in the error message.

Modifications

modify the errors in connection waitUntilReady().

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (no)
• The public API: (no)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable / docs / GoDocs / not documented)
• If a feature is not applicable for documentation, explain why?
• If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

[RobertIndie]

What additional context do you want? It seems you've added unnecessary details to the log, such as "WARN[0009]" and "[::1]:6650".

[walkinggo]

Yes, I also think this is the problem. My error message depends on the example provided in the original issue. Actually, I’m not sure what kind of contextual information is needed. Could you give me some advice? @RobertIndie