Fix for issues in V7.1.4

[Narflex]

To any of you having issues with V7.1.4, please try it with the following updated Sage.jar file (replace the one in your SageTV folder):

http://download.sagetv.com/v714fix/Sage.jar

If it had moved your Wiz.bin/bak files to be 'corrupt' files, you can restore those and they should load OK. This *should* have no problem loading any Wiz.bin file from prior versions, as well as ones that were marked corrupted by 7.1.3 or 7.1.4.

Please test this out as soon as you can; we would very much like to get confirmation from people that had issues with 7.1.4 that this resolves the problem so we can create a 7.1.5 build today to get the beta back on track.

Sorry for these issues, but we do our best to promptly resolve problems when they do occur.

Please post here if you've tried it along with your results.

Thanks again for all the beta testing support.

[nyplayer]

It appears to have fixed the problem. Here is my new log,

[JREkiwi]

Works for me too.

John

[tmiranda]

The 7.1.4 download links are broken.

[nyplayer]

Installed in my production machine wiz.bin etc... ok no problem at all.

[JREkiwi]

Originally Posted by tmiranda

The 7.1.4 download links are broken.

from SageTV V7.1.4 Beta is Ready!

NOTE: We're temporarily removing the 7.1.4 downloads while we investigate some issues that users are reporting with it; we will post any updates to the beta forum

I suspect 7.1.5 including this fix will be the next one available for download.

John

[Narflex]

If you just append 'X' to the download links for 7.1.4 you can download them to test that way.

Thanks for the quick testing turnaround guys. Much appreciated.

And the log posted above does verify that it did the proper repair by this:

Fri 3/11 13:32:32.667 [main@e89b94] ERROR WITH DATABASE - FOUND CATEGORY ITEM LINKED TO SUBCATEGORY INDEX...REPAIR THIS AFTER LOAD IS FINISHED...THIS IS A KNOWN LEGACY BUG

and this:

Fri 3/11 13:32:34.081 [main@e89b94] Performing database repair on Show category information now...
Fri 3/11 13:32:34.091 [main@e89b94] Done with category repair...fixed 3579 entries.

And we also got a log over email from another user that had a secondary problem related to this.

We were able to reproduce both problems and verify the fixes ourselves. We're doing the builds for 7.1.5 now (but it's the same as 7.1.4 with the new JAR file posted here; we would still like people to try this fix just in case there is some other scenario we did not catch before we post 7.1.5).

[stuckless]

Originally Posted by Narflex

If you just append 'X' to the download links for 7.1.4 you can download them to test that way.

Thanks for the quick testing turnaround guys. Much appreciated.

And the log posted above does verify that it did the proper repair by this:

Fri 3/11 13:32:32.667 [main@e89b94] ERROR WITH DATABASE - FOUND CATEGORY ITEM LINKED TO SUBCATEGORY INDEX...REPAIR THIS AFTER LOAD IS FINISHED...THIS IS A KNOWN LEGACY BUG

and this:

Fri 3/11 13:32:34.081 [main@e89b94] Performing database repair on Show category information now...
Fri 3/11 13:32:34.091 [main@e89b94] Done with category repair...fixed 3579 entries.

And we also got a log over email from another user that had a secondary problem related to this.

We were able to reproduce both problems and verify the fixes ourselves. We're doing the builds for 7.1.5 now (but it's the same as 7.1.4 with the new JAR file posted here; we would still like people to try this fix just in case there is some other scenario we did not catch before we post 7.1.5).

Just out of curiosity... what is it doing when it's "repairing" the categories? There a "bug" in bmt where since 7.1.2 (i think) when people save metadata with a genres then they get slashes appended (or something like that). Bmt doesn't do anything with genres except pass them along to sage, so i'm wondering if this is related??

[Narflex]

Originally Posted by stuckless

Just out of curiosity... what is it doing when it's "repairing" the categories? There a "bug" in bmt where since 7.1.2 (i think) when people save metadata with a genres then they get slashes appended (or something like that). Bmt doesn't do anything with genres except pass them along to sage, so i'm wondering if this is related??

The problem was that it used database IDs from the 'subcategory' index for objects in the category field. So when it loaded a database and tried to look up those 'category' items, it was getting a null reference.

Coding lesson for the day:

int x = 0;
int[] array = new int[2];
array[x++] = (x == 0) ? 1 : 2;

This results in array[0] = 2. Arguments for an operator are always evaluated from left to right; with the assignment being the primary operator. Easy one to forget about of course.

I don't think the problem you mention is related...but we did change things related to categories in V7.1.3...I'd need to know the exact API calls you're using to get/set the data. But I think I know which ones...and I took a look at the diffs back to 7.0...and the behaviors looked like they'd be the same as in 7.0.

[jptheripper]

Wow you guys are really awesome. I cant test until later tonite (kids demanding a movie).

Would you prefer a 7.1.4 with "patch" test or a 7.1.5 test once out.

[PLUCKYHD]

Originally Posted by Narflex

The problem was that it used database IDs from the 'subcategory' index for objects in the category field. So when it loaded a database and tried to look up those 'category' items, it was getting a null reference.

Coding lesson for the day:

int x = 0;
int[] array = new int[2];
array[x++] = (x == 0) ? 1 : 2;

This results in array[0] = 2. Arguments for an operator are always evaluated from left to right; with the assignment being the primary operator. Easy one to forget about of course.

I don't think the problem you mention is related...but we did change things related to categories in V7.1.3...I'd need to know the exact API calls you're using to get/set the data. But I think I know which ones...and I took a look at the diffs back to 7.0...and the behaviors looked like they'd be the same as in 7.0.

I think what he is refering to is it appears it is storing multiple categories now with a "/" separator between categories when it did use "," I am seeing issues with this in diamond too. Can you confirm this change?

[GKusnick]

Originally Posted by jptheripper

Would you prefer a 7.1.4 with "patch" test or a 7.1.5 test once out.

The whole point of the patch is to test it before 7.1.5. goes live.

[Narflex]

Originally Posted by PLUCKYHD

I think what he is refering to is it appears it is storing multiple categories now with a "/" separator between categories when it did use "," I am seeing issues with this in diamond too. Can you confirm this change?

Please let me know what API calls you're referring to with this. Each category is stored separately, we don't store them all together with a slash between them. And please start another thread to continue this discussion.

[jptheripper]

The whole point of the patch is to test it before 7.1.5. goes live.

Originally Posted by Narflex

We're doing the builds for 7.1.5 now (but it's the same as 7.1.4 with the new JAR file posted here; we would still like people to try this fix just in case there is some other scenario we did not catch before we post 7.1.5).

Since they are already doing the build, i think that is a moot point, which is why I asked.

[Narflex]

Originally Posted by jptheripper

Since they are already doing the build, i think that is a moot point, which is why I asked.

But we haven't posted the build yet...we'll definitely redo it if there are issues found...so please do test the patch against 7.1.4.

[jptheripper]

Happy to!

[vikingisson]

That made a big difference on mine.

[fuzzy77]

Fixed my issues. My client machines couldn't even connect to the server before the patch.

From the client log

Sat 3/12 0:38:12.423 [main@5740bb] Error establishing server connection of:java.lang.ArrayIndexOutOfBoundsException: 1
Sat 3/12 0:38:12.428 [main@5740bb] NetworkClient fullCleanup null
Sat 3/12 0:38:12.428 [main@5740bb] Cleaning up c/s connection
Sat 3/12 0:46:58.984 [main@5740bb] Removed system shell hook
Sat 3/12 0:46:58.985 [main@5740bb] Sage.exit() called.
Sat 3/12 0:46:58.986 [main@5740bb] Stopping all core plugins

[fuzzy77]

Actually, it looks like after restoring my wiz.bin now all of my favorites have been removed

[jptheripper]

I look like i am all good.

When i restored back to 7.1.3, i lost about half of my detailed setup settings (like wrapping, etc..) was weird.

However, all the corruption/null pointer issues seem to be gone. Upgrading to 715