jetstream
jetstream copied to clipboard
mmmries
an Elixir client for NATS Jetstream
While trying to use this library to obtain the `pending`/`num_pending` count for a given consumer, I noticed that information is advertised in the typespec but not made available at all...
The current implementation is essentially "single-threaded" since it requests a single message and then wait for it to arrive, then we handle that message before sending back the `ACK` or...
Hello, hope all is well. I really appreciate that has been put in to bring this library up to speed. I have seen in a few of these issues the...
I'm working on #36 and thinking about #41 and one thing that feels a bit awkward to me is the fact that our `init/1` callback returns a `state` term which...
Similar to #39 I think we want to help user code deal with unexpected errors being raised or process exits. This can often come from things like a statement timeout...
I noticed that we are using a very simple `case` statement to enforce the behaviour of the `PullConsumer` which means that if a user ever implements a function that has...
In order to let `PullConsumer` be full `GenServer` derivative, we must implement missing `code_change/3` callback functionality. I'm not sure if this won't require more sophisticated support under the hood. See:...
In order to let `PullConsumer` be full `GenServer` derivative, we must implement missing `terminate/2` callback functionality. It should be called when the process dies, not necessarily when connection disconnects. See:...
Allow `Jetstream.PullConsumer.handle_message/2` callback return `{:stop, reason, new_state}` tuple. It should behave exactly the same as it would be returned from GenServer's `handle_call/2` or Connection's counterparts.