TooManyConcurrentRequests error from abort_write_group hides underlying error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Andrew Bennetts |
Bug Description
I think my http connection closed, and I got this traceback. I think it's quite unlikely that abort_write_group can succeed over an ssh connection as it's highly likely the connection is already in use.
Some things we could do here:
* like for unlock, have abort_write_group transform errors into warnings if something goes wrong; this is hiding information from the caller but the worst that should happen is that there will be accumulated garbage. (actually we would have to be careful as to which errors are caught this way.)
* from the except block, log the exception that caused the write group to be aborted; or pass it in to the abort_write_group method so it can be printed later
* have the ssh transport not fail if it's already in use but instead open another connection - this won't totally fix the problem if eg the link is down and it's not possible to open a new connection
Traceback (most recent call last):
File "/usr/lib/
return run_bzr(argv)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
use_
File "/usr/lib/
revision_
File "/usr/lib/
result_
File "/usr/lib/
find_
File "/usr/lib/
result = unbound(self, *args, **kwargs)
File "/usr/lib/
pb, find_ghosts)
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
resp = self._call2(
File "/usr/lib/
return self._client.
File "/usr/lib/
result, protocol = self.call_
File "/usr/lib/
method, args, expect_
File "/usr/lib/
readv_
File "/usr/lib/
protocol_
File "/usr/lib/
request = self._medium.
File "/usr/lib/
return SmartClientStre
File "/usr/lib/
raise errors.
TooManyConcurre
Related branches
Changed in bzr: | |
assignee: | nobody → spiv |
importance: | Undecided → Medium |
status: | New → Confirmed |
Possibly related to bugs 243391, 246233, 273177 and 230902 (the last one is less likely, but bug 273177 seems to indicate they might be dupes).