-
$ nats --user=root --password=aaaaaa account info
```
Connection Information:
Client ID: 17
Client IP: 127.0.0.1
RTT: 152.236µs
Head…
-
### Observed behavior
Creating a stream via the rust client with a subject of `"*.*.*.*"` or `"*.*.*" ` causes unexpected behaviour when listing streams via the cli. In addition, it will cause subs…
-
I am using helm to deploy NATS on k8s and have a 3 node cluster.
The moment one of the nodes goes down, the rest of the NATS is inaccessible.
Is there something I am misunderstanding about the clust…
-
### Affected project(s)
- [ ] documentation
- [ ] examples
- [ ] wasmCloud host
- [ ] wasmCloud CLI (wash)
- [ ] wasmCloud dashboard UI (washboard)
- [X] capability providers
- [ ] provider bindgen
-…
-
### Proposed change
### Proposed change
Implement the new API for pausing consumers.
The Server PR with related change has been merged here: https://github.com/nats-io/nats-server/pull/5066
…
-
# Observed behavior
When I call NatsKVContext.GetStoreAsync(…) for a bucket/store that was created using the NATS CLI, I get a `System.Text.Json.JsonException`:
Message: `JSON deserialization f…
-
### Observed behavior
When I use nats.jetstream.CreateKeyValue after changing TTL, I got error "nats: stream name already in use"
### Expected behavior
I use nats.jetstream.CreateKeyValue and…
-
### Observed behavior
When the host running `nats-server` ran out of disk space, the durable message stream I was running stopped accepting new messages despite having a discard policy set to "old"…
-
**Problem**
There is `knative.dev/eventing` golang library, it has `channel` package. There is `MessageDispatcher` in `channel` package. Simplified diagram how it is working:
![image](https://github…
-
### Observed behavior
With code below it looks like the backoff is not in effect. Also there is no reference anywhere in the [source](https://github.com/nats-io/nats.net.v2/blob/56f831f8e59091aa91b…