Alt.Binz forum

New Alt.Binz versions => Bugs => Fixed bugs => Topic started by: kC_ on May 17, 2010, 11:02:03 pm

Title: Binsearch: '4267 [' is not an integer value
Post by: kC_ on May 17, 2010, 11:02:03 pm

using binsearch tab, whenever i search for "pacific" or "the pacific"
the search freezes and up pops '4267 ]' is not an integer value

i press ok, then it pops up again, i then need to force close alt binz, and can repeat the error each time.

0.31.5

Title: Re: '4267 ]' is not an integer value
Post by: Hecks on May 17, 2010, 11:07:36 pm

This seems to be a result of Binsearch adding (somehow) new strings to the collection identifier to flag passworded files, e.g:

Quote

collection  size: 1.57 GB, parts available: 4267 / 4267 [requires password]

Title: Re: '4267 ]' is not an integer value
Post by: kC_ on May 17, 2010, 11:11:49 pm

and if i tick "only collections"

get a  '1608 ]' is not an integer value


cheers

Title: Re: Binsearch: '4267 [' is not an integer value
Post by: zoned on May 20, 2010, 07:43:20 am

Ah at least they are trying to rid those passworded files.

Am i' alone seeing for a while NZBindex has a lot more search results than Binsearch. This isn't anything to do with passworded files.

On some new files Binsearch, for few weeks show larger file size than should be. Using NZBindex varifies this, haven't tried to get files that say are bigger from Binsearch as yet. Can see same file on both and select the correct size one on NZBindex and all is ok no password etc. Maybe this file size thing is a sysmtom of trying to rid the passsworded files ?

Would be nice if they could rid all the larger gb files that are passworded. Unknown if leave to cook while away, to find of no use when get back. Will have to download the first 50mb of each first part and check in future as with other likely passworded files. :)

Title: Re: Binsearch: '4267 [' is not an integer value
Post by: Hecks on May 20, 2010, 11:03:26 am

Yes, Binsearch autogrouping has had quite a lot of trouble with those passworded dupes, often combining them with the legit ones.  Unless you're manually selecting from the Fetch Collection Info list I would avoid Binsearch where you know there is likely to be passworded probs.  NZBIndex has handled this much better, although still not perfectly.

Title: Re: Binsearch: '4267 [' is not an integer value
Post by: frantic ab on May 20, 2010, 12:02:11 pm

Hmmm... seems that I am not the only one having this problem.

Title: Re: Binsearch: '4267 [' is not an integer value
Post by: Rdl on May 20, 2010, 01:31:11 pm

I'm working on it.

Title: Re: Binsearch: '4267 [' is not an integer value
Post by: frantic ab on May 27, 2010, 06:17:02 pm

Great...  ;D


For now restarting Altbinz is the only option to temporarily get rid off it.

Title: Re: Binsearch: '4267 [' is not an integer value
Post by: bb-q on May 28, 2010, 04:08:32 am

this bug is becoming very annoying, can barely search anything without having to close and reopen altbinz.

Title: Re: Binsearch: '4267 [' is not an integer value
Post by: Hecks on May 28, 2010, 09:48:12 am

Quote from: bb-q on May 28, 2010, 04:08:32 am

this bug is becoming very annoying, can barely search anything without having to close and reopen altbinz.

Then obviously the thing to do is: stop using Binsearch until a fix is out.  See NZBIndex and Newzleech.

Title: Re: Binsearch: '4267 [' is not an integer value
Post by: Rdl on May 28, 2010, 03:16:51 pm

Fixed.
'Unknown' is now displayed under files column for collections that don't have filecount.
'(*) ' is displayed in front of the subject if binsearch has marked collection as password protected