Casper Beyer comments

Results 106 comments of


                                            Casper Beyer

jetstream examples should be merged

Key difference is that they create different configs, e.g `pull::Config` vs `push::Config`, these give different implementations of the internals. Pull example can probably be expanded to showcase fetch etc tho.

Subject should implement AsyncContextManager for auto-unsubscribe

On `Subscription`? but yes, pull request very welcome 👍

Missing option to control initial connection behavior

The initial connection is currently controlled by `allow_reconnect`. But I can raise a pull request with an equivalent of `RetryOnFailedConnect`.

Usage of mutable value in function signature of connect

Started moving over to GitHub Actions so we can turn on linting and formatting inline here https://github.com/nats-io/nats.py/pull/568

Enforce valid identifiers for "key value keys"

Might make sense to punt to `nats.jetstream` in that case.

Enforce valid identifiers for "key value keys"

Superseded by #706

Add ability to debug NATS communication

Probably via `logging`?

Race condition when creating a consumer

Thank you for the report, was initially unable to reproduce and took me a while to come up with a failing case. But I do get it to fail but...

Race condition when creating a consumer

Continuing to look into this, but it's a bit puzzling currently as request / reply inboxes seem to match up as expected based on server logs.

Race condition when creating a consumer

Based on server logs, server seems to be sending two responses to the request as the subjects are basically overlapping with JS prefix. ``` 2025/05/09 12:13:09.578133 [DBG] 172.17.0.1:57220 - cid:5...