[tahoe-dev] [tahoe-lafs] #653: introducer client: connection count is wrong, !VersionedRemoteReference needs EQ

[tahoe-lafs]

#653: introducer client: connection count is wrong, !VersionedRemoteReference
needs EQ
--------------------------+-------------------------------------------------
 Reporter:  warner        |           Owner:  warner  
     Type:  defect        |          Status:  assigned
 Priority:  major         |       Milestone:  1.6.0   
Component:  code-network  |         Version:  1.3.0   
 Keywords:                |   Launchpad_bug:          
--------------------------+-------------------------------------------------
Changes (by zooko):

  * milestone:  1.5.0 => 1.6.0


Comment:

 I spoke with Brian on IRC this morning before his gallivanting schedule,
 and he said that it was unlikely that this problem will recur with the
 current versions of foolscap and of TahoeLAFS.  I agree and am going to
 bump this ticket out of the v1.5 Milestone.

 Note that we can't actually close this ticket yet because there isn't a
 test for the original issue: duplicate entries in
 {{{IntroducerClient._connections}}} because ~RemoteReferences don't
 compare equal when they denote the same underlying TCP connection to the
 same peer, much less the newly discussed issue: duplicate
 ~RemoteReferences because (somehow) the peer is setting up new
 ~RemoteReferences while {{{notifyOnDisconnect()}}} is not getting called
 for the old ones.

 However, I'm fairly confident that this is (a) not a regression versus
 TahoeLAFS v1.4.1, and (b) not a critical bug.  (In fact, it might actually
 be already fixed in current trunk.)

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/653#comment:14>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid