On Aug 4, 2019, at 9:04 PM, Waqar Khan <wk80333@gmail.com> wrote:
Ah yes.. That is true..
If I comment out request.finish() (Here is the doc which I tried to followed: https://twistedmatrix.com/documents/13.0.0/web/howto/web-in-60/interrupted.h... <https://twistedmatrix.com/documents/13.0.0/web/howto/web-in-60/interrupted.h...>) Then actually.. when I try to test out the code... (via curl or like doing requests.get .. to the URI).. it is just stuck..
Yep! This makes sense; if you don't call `.finish()` at all then your code will never tell the client that it's done. But if you call `.finish()` after notifyFinish() has fired then you get that error. If you change your code to only call `.finish()` if the deferred returned by notifyFinish() has not fired or failed yet, do you get the error? It's possible that you still do, in which case, there's a bug in Twisted that needs to be fixed.
I do want to convey my thanks for the help. Really appreciate it.
Thanks for using Twisted :) -g