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
Currently, if you try to connect by passing a list of incomplete URLs (e.g., ["nats://nats", "nats://nats-1", "nats://nats-2"] or ["nats", "nats-1", "nats-2"]), the client fails to connect, while connecting using just one of the items from the list is successful.
Expected behavior
Essentially, when a URL is passed as a single string, it gets normalized, but when taken from a list, this does not happen.
Server and client version
NATS server (Docker image): 2.10.14
NATS Python client: 2.7.2
Host environment
Host environment not relevant
Steps to reproduce
Writing incomplete URLs as below will result in a connection refused exception
Observed behavior
Currently, if you try to connect by passing a list of incomplete URLs (e.g., ["nats://nats", "nats://nats-1", "nats://nats-2"] or ["nats", "nats-1", "nats-2"]), the client fails to connect, while connecting using just one of the items from the list is successful.
Expected behavior
Essentially, when a URL is passed as a single string, it gets normalized, but when taken from a list, this does not happen.
Server and client version
NATS server (Docker image):
2.10.14
NATS Python client:
2.7.2
Host environment
Host environment not relevant
Steps to reproduce
Writing incomplete URLs as below will result in a connection refused exception
The following code snippets will run fine:
The text was updated successfully, but these errors were encountered: