You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice if there was a way to set infinite timeout, --timeout=0 exits immediately and --timeout=-1 is an invalid option (similar for --count).
This would be useful for a couple of reasons:
Allow simulation similar to an infinitewhile() loop
Allow better testing of retries, for example one nats instance with --no-ack and then waiting for retry timeout
Yes, arguably you could set a long timeout, but something like -1 = infinite would be "cleaner" and more deterministic (and obvious when writing docs).
The text was updated successfully, but these errors were encountered:
Would be nice if there was a way to set infinite timeout,
--timeout=0
exits immediately and--timeout=-1
is an invalid option (similar for--count
).This would be useful for a couple of reasons:
while()
loop--no-ack
and then waiting for retry timeoutYes, arguably you could set a long timeout, but something like
-1 = infinite
would be "cleaner" and more deterministic (and obvious when writing docs).The text was updated successfully, but these errors were encountered: