-
Notifications
You must be signed in to change notification settings - Fork 398
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
fix(flask-caching): support v2.0 #3882
Conversation
b53feb4
to
9962f41
Compare
flask-caching released version 2.0 which for some reason results in different tag data and breaks our tests. Pin the flask-caching version for now until we can update the tests or fix the integration.
9962f41
to
eaebf56
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this pr be a fix
instead of a chore
? If so we should update the PR title and add a release note
yeah idk. It's a "fix" I suppose since we technically support the latest version of |
eaebf56
to
cd7b3aa
Compare
@Mergifyio backport 1.2 1.1 1.0 0.x |
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770)
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770)
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770)
✅ Backports have been created
|
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770)
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770) Co-authored-by: Kyle Verhoog <kyle@verhoog.ca>
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770) Co-authored-by: Kyle Verhoog <kyle@verhoog.ca>
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770) Co-authored-by: Kyle Verhoog <kyle@verhoog.ca>
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770) Co-authored-by: Kyle Verhoog <kyle@verhoog.ca>
@Mergifyio backport 0.61 |
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770)
✅ Backports have been created
|
## Description flask-caching released version 2.0 which moves the cache client to a new library called [`cachelib`](https://github.com/pallets-eco/cachelib). Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0 This breaks our logic which collects tags for the redis client. ## Fix It was noticed that both `_write_client` and `_read_client` use the same connection information so we don't need to dynamically check for each. Also [`_read_clients`](https://github.com/pallets-eco/flask-caching/blob/ac13e01baa11d65c68dcba64f99ccaafd9b5419c/src/flask_caching/backends/rediscache.py#L62) was moved to [`_read_client`](https://github.com/pallets-eco/cachelib/blob/13c8bf8db156dd06154f5e08e23bdd9e73480a5b/src/cachelib/redis.py#L29) when the logic was moved to `cachelib`. (cherry picked from commit 94b0770) Co-authored-by: Kyle Verhoog <kyle@verhoog.ca> Co-authored-by: Munir Abdinur <munir.abdinur@datadoghq.com>
Description
flask-caching released version 2.0 which moves the cache client to a new library
called
cachelib
.Diff here: pallets-eco/flask-caching@v1.10.0...v2.0.0
This breaks our logic which collects tags for the redis client.
Fix
It was noticed that both
_write_client
and_read_client
use the same connection informationso we don't need to dynamically check for each.
Also
_read_clients
was moved to_read_client
when the logic was moved tocachelib
.Checklist
feat
andfix
pull requests.Reviewer Checklist
changelog/no-changelog
label added.