-
### Observed behavior
`async_nats::connect` ignores all options in nats url and use default options
### Expected behavior
parse options from url
### Server and client version
bug is in crate `asy…
-
### Observed behavior
I have a NATS instance configured with a "store_dir" config set to some folder.
Whenever I attempted connecting with MQTT, the connection got cancelled and the NATS log display…
-
### Observed behavior
```
let nc_main = ConnectOptions::with_jwt(jwt, move |nonce| {
let keypair_clone = keypair_clone.clone();
async move { keypair_clone.sign(&nonce).map_err(…
-
### Observed behavior
NATS Alpine image (NATS 2.10.19) with Jetstream enabled is deployed in a three-node cluster within a Red Hat OpenShift environment. A headless service is exposed for application…
-
### Observed behavior
When using the `allow_responses` map in user permissions with `max` set, request/reply takes a significant performance hit depending on the value of `expires`. If the `max` valu…
-
### Observed behavior
Consumer Last Delivered Message is way ahead of stream Last Sequence. This makes consumer stop delivering messages.
### Expected behavior
Consumer delivered message should nev…
-
When putting heavy load to nats receivers the nats service will possibly redeliver events and therefore duplicate them. This is because we do not configure it correctly.
When pulling events from t…
-
### Expected Behavior
NATS Consume task should be able to consume from NATS topic.
### Actual Behaviour
NATS Consume task is unable to connect to the NATS server. Here is the error:
```
2024-03…
-
### Describe the bug
I would like to report a bug regarding NodeID consistency. Currently, the NodeID does not remain the same when the container is recreated. Ideally, the NodeID that was initiall…
-
### What version were you using?
```
$ docker image ls --format "table {{.Repository}}\t {{.Tag}}"
REPOSITORY TAG
nats …