[tahoe-lafs-trac-stream] [tahoe-lafs] #1664: webapi fails to handle all TCP disconnects: "Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this."

[tahoe-lafs]

#1664: webapi fails to handle all TCP disconnects: "Request.finish called on a
request after its connection was lost; use Request.notifyFinish to keep
track of this."
-----------------------------+---------------------------------------------
     Reporter:  nejucomo     |      Owner:  nobody
         Type:  defect       |     Status:  new
     Priority:  major        |  Milestone:  1.11.0
    Component:  code-        |    Version:  1.9.0
  frontend-web               |   Keywords:  webapi error disconnect twisted
   Resolution:               |
Launchpad Bug:               |
-----------------------------+---------------------------------------------

Comment (by nejucomo):

 I am somewhat confident this behavior is benign; the web server will
 continue processing other requests without being affected.  For this
 reason I'd lower the priority.

 There's only two possible drawbacks I now brainstorm:

 * The exception may scare users.
 * The process generating the response may be wasting resources; especially
 if this is a very long-running request which consumes many resources.

 There *could* be a bug if a failure for the client to receive a request
 result leads to corruption.  I doubt that is the case, at least for the
 RESTful storage APIs.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1664#comment:5>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage