-
I started NATS Server with Docker and added the parameter - n my-nats-ser1-m 18080-c NATS.config. The config. txt file has also been configured.
![a058262ebfd3db513116323569da57e](https://github.com/…
-
### Observed behavior
Hello.
We have detected high disk write load on some servers of the NATS cluster. (up to 100 MB/s)
Restarting the NATS server helps reduce the disk load.
We had no id…
-
I am working on e posing this bad boy over nats.
there is a good rust Nats driver
this then allows the library to be able to be controlled from any language that nats supports which is about 20…
-
### Observed behavior
Calling `await foreach (var key in store.GetKeysAsync())` cause connection leak
### Expected behavior
No connection leak should be occured
### Server and client version
NATS…
-
### What problem are you trying to solve?
a services does not run as a service.
```sh
devbox global services ls
No services currently running. Run `devbox services up` to start them:
caddy
…
-
## Defect
When a leaf node has a stream configured with work queue policy and this stream is aggregated on a remote stream, there is a chance messages will be silently dropped if a network outage o…
bjurr updated
1 month ago
-
### Proposed change
Talking about JetStream specifically (because I'm using it). When messages are received by a consumer, that can `nac` the message with delay. so the delay (some sort of support)…
-
### Observed behavior
Description: The app crashes in the ConnectionHandler.connect() method of nats.swift when the app is either idle for an extended random period or has been moved to the backgro…
-
**Describe the bug**
According to the [documentation](https://kubectl.docs.kubernetes.io/references/kustomize/builtins/#_helmchartinflationgenerator_) of the helm inflator it shall be possible …
-
### Observed behavior
Publish messages to a stream which is not existed, then the client panic
```
panic: runtime error: slice bounds out of range [14:0]
goroutine 2369 [running]:
github.com/n…