invoke_get_quote fails on tornado 6.0
See original GitHub issueThe 'callback` function has been deprecated in 6.0 release:
https://www.tornadoweb.org/en/stable/releases/v6.0.0.html
This results in the following code breaking:
and possibly…
Using config file /etc/keylime.conf
2019-10-17 12:09:44.918 - keylime.cloudverifier - INFO - Starting Cloud Verifier (tornado) on port 8881, use <Ctrl-C> to stop
2019-10-17 12:09:44.919 - keylime.cloudverifier_common - INFO - Setting up TLS...
2019-10-17 12:09:44.920 - keylime.cloudverifier_common - INFO - Existing CA certificate found in /var/lib/keylime/cv_ca, not generating a new one
2019-10-17 12:09:44.922 - keylime.cloudverifier - INFO - Starting service for revocation notifications on port 8992
2019-10-17 12:10:33.188 - keylime.cloudverifier - ERROR - Polling thread error: __init__() got an unexpected keyword argument 'callback'
2019-10-17 12:10:33.189 - keylime.cloudverifier - ERROR - __init__() got an unexpected keyword argument 'callback'
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/keylime-1.2-py3.7.egg/keylime/cloud_verifier_tornado.py", line 406, in process_agent
self.invoke_get_quote(agent, True)
File "/usr/local/lib/python3.7/site-packages/keylime-1.2-py3.7.egg/keylime/cloud_verifier_tornado.py", line 307, in invoke_get_quote
client.fetch(url, callback=cb)
File "/usr/local/lib64/python3.7/site-packages/tornado/httpclient.py", line 284, in fetch
request = HTTPRequest(url=request, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'callback'
2019-10-17 12:10:33.192 - keylime.cloudverifier - INFO - POST returning 200 response for adding agent id: D432FBB3-D2F1-4A97-9EF7-75BD81C00000
2019-10-17 12:10:33.486 - keylime.cloudverifier - INFO - PUT returning 404 response. agent id: D432FBB3-D2F1-4A97-9EF7-75BD81C00000 not found.
I guess we will need to replace this with async code.
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (14 by maintainers)
Top Results From Across the Web
tornado 6.0 breaks notebook · Issue #4439 - GitHub
tornado 6.0 is released at 10AM ET, March 1, 2019, which breaks Jupyter Notebook. https://pypi.org/project/tornado/6.0/#history. Error message.
Read more >What's new in Tornado 6.0
If a server returns a 3xx response code without a Location header, the response is raised or returned directly instead of trying and...
Read more >Python Tornado not implemented error workaround
It might help if you execute this before getting and starting of your IOLoop asyncio.set_event_loop_policy(asyncio.
Read more >OSHA opens investigation after Amazon warehouse collapses ...
OSHA opens investigation after Amazon warehouse collapses during tornado, killing 6. Economy Dec 13, 2021 6:00 PM EST.
Read more >Summary of May 6, 1965 Twin Cities Tornadoes
May 6, 1965 was one of the worst tornado outbreaks in Minnesota history. Six tornadoes affected six counties around the Twin Cities with...
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
Hi @lukehinds
I haven’t found a way to do this without using the nest-asyncio PIP package. It sounds like python and tornado developers are trying to prevent developers from doing recursive event loops, which we need here.
If you’re willing to use (and install) the
nest-asyncio
pip package, then here is a patch tocloud_verifier_tornado.py
that works on my end.What do you think?
🎉 This issue has been resolved in version 4.0.1 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀