-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redis has changed their lock API in a backwards incompatible fashion #220
Comments
I would need to see a complete stack trace |
|
redis has been releasing in recent weeks and they changed this API to be positional only (even though I think main Python API is positional only, will check) |
Mike Bayer has proposed a fix for this issue in the main branch: repair backwards incompat redis lock changes https://gerrit.sqlalchemy.org/c/sqlalchemy/dogpile.cache/+/3904 |
they changed the API in release 4.3.2 |
FYI, It looks like Redis took over that project from https://github.com/andymccurdy sometime in the past 2 years. The original maintainer was often focused on API stability. |
Seems to be fixed in 4.3.3 redis/redis-py#2209 (comment) |
yeah....OK let me just run dogpile main in jenkins and we can close this |
it's still wrong |
submitter please pin to py-redis 4.3.1 until they fix this |
ok thanks, updated to |
I'm using the Redis backend and basically copied the code from the module in sqlalchemy that contains the CachingQuery class. However I am using manual keys.
With the following configuration I get the intermittent error in subject line.
regions["default"] = make_region(key_mangler=md5_key_mangler).configure( "dogpile.cache.redis", expiration_time=3600, arguments={ "host": config["redis"].get("host"), "redis_expiration_time": 60 * 60 * 2, "distributed_lock": True, "thread_local_lock": False, }, )
Here's the code where it occurs:
`
Any suggestions would be appreciated.
The text was updated successfully, but these errors were encountered: