Closed trading-peter closed 4 years ago
@pkaske - found it - the issue is if max
is set when the subscription is called a bogus subscription id is sent for the unsubscribe. As a workaround until I push a release in the next couple of days, you can do an sub.unsubscribe(n)
.
Thank you very much for pointing this issue.
I have released v1.2.15. npm install ts-nats@latest
Oh wow that was fast! Awesome 🙂 Thank you
If you run the following code the following is expected:
max
is set to 1.What actually happens is:
If you comment the inbox code out, everything is working fine.