-
-
Notifications
You must be signed in to change notification settings - Fork 383
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
Does not work well together with tornado #47
Comments
Spent some time on this. viztracer did trigger this behavior, but it's not 100% viztracer's fault. tornado is using some hacky stuff here. The issue is tornado has a local The reason viztracer triggered it is because viztracer kept an unnecessary reference to the whole However, I think it might be reasonable to reconsider the issue now that it breaks stuff. I would probably change viztracer so it will work with tornado. If so, you should be expecting the change soon :) |
@maartenbreddels I fixed the issue and tested it locally. It's released as 0.10.2. You can just If you still have issues with viztracer, please let me know :) |
Yeah, works great! Thanks, and already helpful jupyter/jupyter_client#590 |
Hi,
I wanted to see if this util could help me profile voila (which is using Tornado), but it gives me this:
Is viztracer doing something that could trigger this?
Regards,
Maarten Breddels
The text was updated successfully, but these errors were encountered: