Ben Darnell

There's not much to go on here - looks like the browser/client has closed the connection. This is more likely to be a jupyterlab-specific issue than something in Tornado.

Thanks!

I think that patch may be obsolete. We now have an `except` clause in `bind_unix_socket` to catch an error that is said to occur on hurd: https://github.com/tornadoweb/tornado/blob/559f94aa8809fa37cb2015fadc06d8e46430fafe/tornado/netutil.py#L205-L210

Per https://developers.facebook.com/docs/graph-api/guides/field-expansion, there are a few different formats this can take: - "Limiters" such as `.limit(x)`, `.width(x)`, `.height(x)`. - Nested requests using curly-brace syntax such as `posts.limit(5){message}` (with or without...

My initial reaction is that this doesn't seem like something I'd like to include in Tornado, because it's such an uncommon desire (I've never seen anyone try to mask timing...

I'm going to close this since it sounds like things have been improved on the jupyter side (although jupyter/notebook#6721 is still open?) It sounds like the fix is now to...

Hmm, I can't think of anything in Tornado that would close a connection every 10 minutes (which suggests to me the possibility of proxy or NAT issues). What did the...

What's closing the handler? Do you mean that the client is half-closing its side of the connection and waiting to receive the rest of the data (that's possible with http,...

The assertIsNone and assertIsNotNone changes are good and I'd be happy to see those methods adopted wherever applicable. (The same is true in most cases for all of the new...

The 125-byte limit only applies to control frames, which means pings and close messages. Regular messages (both text and binary) sent with `write_message` have the limit from `max_message_size`.