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
I have created a repository https://github.com/bredtape/nats_kv_watch_fail to recreate the issue. It includes an extra test TestKVWatchWhatWorks to document that the Get and the OrderedConsumer works.
Observed behavior
Given a nats-server configured with 2 accounts: KV1 and KV2. Then a key-value store is created in KV1 and exported and imported in KV2.
KV2 can perform Get but Watch (and related operations like WatchAll, ListKeys) will block with no messages delivered.
Also, the backing stream can successfully be read with the OrderedConsumer.
Expected behavior
KeyValue.Watch should deliver all existing entries, but blocks with no messages delivered.
Server and client version
nats-server v2.10.24
nats.go v1.38.0
Host environment
Ubuntu v24.04.1 LTS
Docker v27.5.0
Docker compose v2.32.4
Steps to reproduce
I have created a repository https://github.com/bredtape/nats_kv_watch_fail to recreate the issue. It includes an extra test
TestKVWatchWhatWorks
to document that the Get and the OrderedConsumer works.nats server.conf:
Golang unit test:
logs.txt
The logs indicates that a message is pending
"num_pending:" 1
:The text was updated successfully, but these errors were encountered: