nats.rs issues

[WIP] concrete error types

This PR experiments with concrete error types. Feel free to share ideas and feedback.

KV store blocks on calls to get all keys

6

## Problem Calls to get all keys blocks even when there is a non-zero number of keys in the store. Note that this call always blocks when there are 0...

segfaultdoc

Enable NATS Client to Run in WebAssembly

9

### Use case Deploying lightweight NATS-based microservices on edge devices is a compelling architecture for many applications and probably represents the most significant architecture of the near future. Some immediate...

andrew-goldie

enhancement

Don't force flush if write buffer isn't empty

1

It turns out `poll_write` could return `Poll::Pending` while `poll_flush` could flush successfully (`Poll::Ready`). This seems like a rare case, although possible in theory. This fixes it by actually making it...

paolobarbolini

additional useful derives

1

sunny-g

expose retry_on_failed_connect option

3

- Expose retry_on_failed_connect option - Debug error field ```rust #[tokio::main] async fn main() -> Result { async_nats::ConnectOptions::new() .retry_on_failed_connect() .connect("demo.nats.io")?; Ok(()) } ```

cn-kali-team

async-nats: Pull consumer issue: "pull request failed: request failed: missing field `stream_name` at line 1 column 129"

3

### Observed behavior We are creating a Stream, then creating a Consumer and finally listening to messages. We are getting this error in our logs. ``` {"message":"Nats error: 'pull request...

simon-connektica