-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: unbound error on base middleware handler #1379
Labels
bug
Something isn't working
Comments
Looks so, but we already have |
Lancetnik
added a commit
that referenced
this issue
Apr 18, 2024
Btw, can I wait for your PR with 0.5.0 compatibility in taskiq-faststream @chrisgoddard ? |
Wait? Not sure I follow. I haven't seen any activity on my PR. I'll bump the version to 0.5.2 when I'm back at my computer this evening. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm currently using the TaskIQ scheduler integration (see my fork here - I've made the changes for 0.5x compatibility).
When I'm running the app using
taskiq scheduler module:app
- when I cancel the process, I get this:Unrelated to the implementation, I'm wondering if on broker/middlwares/base.py:consume_scope, we should add = None so we don't get the scope error?
The text was updated successfully, but these errors were encountered: