Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
This fix looks okay to me but it's beyond the scope of the NATs module. And I'm wondering if this can be fixed in the NATS module instead of the core. The change you made here is probably called from nats in cfg_update. I wonder if @miconda has any insight
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.