Cache init parametes bug
See original GitHub issuehttps://github.com/ipinfo/python/blob/master/ipinfo/handler.py#L42
In case cache_options
was defined, we end up “re-seinding” it, after having retrieved maxsize
and ttl
from the same dictionary. This way we multiply the same parameter in the function call, thus it can’t perform.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
gc: requires loading parameters files · Issue #7585 · iterative/dvc
Bug Report Description When "dvc.yaml" references a parameter file ... This will remove all cache except items used in the workspace and all ......
Read more >[BUG] CacheInitialization deadlocks and prevents ...
If CacheInitialization is used and Addressable initialization process is started too soon (before Caching.ready == true) the CacheInitOp.
Read more >Advanced topics on caching in Apollo Client
This article describes special cases and considerations when using the Apollo Client cache. Bypassing the cache. Sometimes you shouldn't use the cache for...
Read more >Spring 3.1 Cache Abstraction without parameters
Short answer: Yes, methods without any arguments will get cached just like any other methods. I guess there will be exactly one entry...
Read more >Oracle Waits and Latches Related to Initialization Parameters
Setting Oracle initialization parameters incorrectly can result in performance issues that show up as general waits or latch waits in a ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, my report wasn’t sufficiently verbose.
Calling the
getHandler()
function withcache_options
parameters, such asresults in:
(This was what I meant, by ‘can not perform’ 😃 )
The reason is https://github.com/ipinfo/python/blob/master/ipinfo/handler.py#L42 .
We are setting default values for
maxsize
andttl
(in case they were not defined). However, in case they were defined, we end up sending both named parameters a second time, in**cache_options
Thx much, this is what I call a prompt response and a quick fix! 😃