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
We uses NATS.Client in our code but nBomber is using an older version which creates conflicts for us, and we cannot downgrade as we need feature used in 1.1.2.
Our workaround is for us to remove our usage of NATS immediately. But this is only a temporary solution because we will have it soon as a hard requirement. We are using NATS JetStream, which is not available in the outdated NATS client NBomber is referencing to. And Upgrade should be harmless. Our problem is that NATS client changed their connection interface and thus the library is breaking now. I would suggest
Updating NATS client to > 1.1.0
Pin the version within the minor so only >1.1.0 and < 1.2.0 is allowed. This gives clear compile errors rather than the runtime errors we see. NATS seems to break backwards compatibility within minor versions.
But the issue is not the NATS server version, its that the client broke backwards compatibility but its not detected proper (because NBomber does not define a < version requirement). I have to say, its shitty from NATS to break it, because I would assume backwards compatiblity between minor versions
The text was updated successfully, but these errors were encountered:
AntyaDev
changed the title
Backwards compatibility issues with NATS
Backwards compatibility issues with NATS Client
May 2, 2024
We uses NATS.Client in our code but nBomber is using an older version which creates conflicts for us, and we cannot downgrade as we need feature used in 1.1.2.
Our workaround is for us to remove our usage of NATS immediately. But this is only a temporary solution because we will have it soon as a hard requirement. We are using NATS JetStream, which is not available in the outdated NATS client NBomber is referencing to. And Upgrade should be harmless. Our problem is that NATS client changed their connection interface and thus the library is breaking now. I would suggest
But the issue is not the NATS server version, its that the client broke backwards compatibility but its not detected proper (because NBomber does not define a < version requirement). I have to say, its shitty from NATS to break it, because I would assume backwards compatiblity between minor versions
The text was updated successfully, but these errors were encountered: