Does not work well together with tornado about viztracer HOT 3 CLOSED

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 memoryview to the bytearray, which would be fine on its own. However, if there's another reference to the local variable, then the bytearray (in this case, self._read_buffer_pos) will not be re-sizeable. Personally I don't think this is a safe assumption to make on tornado's side, but I won't bore you with the details if you are not interested.

The reason viztracer triggered it is because viztracer kept an unnecessary reference to the whole code object, where it has reference to the local variables, for every function, for performance concern.

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 :)

from viztracer.

@maartenbreddels I fixed the issue and tested it locally. It's released as 0.10.2. You can just pip install viztracer --upgrade.

If you still have issues with viztracer, please let me know :)

from viztracer.

Yeah, works great! Thanks, and already helpful jupyter/jupyter_client#590

from viztracer.