Aleksandr Antonov

I found a corner case with **Any** return annotation, so code block getting bigger, and now it's should be separated for sure. Raw&Dirty implementation: _(fastapi/routing.py, line 600)_ ``` from typing...

Upd.

Any activity on this integration?

> Hi @AbstractiveNord, thanks for the question: > > We have a NATS connector recently built by the community - https://github.com/infinyon/nats-connector > > Does this help? Or is there something...

> > > Hi @AbstractiveNord, thanks for the question: > > > We have a NATS connector recently built by the community - https://github.com/infinyon/nats-connector > > > Does this help?...

> Thanks for the discussion everyone! Yep, as some have said, this is particularly important when returning something different than what you want FastAPI to send in the response. Maybe...

Recently Jeremy from NATS team released video about Jetstream KV, and mentioned example toy project, leader election system. I've tried to implement that project in Rust, and got two problems....

Awesome news about `create` method, thanks a lot, but still, errors formatted with metadata, but doesn't contain metadata fields is problem.

> Server actually returns that information, unfortunately as a part of the string description. Wait a little, did I got this correctly. Server doesn't clearly return metadata such as last...

> Server returns the error code (`10071` in this case), with a description `wrong last sequence: {seq}`. Should that behavior reported to server team as problematic? It's kinda weird, cause...