ErrorFromSmartServer should not cause a traceback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Andrew Bennetts |
Bug Description
Bug 263506 mentions a case where a bzr server has a bug causing it to send an unexpected error response to the client. The client currently gives a traceback in this case, e.g.:
"""
$ bzr commit -m 'selftest --starting-with now accepts multiple values'
Committing to: bzr+ssh:
modified NEWS
modified bzrlib/builtins.py
modified bzrlib/
modified bzrlib/
modified bzrlib/
Committed revision 3669.
bzr: ERROR: bzrlib.
Traceback (most recent call last):
File "/v/home/
return run_bzr(argv)
File "/v/home/
ret = run(*run_argv)
File "/v/home/
return self.run(
File "/Volumes/
exclude=
File "/v/home/
result = unbound(self, *args, **kwargs)
File "/v/home/
result = WorkingTree3.
File "/v/home/
result = unbound(self, *args, **kwargs)
File "/v/home/
revprops=
File "/v/home/
self._cleanup()
File "/v/home/
raise e
ErrorFromSmartS
bzr 1.7dev on python 2.5.2 (linux2)
...
"""
It's correct that ErrorFromSmartS
That is, the right output in that example would be just:
"""
$ bzr commit -m 'selftest --starting-with now accepts multiple values'
Committing to: bzr+ssh:
modified NEWS
modified bzrlib/builtins.py
modified bzrlib/
modified bzrlib/
modified bzrlib/
Committed revision 3669.
bzr: ERROR: bzrlib.
"""
This should be easy; I'll do this for 1.7.