Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error: type object 'Retry' has no attribute 'DEFAULT_ALLOWED_METHODS'
See original GitHub issueThis happens on 1.5.0, and started today. The relevant code is pretty simple and shouldn’t be problematic, in theory:
fcm = pyfcm.FCMNotification(api_key=conf["google"]["fcm"]["key"])
Downgrading to 1.4.9 or 1.4.7 solves the problem
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
'Retry' object has no attribute 'allowed_methods' #196 - GitHub
Hello, I've just tried to migrate to the last version 0.25.0, but when creating a KeycloakOpenId object: keycloak_openid ...
Read more >AttributeError: 'Retry' object has no attribute 'method_whitelist'
I don't know your specific case since there is not much info. Nevertheless, I had the same error while using the requests package...
Read more >Utilities - urllib3 1.26.13 documentation
Each retry attempt will create a new Retry object with updated values, ... Other errors are errors that are not connect, read, redirect...
Read more >Developers - AttributeError: type object 'Retry' has no attribute ...
AttributeError : type object 'Retry' has no attribute 'DEFAULT_ALLOWED_METHODS'
Read more >Kong Gateway Changelog | Kong Docs
Fixed an issue when passing a license from the control plane to the data plane using the Admin API /licenses endpoint. In hybrid...
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 Free
Top 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
@olucurious I saw the proposed fix and I tried manually upgrading urllib3 to 1.26.0+, and that solved the problem. As far as I was able to test (can’t test the whole implementation since my setup relies on pypi) things are looking good.
It looks like the same thing is happening once again on 1.5.2 (reverting to 1.5.1 solved the problem)