Cover ttl=0 (expire always) _DNSCacheTable case (#7014) #7045
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix bug when using ttl_dns_cache=0
When using `ttl_dns_cache=0`, hostname is added to cache and on expire check there is a KeyError as it is never added into _timestamp dictionary.Added a short description to docs ClientSession advising to use
use_dns_cache
instead ofttl_dns_cache=0
for always expiring cache.Alternative to this change is to enforce user to use positive none 0 float or None for
ttl_dns_cache
during init time and in case of using 0 implicitly changeuse_dns_cache
to False or raise exception. No.CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature. *.bugfix
: Signifying a bug fix. *.doc
: Signifying a documentation improvement. *.removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.Co-authored-by: Sam Bull [email protected]
(cherry picked from commit 12f56d7)
What do these changes do?
Are there changes in behavior for the user?
Related issue number
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.