Ok! Instead of my usual "huge" test branch, I've been working with a tiny
branch with only three files. So...
Sure enough, bound branches do not exhibit the Too ManyConcurrentRequests
bug.
So far, only checkouts are showing the TooManyConcurrentRequests bug.
To be clear: the bug occurs on Windows XP using bzr+ssh with bzr 2.2.0 and
bzr-explorer 1.1b1 for lightweight checkouts only.
I have not seen the bug on ubuntu (I have looked) but I am still running bzr
2.1.x on my lucid boxes.
~M
On Mon, Aug 23, 2010 at 11:48 AM, Alexander Belchenko <email address hidden>wrote:
> Martitza пишет:
> > Yes. I am experimenting with lightweight cbeckouts. (Turns out they
> > mighT be ok fpr us if we organize our repos a little differently.). I
> > will try your suggestion today.
>
> Another suggestion: use heavyweight checkouts, aka bound branches
> instead of light branches, if you have enough room on your disk to
> hold all your history.
>
> --
> TooManyConcurrentRequests when saving from editor spawned by bzr-explorer
> https://bugs.launchpad.net/bugs/622474
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Explorer: New
> Status in Qt frontend for Bazaar: New
>
> Bug description:
>
> 1. Launch Bazaar Explorer
> 2. Open an existing working tree (mine is a checkout, but branches might
> show the same problem)
> 3. Select a text file in the working tree browser.
> 4. Click the icon (under the WT) to Edit the file. ==> Notepad opens on
> Windows
> 5. Change some text to mark file as dirty in Notepad.
> 6. Press Ctrl-S to save ==> get the attached traceback
>
> 7. Ignore the error.
> 8. Notice that subsequent saves work without error.
> 9. Close and reopen the text file.
> 10. Notice that subsequent edit+save works without error but that saving is
> noticeable slow (hourglass appears for ~1 second)
> 11. Commit change.
> 12. Go back to steps 3..6. Notice that the error reoccurs.
>
> Note that this trace appears in a dialog box but does *not* appear in the
> .bzr.log.
> It looks like it may actually be local to bzr explorer...
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/bzr-explorer/+bug/622474/+subscribe
>
Ok! Instead of my usual "huge" test branch, I've been working with a tiny
branch with only three files. So...
Sure enough, bound branches do not exhibit the Too ManyConcurrentR equests
bug.
So far, only checkouts are showing the TooManyConcurre ntRequests bug.
To be clear: the bug occurs on Windows XP using bzr+ssh with bzr 2.2.0 and
bzr-explorer 1.1b1 for lightweight checkouts only.
I have not seen the bug on ubuntu (I have looked) but I am still running bzr
2.1.x on my lucid boxes.
~M
On Mon, Aug 23, 2010 at 11:48 AM, Alexander Belchenko <email address hidden>wrote:
> Martitza пишет: ntRequests when saving from editor spawned by bzr-explorer /bugs.launchpad .net/bugs/ 622474 /bugs.launchpad .net/bzr- explorer/ +bug/622474/ +subscribe
> > Yes. I am experimenting with lightweight cbeckouts. (Turns out they
> > mighT be ok fpr us if we organize our repos a little differently.). I
> > will try your suggestion today.
>
> Another suggestion: use heavyweight checkouts, aka bound branches
> instead of light branches, if you have enough room on your disk to
> hold all your history.
>
> --
> TooManyConcurre
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Explorer: New
> Status in Qt frontend for Bazaar: New
>
> Bug description:
>
> 1. Launch Bazaar Explorer
> 2. Open an existing working tree (mine is a checkout, but branches might
> show the same problem)
> 3. Select a text file in the working tree browser.
> 4. Click the icon (under the WT) to Edit the file. ==> Notepad opens on
> Windows
> 5. Change some text to mark file as dirty in Notepad.
> 6. Press Ctrl-S to save ==> get the attached traceback
>
> 7. Ignore the error.
> 8. Notice that subsequent saves work without error.
> 9. Close and reopen the text file.
> 10. Notice that subsequent edit+save works without error but that saving is
> noticeable slow (hourglass appears for ~1 second)
> 11. Commit change.
> 12. Go back to steps 3..6. Notice that the error reoccurs.
>
> Note that this trace appears in a dialog box but does *not* appear in the
> .bzr.log.
> It looks like it may actually be local to bzr explorer...
>
> To unsubscribe from this bug, go to:
> https:/
>