-
Notifications
You must be signed in to change notification settings - Fork 321
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
TypeError: 'NoneType' object is not callable #1289
Comments
Hi @uduse! |
Hey @uduse. Just wanted to check, did you have a chance to try (and possibly reproduce this issue) with |
@alberttorosyan Yeah I can't reproduce this problem with the new version of |
I'm experiencing the same problem again. Though I can't reproduce the same problem in the small demo I shown above, this happens in my complicated project and I don't know what's going on...
|
@uduse let me share a bit of what's going on under the hood here. it might give you some ideas wrt how the more complex scenario might affect things. |
No I don't call those functions explicitly. Could it be a concurrency problem? I'm having multiple |
I ran into this a few days ago with aim
I will update aim (although the changelog does not suggest any changes that might be relevant) and disable resource tracking. |
🐛 Bug
To reproduce
Minimum example:
This problem happens occasionally. In my case it happens one out of four times. However, if I change the script slightly, the problem above never appears.
Notice that I moved the variable
run
into global scope. I think the problem is due to some objects are de-referenced too quickly (e.g., the thread used to track? I'm not sure).Expected behavior
The script should run without problem.
Environment
The text was updated successfully, but these errors were encountered: