TooManyConcurrentRequests when committing and the smart server is offline
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned |
Bug Description
When committing against a bzr checked out branch against a smart server that is offline, the following error is displayed:
bzr: ERROR: bzrlib.
edium.SmartTCPC
uest limit. Be sure to finish_writing and finish_reading on the currently open r
equest.
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\
File "bzrlib\
File "bzrlib\
TooManyConcurre
object at 0x0181E5D0>' has reached its concurrent request limit. Be sure to fin
ish_writing and finish_reading on the currently open request.
bzr 1.11 on python 2.5.2 (win32)
arguments: ['bzr', 'commit', '-m', 'Refactored out the creation of a dot in draw
-maps and overlap']
encoding: 'cp1252', 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.
The server is:
Bazaar (bzr) 1.9
Python interpreter: C:\Program Files\Bazaar\
Python standard library: C:\Program Files\Bazaar\
bzrlib: C:\Program Files\Bazaar\
Bazaar configuration: C:\Users\
Bazaar log file: C:\Users\
Copyright 2005, 2006, 2007, 2008 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.
I am reporting this because it seems that the issue was that the server was unavailable, as once I started it the commit worked fine.
However, at first glance, it would seems as though it was a bug.
Ack, this is confusing. Bumping to high because we really need to get these stomped out.