Bazaar Explorer crash on qconfig when using checkouts via bzr+ssh

Vincent Ladeuil v.ladeuil+lp at free.fr
Sun Sep 26 19:56:02 BST 2010


>>>>> Maritza Mendez <martitzam at gmail.com> writes:

    > 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.

Very nice bug report, please, don't hesitate to file it on
launchpad. Anyway, failing to find a duplicate is not a deadly sin ;)

At worst, the community or the devs may finally realize it's a dupe but
could point to it if the report is clearer or better explain the
problem.

    >> 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 ssh.

Even if the reason is not legitimate, it's still possible that we
shouldn't tracebak and create a new connection (I'm pretty sure we have
related and valid use cases that we fail to handle (and we raise
TooManyConcurrentRequests), http:/pad.lv/483661 for example. There is
also one use case I thought I reported but couldn't find anymore :-/

<snip/>

    >> 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.

In fact, that's the opposite that is surprising: that we manage to resue
the same connection instead of creating a new "illegitimate" one. Trying
to use the same connection is "illegitimate", hence the exception. But
*why* we are doing this, is unclear.

<snip/>

    > 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.

This sounds interesting, would you mind share your setup (if only in
describing it a bit more) and tell us what is missing in the crontrib/
directory or if you used or modified something here ?

          Vincent



More information about the bazaar mailing list