[tahoe-lafs-trac-stream] [tahoe-lafs] #1366: avoid calling req.finish() on closed HTTP connections

[tahoe-lafs]

#1366: avoid calling req.finish() on closed HTTP connections
-----------------------------------+----------------------------------------
     Reporter:  warner             |       Owner:  zooko    
         Type:  defect             |      Status:  assigned 
     Priority:  major              |   Milestone:  undecided
    Component:  code-frontend-web  |     Version:  1.8.2    
   Resolution:                     |    Keywords:  reviewed 
Launchpad Bug:                     |  
-----------------------------------+----------------------------------------

Comment (by zooko):

 Replying to [comment:5 davidsarah]:
 > Replying to [comment:3 zooko]:
 > > Could this have been related to #1278 (gateway won't serve any page;
 variety of interesting error messages in twistd.log)?
 >
 > That does look likely given the log message on #1278:
 > {{{
 > exceptions.RuntimeError: Request.finish called on a request after its
 > connection was lost; use Request.notifyFinish to keep track of this.
 > }}}

 If my theory from comment:6 looks sufficiently likely to you then perhaps
 we should close #1278 as "MIA--presumed dead". It wasn't very reproducible
 by me -- perhaps there is an element of race condition between Twisted
 finishing the connection and Tahoe-LAFS finishing it ?

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1366#comment:7>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage