[bug] RepoFetcher run between the same location
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Invalid
|
Low
|
Unassigned |
Bug Description
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I just did this:
cd bzr.dev
bzr up
And in another terminal I did
bzr branch bzr.dev test-branch
And I got:
bzr: ERROR: RepoFetcher run between two objects at the same location:
KnitRepository(
KnitRepository(
What happened was the second command waited for the first to finish
(because it wanted to grab a write-lock on a repository). And somewhere
in all of that timing, it didn't realize that they were the same repository.
I don't know how it got the idea that they were different repositories,
or that it didn't have the revision it cared about. (It seems like it
locked for read, and didn't find the revision, so it tried to push it
later.)
John
=:->
affects bzr
status triaged
importance low
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFHC8RMJde
9gEePTc5vXnKDde
=Lvb+
-----END PGP SIGNATURE-----
On Tue, 2007-10-09 at 18:11 +0000, John A Meinel wrote: 'file:/ //home/ jameinel/ dev/bzr/ .bzr/') and 'file:/ //home/ jameinel/ dev/bzr/ .bzr/')
> Public bug reported:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I just did this:
>
> cd bzr.dev
> bzr up
>
> And in another terminal I did
>
> bzr branch bzr.dev test-branch
>
> And I got:
> bzr: ERROR: RepoFetcher run between two objects at the same location:
> KnitRepository(
> KnitRepository(
>
> What happened was the second command waited for the first to finish
> (because it wanted to grab a write-lock on a repository). And somewhere
> in all of that timing, it didn't realize that they were the same repository.
>
> I don't know how it got the idea that they were different repositories,
> or that it didn't have the revision it cared about. (It seems like it
> locked for read, and didn't find the revision, so it tried to push it
> later.)
This assert is meant to only be triggered if someone failed to check for
has_same_location in Repository.fetch, or is incorrectly using the
RepoFetcher api directly.
Did you get a backtrace?
-Rob www.robertcolli ns.net/ keys.txt>.
--
GPG key available at: <http://