-
Notifications
You must be signed in to change notification settings - Fork 47
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
Debugging+Logging: find out when sync function run in asynq context #28
Comments
JelleZijlstra
added a commit
to JelleZijlstra/asynq
that referenced
this issue
Apr 15, 2017
Merged
manannayak
pushed a commit
that referenced
this issue
Apr 18, 2017
Is Manan's addition in #31 sufficient for your use case? |
How can this be turned on? |
if you set |
I'm guessing like this? If so, this is great, thank you! from asynq.debug import options
options.DUMP_SYNC_CALLS = True |
Yep |
We should really document that options mechanism. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we migrate our code to use asynq, we would love a way to detect usages of sync calls within asynq contexts.
For example, imagine:
This will incur a sync fetch within an already asynq call which should be fixed since it incurs performance penalties especially when
data_fetch_2
is batched.I have not seen a way to log/debug/add a hook to figure out when this happens
The text was updated successfully, but these errors were encountered: