Albert Callarisa
Albert Callarisa
Still happening to me with a fresh phoenix and addict project. Anyone else still having this issue as well?
I've tested running that piece of code using your PR and still shows `Received: 1, Processed: 0`. I don't think it's waiting for in-flight messages to be acked.
1.3.2 from npm
Tried 1.2.9 and doesn't seem to be happening.
Looking at the code I've found this: https://github.com/streamproc/MediaStreamRecorder/blob/62ab10e75c3b6d64160f0c263c2be9ff656e5ee1/AudioStreamRecorder/MediaRecorderWrapper.js#L93 The blobs I'm getting have a size of around 300. Maybe ignoring blobs smaller than ~500 would make sense? What's the reason...
I think 1.2.9 works because it uses Whammy instead of MediaRecorderWrapper.
Any progress so far?
I'm not aware of all usecases, but it seems that if `AckAck` and `AckNext` are two different things, there should be also `AckNak` and `AckNakNext`, in case one wants to...
That's fine, isn't it? The message will just get redelivered. Adding a backoff functionality would be great, but if that functionality is missing, as a client of jetstream I shouldn't...
In our usecase we NAK the message when there's an error during the handler. We try again the message a few times and after some attempts we just send it...