nats sub --stream does not respect the --js-domain flag about natscli

[ripienaar]

Yes, fixed here b213da1 and not yet released.

[ripienaar]

Thanks for the report,

Do you mind adding --trace to the command arguments?

Here you can see picking a domain does result in the API trying to access the stream in the domain:

$ nats sub --stream X --js-domain foo --trace
09:40:09 >>> $JS.foo.API.STREAM.INFO.X

this indicates its accessing the domain correctly

[Zambito1]

nats --js-domain A s add foo
nats --js-domain B s add bar

nats pub foo.foo foo
nats pub bar.bar bar

nats --js-domain B sub --stream foo --trace # Note, foo is on domain A
<<< Reply Subject: $JS.ACK.foo.OKmk1lpA.1.1.1.1718197970030690510.0
[#1] Received JetStream message: stream: foo seq 1 / subject: foo.foo / time: 2024-06-12T09:12:50-04:00
foo

nats --js-domain B sub --stream bar --trace
nats: error: nats: stream not found

nats --js-domain B s ls # Shows bar with 1 message

[ripienaar]

The —trace flag is only useful if you show the new output like in my example.

[Zambito1]

Sorry, I'm not sure what you mean. Are you referring to the output of the sub --stream bar --trace? If so, I copied the output verbatim:

[Zambito1]

Same with the sub --stream foo --trace:

[ripienaar]

Ok perhaps the trace behaviour are in main only. To me this seems fixed for the next release.