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
This is pretty much the same as #471, just for consumer / durable names.
importnatsimportpytestasyncdefmy_cool_function():
nats=awaitnats.connect("localhost")
jetstream=nats.jetstream()
awaitself.jetstream.add_stream(
name="cool_stream",
subjects=["cool_service.*"],
)
# subjects can have dots in them, queue, durable, consumer names can'tjetstream.subscribe("cool_service.my_subject", "name.with.a.dot.in.it", my_callback)
awaitnc.close()
defmy_callback():
print("I'm a callback")
Running this code will trigger a "nats: timeout" error on the server side with no further information, not even when running the server in debug / trace mode.
Expected behavior
Arguably this should be handled properly on the server side and return a descriptive error message instead of running in a timeout. I might open up a ticket on the nats-server github later.
The official nats terminal cli throws the following
Observed behavior
This is pretty much the same as #471, just for consumer / durable names.
Running this code will trigger a "nats: timeout" error on the server side with no further information, not even when running the server in debug / trace mode.
Expected behavior
Arguably this should be handled properly on the server side and return a descriptive error message instead of running in a timeout. I might open up a ticket on the nats-server github later.
The official nats terminal cli throws the following
https://github.com/nats-io/natscli/blob/234eda9cb376add9f1fba4ddffe4ee9cbdb4ed33/cli/consumer_command.go#L1483
I expected nats.py to validate durable names before sending them to the server and throwing a similar exception.
Server and client version
server: 2.10.23
client: 0.1.5
nats.py: 2.9.0
Host environment
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: