Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[Mut@nt HD2400] Crash in 6.8.007 (self built) - when coming out of playback and no tuner free to return to live TV

No it isn't. The commit log (I see now) just says [SourceCurrentService] add sanity, which is, frankly, a useless commit log as it says absolutely nothing more than the code change itself. There is nothing about why the code change was made, which is what the commit log is actually for. No reference to here, nor nothing here to say that the issue has now been resolved / fixed. That's no traceability or visibility. You can't get stroppy with a curt "That was already fixed." when you've just silently fixed it, as though in a vacuum.

"Over and Out"
 
Ok, you don't know what a sanity test is so you want me to waste precious time writing an exhaustive commit text.
 
I expect if you've fixed the problem you'd come back here, where it was originally reported, and say so.

Failing to do that actually did waste my "precious time" in raising the Issue because it looked like it had dropped through the gap into oblivion.

That was already fixed.
... and then you just expect me to know it's been fixed how, by osmosis?

Ok, you don't know what a sanity test is so you want me to waste precious time writing an exhaustive commit text.
And yes, I know what a sanity test is - looking at the code it's blinding obvious that and (sref := self.serviceref) is a sanity test. Your commit comment is just a waste of time because it adds nothing, no knowledge or insight, you might as well have just written "and (sref := self.serviceref)" as the comment.

Ok. You want help... but supplying the debug log is too difficult for you.
I did supply the redacted debug log, but there was no thanks or acknowledgement for doing so. That just looks like another waste of my time.

Frankly, @Huevos , all I see is an unpleasant, arrogant attitude from you.

I thought I was doing this community a favour by reporting this problem, along with my workaround (I was not "wanting help").

I'll definitely think twice about contributing in future.

Good bye.
 
I can see from your answer you like long texts... I like short and direct ones... So we will just have to agree to differ.
 
I expect if you've fixed the problem you'd come back here, where it was originally reported, and say so.

Failing to do that actually did waste my "precious time" in raising the Issue because it looked like it had dropped through the gap into oblivion.


... and then you just expect me to know it's been fixed how, by osmosis?


And yes, I know what a sanity test is - looking at the code it's blinding obvious that and (sref := self.serviceref) is a sanity test. Your commit comment is just a waste of time because it adds nothing, no knowledge or insight, you might as well have just written "and (sref := self.serviceref)" as the comment.


I did supply the redacted debug log, but there was no thanks or acknowledgement for doing so. That just looks like another waste of my time.

Frankly, @Huevos , all I see is an unpleasant, arrogant attitude from you.

I thought I was doing this community a favour by reporting this problem, along with my workaround (I was not "wanting help").

I'll definitely think twice about contributing in future.

Good bye.
You do know that no image devs are paid for creating, updating or fixing these images that you use for FREE, right ?

It seems that you are the one with "an unpleasant, arrogant attitude".

You reported a bug, he fixed it for you, thank him and move on.
 

OpenViX Feeds Status

Back
Top