KeyError async
See original GitHub issueWas doing some late night builds when I noticed that none of my workers ran anymore.
After this version was pushed I started getting errors
AttributeError async
KeyError async
I think it has to do with some missing changes during this commit https://github.com/celery/kombu/commit/75695205f6e7af8e7e9178e010debc3871b19106
Downgrading to 4.1 solved the issue.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:15
- Comments:15 (7 by maintainers)
Top Results From Across the Web
Celery AttributeError: async error - Stack Overflow
We sorted by just updating to celery==4.1.1. it seems the latest release for the 4.1.X sorted out the module name change on kombu....
Read more >Results - Welcome to Python.org
KeyError is an exception that typically relates to a certain operation. Any recovery code would be local to the place where the error...
Read more >Databricks async operator fails to retrieve response['state']
Databricks async operator fails to retrieve response['state'] ... in get_run_state_async state = response["state"] KeyError: 'state' ...
Read more >KeyError — Elixir v1.15.0-dev - HexDocs
%Task{} · async/1 · async/3 · async_stream/3 · async_stream/5 · await/2 · await_many/2 · child_spec/1 · completed/1 · ignore/1 · shutdown/2 · start/1 ......
Read more >Django 4.1 Async: Basic Troubleshooting And Explanations
except (Exception, KeyError) as e: print('Error async iteration: ', e) return render(request, 'demo_template.html').
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
This issue was introduced by #839; however, I think there’s another issue: versioning. Kombu appears to follow semantic versioning, but that is not documented anywhere. If semantic versioning is followed, this backwards-incompatible change should have resulted in a bump to version 5.0.0.
The third issue lies in the fact that Celery’s dependencies have no upper bound: https://github.com/celery/celery/blob/master/setup.cfg#L18-L21. Even if a major version change had gone into effect, our installations would have still been broken. Celery should have an upper bound to prevent problems like this in the future.
Correct, upgrading and builds passing again. Thanks!