#65 Browsing bug

[Anonymous]

First, I apologize for my strange English, I'm french and
I've not practiced this language since a while...!

Well, this bug concerns Browsing Window (hum not sure
it is really a bug, maybe a bad config somewhere ?):
When I browse some people's file, sometimes I can see
each folder twice, sometimes each file twice, and
sometimes both !
Moreover, it concerns only 1 or 2 persons, and there are
not always the same ! Even other people in my network
have seen this....

I have checked config with my friends as I could, no one
has the same folder twice in "shared folder"... What else
could it be ?

[Nobody/Anonymous]

Logged In: NO

I have noticed someting else that can help you :
Each file in the list has a "speed" column, probably
corresponding to the time the answer has taken to return.

When I see each file twice, the first one has a speed like 580
(for exemple) and the second has a higher speed, like 1250.

Does the problem come from the fact that the answer is
received twice (due to broadcasting) , and then waste
forgots to trash one, as he should ?

ps : I've forgoten to tell you last messages, but Waste rules!
Please go on ;)

[Chris]

Logged In: YES
user_id=573676

That certainly seems like a dual-reply problem. I'm not
sure how that happens since a searchreply is sent as a
routed message, and at each hop should only be emited down
one connection (at least the code LOOKS like it works that
way). I suspect a problem with the broadcast propagation
algorithm.

I can't reproduce this on my small network. Can you confirm
what version you're running? I would guess that if there was
a broadcast bug in an older version than it would only take
one bad client on the mesh to cause duplicate packets like that.

[Nobody/Anonymous]

Logged In: NO

We were first using the 1.5 beta 2 for Windows, now we are
all using the latest nightly builds (11-22-04).

The problem is that we all have the same version (we are
about 5 to 10 users max). So it should work properly... but it
doesn't !

It's really strange and still happens on my network. If you
want to come and see you're welcome, just let a message
and I'll contact you.

[Bob/Paul]

Logged In: YES
user_id=1010948

The only time I've ever seen the dual reply scenerio is when
one of two situations is met:

A) Multiple Folders with the same name on different Partitions
B) Multiple Folders with the same name on different computers.

They're essentially the same. I'll discuss partions below,
but the you can substitue "computers with the same UserID"
for "partition" and the same thing will happen.

Alright. Let's say 2 20GB partitions and 35GB of files to
share on waste. There are two ways to do this:

Method 1:
Spread the files across both partions and share each folder
manually. This will result in a shared structure like this:
C:\C-shared\[chategorized folders]
D:\D-shared\[chategorized folders]

When you browse me on waste you'd see:
BobPaul
|-->C-Shared
| |---> Documents
| |---> Drivers
| |--->[Other Subfoldres]
|-->D-Shared
|---> Drivers
|--->[Subfolders]

Method 2:
Do the same thing, but make sure all of the folder names are
the same. Same named folders will be combined by waste
clients on the recieving end. This would be the following
folder structure:
C:\shared\[chategorized folders]
D:\shared\[chategorized folders]

If you browsed me on WASTE it would look like everything was
on the same partition:
BobPaul
|-->Shared
|--->Documents
|---->Drivers
|---->[Other Subfolders]

Sometimes, the bug described above occurs and you see this:
BobPaul
|-->Shared
|-->Shared
|--->Documents
|---->Drivers
|---->Drivers
|---->[Other Subfolders]

When you get to the actual file listing, though, you'll only
see one appearing.

If the person that you are seeing repeating results from
does not have their computer (or 2 computers with the same
username) setup the way I have laid out in Method 2, then
I'm not sure where the bug is. I've only seen it when the
Method 2 condition is met.

[Nobody/Anonymous]

Logged In: NO

Ok !
First, thanks for your answer, it's very clear.

Unhappily, the bug has disapeared from my network :(
Maybe some persons have re-organized their share...

If it happens again I'll try to check config of "infected" node.
You'll be warned of my conclusions !

Thanks again, and *may the force be with you* guys, you're
right ! ;)

"If it can go wrong, it will !" - Murphy