#twisted

Tickets pending review: https://tm.tl/#9199, #8159, #9208, #761, #8966 (the0id), #9100, #9101, #9118 (the0id), #4964 (jameshilliard), #9131, #9138, #9143

Hi. In resent days, does anybody had problem in twisted with ssl connections?

my code worked perfectly last few months, but today I got error (Failure instance: Traceback: <class 'OpenSSL.SSL.ZeroReturnError'>)

But code did not changed.

ZeroReturnError just means a clean close of the connection

OpenSSL is weird like that

I don't know why you would suddenly start getting it when you didn't before though

glyph reviewed <https://tm.tl/#9199>; - twisted.web.template support for coroutines (assigned to wsanchez)

glyph reviewed <https://tm.tl/#9208>; - logged traceback when hitting ESC in browser using HTTP2 (unassigned)

Glyph <glyph@twistedmatrix.com>; closed <https://tm.tl/#9208>; - logged traceback when hitting ESC in browser using HTTP2

Tickets pending review: https://tm.tl/#8159, #761, #8966 (the0id), #9100, #9101, #9118 (the0id), #4964 (jameshilliard), #9131, #9138, #9143

new core defect https://tm.tl/#9210 by redapple: TLS handshake failure with OpenSSL 1.1.0f

Tickets pending review: https://tm.tl/#8159, #761, #8966 (the0id), #9100, #9101, #9118 (the0id), #4964 (jameshilliard), #9131, #9138, #9143

Hey all, quick question: when was the command line option "--pidfile" added to the twistd script? Trying to track down which release contained that change.

Tickets pending review: https://tm.tl/#8159, #761, #8966 (the0id), #9100, #9101, #9118 (the0id), #4964 (jameshilliard), #9131, #9138, #9143

can twisted work fine with websockets and paho mqtt lib?

OnceMe: the Autobahn library works with paho mqtt

(with Crossbar)

(oops, will answer further in #autobahn)

new web enhancement https://tm.tl/#9211 by wsanchez: Handle future-yielding coroutines in twisted.web._flatten._flattenElement

new core enhancement https://tm.tl/#9212 by wsanchez: ensureDeferred should complain in a useful way when given a Future-yielding coroutine.

new web enhancement https://tm.tl/#9213 by wsanchez: Narrative documentation for t.w.template needs to provide an example of using a coroutine

wsanchez closed <https://tm.tl/#9199>; - twisted.web.template support for coroutines

_moshez: for no reason at all let's talk about requestFactory

_moshez: let's say that you wanted to, I don't know, upload a very large file to a Klein server

if I want to upload, say, 100MB files to a klein-based server, how much of an idiot I am 1-10? :)

how did I ever guess you were going to ask that

_moshez: so to answer this question we have to have a digression about why http://twistedmatrix.com/trac/ticket/288 isn't fixed yet

glyph: Guido's time machine, we had that discussion :)

ok

right now the behavior of twisted.web when receiving a request is to stick it all into memory until it gets to big, then to spool it away into /tmp

I'm guessing you don't want to do that

glyph: it's...going to be a mime/multipart, right? I haven't done that kind of thing in literally years

okay hang on don't skip to the bad part we're still talking about the good part

glyph: so if it's spooled into a file, then I have to grab my 100MB out of that file and put it into a new file?

glyph: ok.

sorry. go on.

I'm looking at 288. I think I should be able to live without a progress bar

_moshez: so the _first_ problem is that the entire *entity-body* of the upload is going to be buffered before Twisted talks to you. That's relatively easy to fix. The reason #288 can't fix it is that 'getChildWithDefault' implementations are _technically within their rights_ to call .content.read()

luckily

nobody ever _actually_ does that

so you can write your own (ha ha) subclass of Request

and then handle the data of the upload however you want, by overriding requestReceived and handleContentChunk.

ok, so a lower-bound on my idiocy is already 3, right?

_moshez: I don't think it's particularly stupid to implement good stuff :)

_moshez: but we're about to get to where you are regretful, if not necessarily stupid

subclassing request is the bad part :(

_moshez: you could easily do this compositionally if Request weren't such a giant mess; but you really do only have to override 3 methods: allHeadersReceived, handleContentChunk, requestReceived.