AniDB

Hi there,

I have about 6000 files in my mylist and at the moment the client updates for hours on end going

[12.06.2004 06:36:20] - Trying to connect to AniDB...
[12.06.2004 06:36:21] - Connected to AniDB.
[12.06.2004 06:36:21] - Executing new AniDB command.
[12.06.2004 06:36:21] - New or updated mylist entry, updating....
[12.06.2004 06:36:21] - Executing new AniDB command.
[12.06.2004 06:36:21] - Converting and saving new mylist data.
[12.06.2004 06:36:21] - Loading mylist data...
[12.06.2004 06:36:22] - Mylist data loaded after 149 milliseconds.
[12.06.2004 06:36:22] - New mylist data saved after 850 milliseconds.
[12.06.2004 06:36:22] - Executing new AniDB command.
[12.06.2004 06:36:23] - Removing obsolete entries.
[12.06.2004 06:36:23] - Obsolete entries removed after 0 milliseconds.
[12.06.2004 06:36:25] - Connection to AniDB successfully terminated. All queued tasks completed.
[12.06.2004 06:36:25] - Trying to connect to AniDB...
[12.06.2004 06:36:26] - Connected to AniDB.
[12.06.2004 06:36:26] - Executing new AniDB command.
[12.06.2004 06:36:26] - New or updated mylist entry, updating....
[12.06.2004 06:36:26] - Executing new AniDB command.
[12.06.2004 06:36:26] - Converting and saving new mylist data.
[12.06.2004 06:36:26] - Loading mylist data...
[12.06.2004 06:36:27] - Mylist data loaded after 139 milliseconds.
[12.06.2004 06:36:28] - New mylist data saved after 1130 milliseconds.
[12.06.2004 06:36:28] - Executing new AniDB command.
[12.06.2004 06:36:28] - Removing obsolete entries.
[12.06.2004 06:36:28] - Obsolete entries removed after 0 milliseconds.

And on and on and on... untill I get a "103xx" someting error telling me "socket error - connection refused" or something like that (sorry, I always click away those messages too fast, I maybe can give you an update in a few hours when it happens again).

Is this something that happens because of the settings or because of the size of my mylist?

Got some more info - seems I found my personal favourite bug :-)

It updates the "watched" info.

I added some directories to the file manager to be watched and marked them "Add new files to mylist" "correct data if different" and checked checked _only_ the box next to the state (it was set to "on cd" for one directory and to "on hdd" for another).

There was _no_ check next to "watched" (!)
AoM changed the state to "unseen" for all files anyway. I stopped it now and deleted the entries in the file manager and will from now on do everything myself when it comes to the state of the files and the storage.

Seems to me AoM can't be trusted with this information. I guess this is also the reason why I lost all my storage info. I bet my ass it set all the storage information to "" even though I did not check the box next to the storage information. Maybe empty field irritate AoM, I don't know, but currently I am a bit pissed... or maybe "correct data if different" means that it checks the data of the entries no matter what is checked or set below! I mean come on, that is nowhere close to beeing intuitive. That should mean that something is updates _if_ and only if there already is information added for that file ( != "").

Just don't use the correct data if different feature please.

Gotcha

How about writing a new readme? I mean I could try doing that (= document "hidden" features

If you want to help make a readme I'll kiss the ground you walk on.
Talk to me on irc first though.

Hehe

Ok I'll try to find you sometime next week.

I guess I should start with AoM 0.6 - once that one is released I can start the readme. At the moment I think I would waste my time if there are as many changes as between 0.3 and 0.5.

So let's wait untill 0.6 gets out and then I will get in touch with you.

it was the same problem i had, check one of the post below.
i had a subdir which i usually have unwatched files, but when i started marking files in that dir as watched, after the FM searched for new files, POOF, back to unwatched, it nearly wrecked all of mylist....

now i have only 1 FM setting and the othe rdir i add it by hand(cumbersome, slow)