Shareaza

I've noticed today that my Host Cache is showing me dates that lie more than 90 years in the future for some hosts within the G2 Hub list. Might be worth an investigation, as this is most probably causing those Hosts never to be removed automatically from the cache...

Take off every 'zig'.

Maybe they're trying to send us a back-time warning from the sole surviving 'zig' that we'll have no chance to survive make our time if the present course of history is not altered?

Same problem here. Help chanel told me i should wait the next release:

[14:35] <Anon4296> so, im having the problem with the G2 cache
[14:35] <Anon4296> all those adress are with a strange date (2110) for example
[14:36] <Anon4296> so sahreaza trys to conect to those hubs but it cant since the dates are wrong/bugged
[14:36] <Anon4296> bug described here: viewtopic.php?f=7&t=1069
[14:37] <SkinVista> That known issue was patched an hour ago: http://shareaza.svn.sourceforge.net/vie ... ision=8945
[14:38] <Anon4296> saw the link. how to implement it?
[14:39] <RoestVrijStaal> ...just wait till the next release?
[14:39] <SkinVista> Try a debug build tomorrow.

I cant connect to G2 with that problem, Only manually when i quickly remove those future host and conect to the last valid host seen. very annoying.

I do protest against this "fix"! It does not solve the issue, it only cures the symptoms. (So, the problem that makes the host be located in the future still exists, we only add a workaround to correct the wrong dates at a later time once they are noticed.)

Shareaza fixes seen-time before new host added to host cache. BTW this correction already was in Shareaza code but not on all code paths.

But where do these false times come from in the first place?

I dont wanna be an ass, but can we see a solution for that in a new future?

r8945 contains a fix for it, so you can use that debug build temporarily. However, that fix is not ideal, so a better solution might be coded soon.

Thank you very much ! im using it right now and the prob is gone.
obs:
can this debug version update itself when it comes to the time? (when 2.5.5 comes out fo example).

Sorry, but no, it can't.

thanx anyway. I wil check from time to time for the next release then...

This bug is making a lot of people to move from shareaza to another p2p programs since G2 is the main source. Around the web I see a lot of ppl asking me what is this error and complaining about this (at least here , in my contry) .. I hope the next public release is set to go asap!