Sven Neumann
Sven Neumann
This, on the other hand, works. So it seems to be something with the Ubuntu image. ``` FROM python:3.10.6 RUN pip install nats-py==2.2.0 ```
Adding the option `--use-deprecated=legacy-resolver` to the `pip install` command allows me to install nats-py 2.2.0 in the Ubuntu based container, albeit with the wrong version: ``` Successfully installed nats-py-0.0.0 ```
It would be awesome if this could be merged, or at least reviewed, as this PR supposedly fixes https://github.com/nats-io/nats.py/issues/362
I am glad we are "only" using `nats.py` for testing. Still I wish there was more active maintenance. If we can somehow help, let me know.
Looks like this is most likely caused by https://bugzilla.gnome.org/show_bug.cgi?id=793955 We will include a fix for this in the next firmware update.
Did something happen here in the meantime? @orsinium, are you still willing to help?
> Sure I do! I have 6 PRs open that are waiting for a review/merge, but the only maintainer (@wallyqs) doesn't appear in nats.py since November. The Nats team currently...
> The library normalizes errors from the underlying transport (like TLS errors) because the transport layer is pluggable and not all errors map directly. The intended method for handling this...
> We can take a look, but in general that many filtered subjects might warrant a design review. Wildcards can be used to dramatically lessen the number of subjects needed....
We have created a benchmark that allows to easily reproduce the problem reported here: https://github.com/holoplot/nats-bench