Bazaar Explorer crash on qconfig when using checkouts via bzr+ssh
martitzam at gmail.com
Sun Sep 26 17:32:49 BST 2010
On Sun, Sep 26, 2010 at 9:25 AM, Maritza Mendez <martitzam at gmail.com> wrote:
> If this bug has been reported, I failed to find it on Launchpad. There
> have been numerous "TooManyConcurrentRequests" bugs filed, but most/all of
> them seem to be related to legitimate attempts to open an ssh connection. I
> have found a case in which there seems to be no legitimate reason to involve
> Before posting this to the list, I have taken a step back from the edge and
> am using only the stable ppa (http://ppa.launchpad.net/bzr/ppa/ubuntu) to
> get my bzr components for Linux. As a result, I'm running bzr 2.2.0 (via
> 2.2.0-1~bazaar4~lucid1) but still on qbzr 0.19.0 (via
> 0.19-1~bazaar1~lucid1). I do not know if what I am about to describe is
> already resolved in releases not yet in the stable ppa.
> I also have bzr (also 2.2) installed on a remote machine we'll call
> server.net. On that machine, a user 'user' owns some branches and also
> has a copy of my ssh public key. So on my local working machine I do
> something like
> 'bzr checkout bzr+ssh//user at server.net/home/user/test/trunk<localpath>/test'
> to get a checkout. That works fine, of course.
> Now, if on the local machine I open this checkout with Bazaar Explorer,
> most things work fine.
> But if I select Settings > Configuration > User Configuration, Bazaar
> Explorer crashes when the dialog is closed with
> bzr: ERROR: bzrlib.errors.TooManyConcurrentRequests: The medium
> 'SmartSSHClientMedium(bzr+ssh://email@example.com/)' has reached its
> concurrent request limit. Be sure to finish_writing and finish_reading on
> the currently open request.
> If I open the same settings dialog either from the Welcome page or from a
> page associated with a real branch (not a checkout) then everything is ok.
> So it *appears* that either qconfig or explorer is triggering an
> illegitimate ssh connection request when the active GUI page is a checkout
> via bzr+ssh.
> I am attaching a traceback which pops in a dialog but does *not* get
> written to .bzr.log.
FYI, it does not matter if the checkout was set up exactly as above or if I
use authentication.conf to minimize typing. As it turns out, I usually need
to include the username in the transport scheme anyway because I use several
different "shared" accounts on the server to grant access to different
groups of branches. It's a simple but effective way of controlling access
to "restrcited" repositories.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bazaar