ugly traceback when sftp server drops connection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
bazaar 1.11 windows version (installed by the installer without tortoise shell).
I had one Fedora server and two clients. Whenever I finished my work on a client, I commit changes and push them to the server. Before I start to work on a client, I pull the changes from the server.
Bazaar crashed when I was pulling changes from the server. The traces and version information are as below.
C:\user\working>bzr pull
Using saved parent location: sftp://
Connected (version 2.0, client OpenSSH_5.1)
SSH user@myserver password:
Authentication (password) successful!
Secsh channel 1 opened.
[chan 1] Opened sftp connection (server version 3)
| [ ] Pull phase 0/2S
ocket exception: Connection reset by peer (10054)
bzr: ERROR: paramiko.
Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\pack.pyo", line 272, in _iter_records
File "bzrlib\pack.pyo", line 277, in _iter_record_
File "bzrlib\pack.pyo", line 218, in reader_func
File "bzrlib\pack.pyo", line 177, in read
File "bzrlib\pack.pyo", line 172, in _next
File "bzrlib\
File "paramiko\
File "paramiko\
File "paramiko\
File "paramiko\
File "paramiko\
SSHException: Server connection dropped:
bzr 1.11 on python 2.5.2 (win32)
arguments: ['bzr', 'pull']
encoding: 'cp936', fsenc: 'mbcs', lang: None
plugins:
bzrtools C:\Program Files\Bazaar\
launchpad C:\Program Files\Bazaar\
netrc_
[unknown]
qbzr C:\Program Files\Bazaar\
svn C:\Program Files\Bazaar\
*** Bazaar has encountered an internal error.
Please report a bug at https:/
including this traceback, and a description of what you
were doing when the error occurred.
C:\user\working>bzr version
Bazaar (bzr) 1.11
Python interpreter: C:\Program Files\Bazaar\
Python standard library: C:\Program Files\Bazaar\
bzrlib: C:\Program Files\Bazaar\
Bazaar configuration: C:\Documents and Settings\
\2.0
Bazaar log file: C:\Documents and Settings\yanlin\My Documents\.bzr.log
Copyright 2005, 2006, 2007, 2008, 2009 Canonical Ltd.
http://
bzr comes with ABSOLUTELY NO WARRANTY. bzr is free software, and
you may use, modify and redistribute it under the terms of the GNU
General Public License version 2 or later.
tags: | added: easy sftp traceback |
summary: |
- bazaar crashed when synchronizing from a Fedora server + ugly traceback when sftp server drops connection |
Changed in bzr: | |
importance: | High → Low |
Changed in bzr: | |
importance: | Low → Medium |
assignee: | nobody → Martin Pool (mbp) |
status: | Confirmed → In Progress |
Changed in bzr: | |
assignee: | Martin Pool (mbp) → nobody |
tags: | added: error-reporting |
tags: | added: check-for-breezy |
bzrlib\ transport\ sftp.py ought to catch the SSHException from fp.readv and turn it into a more appropriate error, possibly a ShortReadvError. The end result ought to be a polite error message for the user saying that the SSH connection was lost, rather than a large, ugly traceback.