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
The docs state that queue names can be divided by dots for hierarchical purposes:
Queue group names follow the same naming rules as subjects. Foremost, they are case sensitive and cannot contain whitespace. Consider structuring queue groups hierarchically using .
When using a queue name with dots and creating a queue subscription with QueueSubscribe the method returns an error: "context deadline exceeded". In js.go the Durable field is directly set from the queue argument without validation. When using the nats.Durable option the name is validated and does not allow for dots and returns an error: "nats: invalid durable name".
Versions of nats.go and the nats-server if one was involved:
When calling `js.QueueSubscribe[Sync](subject, queue_name)`, if
no durable name is provided, the queue name is used as the durable
name, so the same restriction applies
Resolves#840
Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
Defect
The docs state that queue names can be divided by dots for hierarchical purposes:
When using a queue name with dots and creating a queue subscription with
QueueSubscribe
the method returns an error: "context deadline exceeded". In js.go theDurable
field is directly set from thequeue
argument without validation. When using thenats.Durable
option the name is validated and does not allow for dots and returns an error: "nats: invalid durable name".Versions of
nats.go
and thenats-server
if one was involved:OS/Container environment:
Steps or code to reproduce the issue:
Expected result:
QueueSubscribe
returns "nats: invalid durable name".Actual result:
QueueSubscribe
returns "context deadline exceeded".The text was updated successfully, but these errors were encountered: