Comment 2 for bug 625365

  Le 27/08/2010 17:34, Alexander Belchenko a écrit :
> Alexandre Garnier пишет:
>> Public bug reported:
>>
>> $ bzr init-repo repo
>> $ mkdir repo/stuff
>> $ mkdir repo/real-work
>>
>> When opening repo/real-work, bzr-explorer walk through repo/stuff.
> How can you know this?

First it was because I got an encoding error from nowhere :
File
"/users/garniera/system/boulard/lib/python/bzrlib/transport/local.py",
line 163, in get
     return osutils.open_file(path, 'rb')
UnicodeEncodeError: 'ascii' codec can't encode character u'\xc9' in
position 30: ordinal not in range(128)

So I modify to log 'path' to find where it was failing and I got logs of
all subfolders of repo.

Then when trying to reproduce in an other sandbox place (and environment
to avoid encoding problem from Xming connection), opening repo/real-work
opens repo.

>> If this folder is big and/or deep (or is linked to a system folder in my case) the opening can be very long even if I don't care about other folders in the repo...
>>
>> Seems to be something between bzrdir and transport.
> Is there something suspicious in .bzr.log

Nothing, just logs about launching bzr explorer.

>> Walking up the directory tree seems normal, but why walking down through
>> siblings ?
> Can you check that repo/stuff is not listed as parent or submit location
> for repo/real-work (see the output of bzr info).
>
> I agree Explorer should not scan all branches in the shared repo if
> you're opening only one branch. But I need more info on what's going on
> and how you can see it.

In fact, repo/real-work is not a branch, just a folder containing
branches. And there is no connection between repo/real-work (or
sub-branches) and repo/stuff.
When opening repo/real-work/my_branch (a real branch), no problem.

I'll try to create better use-case with logs and everything at home tonight.

--
Alex