Scott Fauerbach

There is a full specification for reconnect behavior. In my head right now, but partially started in this ADR https://github.com/nats-io/nats-architecture-and-design/pull/202. I will work on it. @mtmk Please see me in...

Originally reported as a discussion in the Java repo: https://github.com/nats-io/nats.net/discussions/905

> Can this be re-produced against main? I used the data with 2.10.17 the first time I was able to reproduce it. I only checked the older versions after Wally...

@ripienaar @piotrpio The go client might be correct but I would verify. I found a bug in the java/.net v1 libraries. On the connection to the leaf, it's correct to...

I think I followed the KV spec My problem was when creating a consumer, I treated the consumer filter subject as something that had to be domainified. Creating the consumer...

@tinder-marissanovak 2.20.1 has been released, which might have additional fixes for reconnect. Thank you for your feedback and patience.

@matthewadams We are currently looking at how we can improve integration with Kotlin, and this will make the list.

If JetBrains is involved, wouldn't it stand to reason that their library will adhere to any collaboration they are part of? Can you please point me to any official statements...

I'm inclined to make the change, especially since it's basically a search and replace of the import. I don't have to do the effort to put a class wide annotation...

@hjk235456 You said: > When the number of reconnection times is set to -1 and the server is down, messages are stacked in the queue and will not be consumed....