redis-py

If you want to go down that route, any function that has, or doesn't have, any given resource is colored then. fn foo(db: *Db) !void { ... } fn bar() !void { ... } Would you consider `foo` a blue function and `bar` a red function? That doesn't seem particularly helpful to me. The virality of async await is that once you mark a function async, then you can only call it from another async function, which forces you to mark more functions async, which in turn means that if you want to use blocking I/O APIs then you just can't because it's incompatible with your execution model because by daring to express asynchronicity of operations, you were forcefully opted into stackless coroutines. That's what Zig solves, and that's what is real function coloring. People have written reimplementations of the same libraries multiple times because

Hi HN! This is my first open source package. PyCharm used to have a nifty tool to show you requirements.txt packages that needed updates. You could click a button and open the github page, click a button to upgrade, all in the file. It was super convenient. Then it went away. The package was written in a few languages that I have no experience with, but I figured I'd build something that worked for my use case, and maybe it can help you, too. After installing, you point it at your requirements.txt file, and it will spit out something like this: ---- File caching enabled The following packages need to be updated: requests: 2.28.0 -> 2.31.0 [minor] - Pypi page: https://pypi.python.org/project/requests/ - Homepage: https://requests.readthedocs.io - Changelog: https://requests.readthedocs.io/en/latest/community/updates/... redis: 4.5.0 -> 5.0

There is a 1 year old autoclosed issue which is very similar to OpenAI's issue: https://github.com/redis/redis-py/issues/2028

According to this is not fixed yet... https://github.com/redis/redis-py/issues/2624

Commit fixing the bug: https://github.com/redis/redis-py/commit/66a4d6b2a493dd3a20c...

The original issue report is here: https://github.com/redis/redis-py/issues/2624 This bit is particularly interesting: > I am asking for this ticket to be re-oped, since I can still reproduce the problem in the latest 4.5.3. version Sounds like the bug has not actually been fixed, per drago-balto.

Nice writeup, it's fair in the content presented to us. Yet I'm wondering why there is no checking if the response does actually belong to the issued query. The client issuing a query can pass a token and verify upon answer that this answer contains the token. TBH as a user of the client I would kind of expect the library to have this feature built-in, and if I'm starting to use the library to solve a problem, handling this edge-case would be of a somewhat low priority to me if the library wouldn't implement it, probably because I'm lazy. I hope that the fix they offered to Redis Labs does contain a solution to this problem and that everyone of us using this library will be able to profit from the effort put into resolving the issue. It doesn't [0], so the burden is still on the developer using the library. [0] https://github.com/redis/re

The PR: https://github.com/redis/redis-py/pull/2641 According to the latest comments there, the bug is only partially fixed.

Their post-mortem [0] says the bug was in redis-py, so not FastAPI, but it was similarly due to a race condition in AsyncIO. I wonder if tiangolo had some role in fixing it or if that's just a coincidence. I'm guessing this PR [1] contains the fix (or possibly only a partial fix, according to the latest comment there). [0] https://openai.com/blog/march-20-chatgpt-outage [1] https://github.com/redis/redis-py/pull/2641

the library is provided by the redis team themselves and the bug is awful [1]. I know it's not redis' fault but this bug could hit anyone. Connections may be left in a dirty state where they return data from the previous request in the following one. [1] https://github.com/redis/redis-py/issues/2624

The emphasis could also have been done to educate folks using this combination to check their setup. Though version reference in the postmartem should also be posted, as a general guidance to their own readers, but at least a quick google search leads you to it. https://github.com/redis/redis-py/releases/tag/v4.5.3 For anyone reading this and using a combination of asyncio and py-redis, please bump your versions. Similar issues I've encountered with asyncio python and postgres too in the past when trying to pool connections. It's really not easy to debug them either.

The bug: https://github.com/redis/redis-py/issues/2624

Hey, I wanted to chime in and say that I too am underwhelmed with the support for async in Python libs. Coming from a node.js background, it falls short because you constantly have to think about whether async code is calling sync code, or vice versa, and whether you need an executor, threadpool, etc. Just a mess that gets in the way of productivity IMO. However, things have been getting better, and in case you haven't seen it, AIORedis[0] appears to be the de facto standard for async in Python (a little better with 1,724,389 downloads this month). It's popular enough that it's been merged with the official redis-py driver[1]. [0] https://aioredis.readthedocs.io/en/latest/ [1] https://github.com/redis/redis-py/releases/tag/v4.2.0rc1