0.7 Bug report
 

I had little time tonight, but decided to DL the 0.7 version and I'ts running for 45 min now (win2K JRE 1.4)

Net screen:
no connection problems, the send queued problem seems to be fixed, the only high send queue I saw was with a Bearshare 2.5.0 (GR) client and a Firefly 1.00 client who acted funny (never heard of it before anyway)
There seem to be more Dropped recieved packets than usual.
I like the vendor display !

Search:
Seems to be normal.

Monitor search:
seems to be normal

Swarming downloads:
This screen stay's empty, I mean no download or attempt to download, or even the finished downloads showed up.
I downloaded 2 very common songs by double clicking but they only showed up in the download folder.
1 file finished and the other not, normally I can open the unfinished Mp3 files, but not this last one, so perhaps this proofs the swarming works ?
#edit# ;)
Tried downloading by clicking multisource download, and this does the trick !
Everything was displayed now Never saw a mp3 finish so quik !
Only noticed a click in it when listened to it.

Share :
Seems to be normal, but I noticed more uploads than usual

i'm looking forward to 0.7.1 !

O.K. here's a few more
The most annoying bug is when a part of a file is assigned to a host, and the connection (push) to that host fails,or the host stays busy, no search for another candidate is done, so even if you have all other parts, the file is useless.

The interaction with gnucleus 1600 (morpheus) clients is bad ( I have seen this also in the earlier versions) a lot of uploads fail and still they keep on reqesting the same file.
Sometimes downloads are red but keep on reading 0Kbs even after stopping and restarting.
So who is to blame here, morpheus or phex ?

You mean you have one segment left and only one candidate? The search dosn't care how many segments there are left. But it will raise the time between search if you have many candidates available. Maybe the problem is you have more then one candidate but the segment stays assigned to this one busy candidate? Could this be?

I'm not sure but think Gnucleus/Morpheus has little different multi source downloading behaivor. It is downloading very small pieces and then disconnects, reconnects and downloads the next small piece. Thats my only explenation for this. Phex uses much bigger pieces to download. Well both concepts have there pros and cons.
The 0Kbs files could to be a Phex problem with not recognizing the timeout.

Yes this is the problem, And also when the push fails for this candidate, Phex will keep this candidate assigned.


Another bug is in the GUI of the Swarming downloads screen at startup.
All I see is a screen full of little dots with (the ones you normally have inbetween the download files and download candidates / segments, used for resizing the 2 parts of the screen).
After resizing the whole Phex screen I than can drag the top half of the screen down to see the download files part.