Plugin: Sage Recording Extender (SREv3)

[cat6man]

well, there is no rush since there won't be another all star game until a year from now

[spacecadet]

I've noticed that over the last week or so most (all?) of my sports recordings are being extended with the default padding.

Not sure what to make of this except the Red Sox are on the West Coast this week and the games are ending after midnight. Anyone else who records the Red Sox having this issue? All I know is that lately, I've been seeing about 2 dozen system messages a week related to SRE.

Let me know how I can help to debug.

Errors in the log look like this:

2010-07-24 01:34:00,401 INFO  [AiringMonitor]: 'MLB Baseball: Boston Red Sox at Seattle Mariners': Next check in 2 minutes...
2010-07-24 01:34:27,667 WARN  [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
	at com.google.code.livepvrdata4j.Client.getStatus(Client.java:148)
	at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
	at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:63)
	at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
	at java.util.TimerThread.mainLoop(Unknown Source)
	at java.util.TimerThread.run(Unknown Source)

[Slugger]

I need the entire sre.log file starting at 10pm (when the game started). It does appear to be a bug with either my code or the livepvrdata lib when the date changes over at midnight. I'll have to do some more testing, but the complete log for the game is a good place for me to start.

[cat6man]

Originally Posted by spacecadet

I've noticed that over the last week or so most (all?) of my sports recordings are being extended with the default padding.

Not sure what to make of this except the Red Sox are on the West Coast this week and the games are ending after midnight. Anyone else who records the Red Sox having this issue? All I know is that lately, I've been seeing about 2 dozen system messages a week related to SRE.

i was going to post the same thing here about the sox games on the west coast getting the default padding and an error message saying it couldn't be monitored.

let me know if you need a 2nd log.

[Slugger]

Originally Posted by cat6man

i was going to post the same thing here about the sox games on the west coast getting the default padding and an error message saying it couldn't be monitored.

let me know if you need a 2nd log.

More logs are never a bad thing... send it my way, please. Just prune it so it starts when the game started.

[spacecadet]

Originally Posted by Slugger

I need the entire sre.log file starting at 10pm (when the game started). It does appear to be a bug with either my code or the livepvrdata lib when the date changes over at midnight. I'll have to do some more testing, but the complete log for the game is a good place for me to start.

Check your PM for a copy of my log file.

Thanks!

[cat6man]

another log for overnite recording with the same problem (same angels/sox going
past midnight local time)

[Slugger]

Originally Posted by cat6man

another log for overnite recording with the same problem (same angels/sox going
past midnight local time)

Can you PM me your IP address? Assuming it's the one I see in the livepvrdata.com logs sent to me then I can clearly see that there's a bug. When the game starts it correctly used the date '20100727' but then at the 12:30am status check it queried the event using the date '20100728', which is obviously the problem. I just haven't had time to investigate whether it's an SRE bug or a bug with the livepvrdata library.

Trust me, this is my #1 priority once I have a few spare cycles, but there's just lots of "life" things going on right now that are chewing up all of those free cycles that are coming my way. Rest assured, however, that I will get to this asap. I've created a ticket for this issue and interested users may want to star that ticket at the project site to receive email updates as progress is made.

[cat6man]

hi slugger,

please, there is really no rush to get this fixed..........when you have time to get to it is cool (plus the sox are done with the west coast now ).......real life takes precedence, plus it is summer vacation time

as for my IP address, do you mean the ip address for the fios WAN side?

cheers

[Slugger]

Originally Posted by cat6man

as for my IP address, do you mean the ip address for the fios WAN side?

cheers

Yes, please.

[Slugger]

Snapshot 901 is now in the repository. This build contains the fix for the "airing monitor fails after midnight" bug (issue 137). It also contains the fix for issue 136 (unable to create overrides for future events).

These fixes are bundled with various GUI fixes, which are functional, but not complete. After playing with both SmartGWT and GXT, I've decided I like GXT better and have begun converting SRE from SmartGWT to GXT. These changes aren't complete, but are at a stage that everything that needs to be functional is and in order to deliver the "midnight" fix in a timely fashion, I also had to deliver the GXT fixes.

Please report back your results, especially if you find any bugs.

[Slugger]

Originally Posted by Slugger

Please report back your results, especially if you find any bugs.

I don't record many late games and only did a couple to test the "midnight" fix. If anyone else is recording late games please let me know how it goes with 901.

[Sparhawk6]

Slugger, when I click "get auth code," I get a "HTTP ERROR 404" error with a very long URL and "NOT_FOUND" at the bottom. How do I fix that?

[Slugger]

Originally Posted by Sparhawk6

Slugger, when I click "get auth code," I get a "HTTP ERROR 404" error with a very long URL and "NOT_FOUND" at the bottom. How do I fix that?

Fixed in snapshot 903.

[Slugger]

The livepvrdata.com team had released their latest (closed) beta, which is an API breaker from previous releases. I'm testing the updates required in SRE and will get an update in the repository asap. SRE is broken until you upgrade. (Hopefully it's no more than a couple hours before the update is in the repository.)

[Slugger]

A little ahead of schedule and ready in time for tonight's games!

No actual code changes required to support the latest livepvrdata4j lib, I just had to change the dependencies in sre to require the latest lib. As an added bonus, this snapshot includes an early preview of the ported global override editor. It's functional, but a little buggy still. Should be ready in plenty of the time for the start of NCAA football (where it's needed most).

[kchase56]

I'm running the latest 906 build of SRE and my log file has the following types of errors =>

2010-08-05 21:41:50,290 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2010-08-05 21:41:50,627 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2010-08-05 21:41:50,915 WARN [OverrideValidator]: OverrideValidator error
com.google.code.livepvrdata4j.RestException: ESPN Bottom Line feeds do not support future event lookups!
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:145)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2010-08-05 21:41:50,944 INFO [MonitorStatusChecker]: Done monitor status check. [2406ms]


Any light you could shed on this problem would be greatly appreciated.

Thanks

[Slugger]

Those errors are normal. They mean that SRE is trying to validate games on future days, but livepvrdata.com is not able to. This is because livepvrdata.com is using the ESPN.com Bottom Line feed as its source for MLB scores and that feed only supports the current day's games so when SRE asks livepvrdata to verify a future game, livepvrdata fires an error saying it can't verify the event. Even though it's an expected error, SRE still logs it as an error with the stack trace b/c SRE does not know what's an "expected" error and what isn't. This extra logging is necessary to ensure that "unexpected" errors are fully logged as well.

Once a game starts recording then you should see log entries from "[AiringMonitor]" describing that it's properly monitoring the game or you should get a system message in sagetv saying that there is a problem monitoring the active recording. If you get the latter, then I definitely want to see those logs.

[kchase56]

Basically SRE has stopped monitoring events all together. What can I send you to help debug this issue? The SRE.log file contains nothing but items like what I previously posted, so I don't think that it would be of any use to you.

Here is what was logged during the recording of the Red Sox vs. Cleveland game yesterday =>

2010-08-04 19:08:46,922 INFO [AiringMonitor]: 'MLB Baseball: Cleveland Indians at Boston Red Sox': Next check at Wed Aug 04 21:30:00 EDT 2010
2010-08-04 19:09:07,750 WARN [OverrideValidator]: OverrideValidator error
java.io.IOException: <html>
<head>
<title>Status page</title>
</head>
<body style="font-family: sans-serif;">
<h3>Method Not Allowed</h3><p>You can get technical details <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.6">here</a>.<br>
Please continue your visit at our <a href="/">home page</a>.
</p>
</body>
</html>

at com.google.code.livepvrdata4j.Client.submit(Client.java:99)
at com.google.code.livepvrdata4j.Client.submit(Client.java:90)
at com.google.code.livepvrdata4j.Client.getStatus(Client.java:161)
at com.google.code.sagetvaddons.sre3.server.OverrideValidator.check(OverrideValidator.java:46)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.checkMonitor(MonitorStatusChecker.java:65)
at com.google.code.sagetvaddons.sre3.server.MonitorStatusChecker.run(MonitorStatusChecker.java:37)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2



Thanks

[Slugger]

You were still running 903 after the livepvrdata.com upgrade, which required 906 to operate. Show me [AiringMonitor] logs from last night (Aug 5) where a game was not being properly monitored (assuming you had also upgraded to 906 by then).