← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to bzrlib/errors.py

  • Committer: John Arbash Meinel
  • Date: 2011-09-14 12:58:17 UTC
  • mto: (6133.4.49 2.5-soft-hangup-795025)
  • mto: This revision was merged to the branch mainline in revision 6170.
  • Revision ID: john@arbash-meinel.com-20110914125817-h9csfegz6bvz93yj
It turns out that if we don't explicitly close the socket, it hangs around somewhere.

Which means that the client doesn't *know* that it has been disconnected.

Show diffs side-by-side

added added

removed removed

Lines of Context:
bzrlib/errors.py
1710
1710
    _fmt = "Connection closed: %(msg)s %(orig_error)s"
1711
1711
 
1712
1712
 
 
1713
class ConnectionTimeout(ConnectionError):
 
1714
 
 
1715
    _fmt = "Connection Timeout: %(msg)s %(orig_error)s"
 
1716
 
 
1717
 
1713
1718
class InvalidRange(TransportError):
1714
1719
 
1715
1720
    _fmt = "Invalid range access in %(path)s at %(offset)s: %(msg)s"