nats-io/nats-box

nats-rply/nats-req not working

aricart opened this issue · 5 comments

nats-rply/req doesn't seem to be honoring the -s flag

docker run --network host -ti synadia/jsm:nightly
             _             _               
 _ __   __ _| |_ ___      | |__   _____  __
| '_ \ / _` | __/ __|_____| '_ \ / _ \ \/ /
| | | | (_| | |_\__ \_____| |_) | (_) >  < 
|_| |_|\__,_|\__|___/     |_.__/ \___/_/\_\
                                           
nats-box v0.3.0
docker-desktop:~# nats-rply -s demo.nats.io hello "hi there!"
nats: no servers available for connection
❯ docker run --network host -ti synadia/jsm:nightly
             _             _               
 _ __   __ _| |_ ___      | |__   _____  __
| '_ \ / _` | __/ __|_____| '_ \ / _ \ \/ /
| | | | (_| | |_\__ \_____| |_) | (_) >  < 
|_| |_|\__,_|\__|___/     |_.__/ \___/_/\_\
                                           
nats-box v0.3.0
docker-desktop:~# nats-req -s demo.nats.io hello ""
nats: no servers available for connection
docker-desktop:~# 

Hm. Yeah, I was able to reproduce as well. Will fix.
For now, here's a workaround:

NATS_URL=demo.nats.io nats-rply hello "hi there!"

Hm. nats-box itself seems to work. Not sure how synadia/jsm is built. Will keep looking.

$ docker run --network host -ti synadia/nats-box:latest
             _             _               
 _ __   __ _| |_ ___      | |__   _____  __
| '_ \ / _` | __/ __|_____| '_ \ / _ \ \/ /
| | | | (_| | |_\__ \_____| |_) | (_) >  < 
|_| |_|\__,_|\__|___/     |_.__/ \___/_/\_\
                                           
nats-box v0.4.0
synadiax1:~# nats-rply -s demo.nats.io hello "hi there!"
Listening on [hello nats-box]

Not sure about those, they are not used for jsm purposes. We need to retire then everywhere in favour of nats. They will not support any new features.

I think we may be able to close this since we've now deprecated this tool in #14.