Reply to thread

Message

Great.

If you're following the internal 1.17 PR release thread (which I hope you are!) you'll see that Owlsroost's fix is included in the latest test builds. No problem reports there with it either (though I suspect people are not specifically testing the fix), so it's well on its way to being included in the release. Thanks again for your thorough testing and information gathering. It really does make a dev's life much easier.

Aside from the fact that these are error log entries, is there something that's concerning you about this scenario? I mean, I don't see any negative effects. Not that a lack of negative effects is a good excuse to ignore an error message. Rather, I'm just trying to fully understand the scenario.

Well, I can say without a shadow of a doubt that the log entries have nothing to do with the [now-resolved] issue in the streaming server. Therefore a new thread would probably be appropriate. However, before we spring for that...

The meaning of the message is that TV Server failed to unset the recording flag/marker on the program associated with the schedule. That flag/marker is used to determine whether a program should be marked as "recording" (red shading, dot or whatever) in the EPG. I'm pretty sure the reason the failure occurred is that an EPG update ran between 17:47 and 17:53. The original program associated with the schedule would likely have been deleted as part of that update. If the program was deleted (which is consistent with the "...0 did not match the expected count of 1..." part of the log message) there'd be no way to un-flag/un-mark it.

In other words: I currently think there's nothing further to investigate and that the error message could be ignored. However, again, I want to make sure that I haven't missed something.

<blockquote data-quote="mm1352000" data-source="post: 1221462" data-attributes="member: 82144">Great. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />If you're following the internal 1.17 PR release thread (which I hope you are!) you'll see that Owlsroost's fix is included in the latest test builds. No problem reports there with it either (though I suspect people are not specifically testing the fix), so it's well on its way to being included in the release. Thanks again for your thorough testing and information gathering. It really does make a dev's life much easier. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />Aside from the fact that these are error log entries, is there something that's concerning you about this scenario? I mean, I don't see any negative effects. Not that a lack of negative effects is a good excuse to ignore an error message. Rather, I'm just trying to fully understand the scenario.Well, I can say without a shadow of a doubt that the log entries have nothing to do with the [now-resolved] issue in the streaming server. Therefore a new thread would probably be appropriate. However, before we spring for that...The meaning of the message is that TV Server failed to unset the recording flag/marker on the program associated with the schedule. That flag/marker is used to determine whether a program should be marked as &quot;recording&quot; (red shading, dot or whatever) in the EPG. I'm pretty sure the reason the failure occurred is that an EPG update ran between 17:47 and 17:53. The original program associated with the schedule would likely have been deleted as part of that update. If the program was deleted (which is consistent with the &quot;...0 did not match the expected count of 1...&quot; part of the log message) there'd be no way to un-flag/un-mark it.In other words: I currently think there's nothing further to investigate and that the error message could be ignored. However, again, I want to make sure that I haven't missed something.</blockquote>

[QUOTE="mm1352000, post: 1221462, member: 82144"] Great. :) If you're following the internal 1.17 PR release thread (which I hope you are!) you'll see that Owlsroost's fix is included in the latest test builds. No problem reports there with it either (though I suspect people are not specifically testing the fix), so it's well on its way to being included in the release. Thanks again for your thorough testing and information gathering. It really does make a dev's life [I]much [/I]easier. (y) Aside from the fact that these are error log entries, is there something that's concerning you about this scenario? I mean, I don't see any negative effects. Not that a lack of negative effects is a good excuse to ignore an error message. Rather, I'm just trying to fully understand the scenario. Well, I can say without a shadow of a doubt that the log entries have nothing to do with the [now-resolved] issue in the streaming server. Therefore a new thread would probably be appropriate. However, before we spring for that... The meaning of the message is that TV Server failed to unset the recording flag/marker on the program associated with the schedule. That flag/marker is used to determine whether a program should be marked as "recording" (red shading, dot or whatever) in the EPG. I'm pretty sure the reason the failure occurred is that an EPG update ran between 17:47 and 17:53. The original program associated with the schedule would likely have been deleted as part of that update. If the program was deleted (which is consistent with the "...0 did not match the expected count of 1..." part of the log message) there'd be no way to un-flag/un-mark it. In other words: I currently think there's nothing further to investigate and that the error message could be ignored. However, again, I want to make sure that I haven't missed something. [/QUOTE]