Jump to content


Photo

Instant recording (with custom duration) faulty in nightly build


  • Please log in to reply
81 replies to this topic

Re: Instant recording (with custom duration) faulty in nightly build #41 littlesat

  • PLi® Core member
  • 57,122 posts

+698
Excellent

Posted 23 August 2023 - 13:00

There is also nothing in our code like usable characters. It here simply give as type that the input should be a NUMBER... So where does it go wrong?

                def changeDuration(self, entry):
                                if entry is not None and entry >= 0:
                                                self.selectedEntry = entry
                                                self.session.openWithCallback(self.inputCallback, InputBox, title=_("How many minutes do you want to record?"), text="5", maxSize=False, type=Input.NUMBER)
 
                def addRecordingTime(self, entry):
                                if entry is not None and entry >= 0:
                                                self.selectedEntry = entry
                                                self.session.openWithCallback(self.inputAddRecordingTime, InputBox, title=_("How many minutes do you want add to the recording?"), text="5", maxSize=False, type=Input.NUMBER)

Edited by littlesat, 23 August 2023 - 13:00.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Instant recording (with custom duration) faulty in nightly build #42 littlesat

  • PLi® Core member
  • 57,122 posts

+698
Excellent

Posted 23 August 2023 - 13:27

So I suggest we should revert this: https://github.com/O...edd07a67ba42f38 it does not have any added value as I cannot verify how to get it not being a number in the first place.....


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Instant recording (with custom duration) faulty in nightly build #43 Stan

  • Senior Member
  • 380 posts

0
Neutral

Posted 23 August 2023 - 13:32

I just tried to verify the issue with the 5 space 5... but I tried with instant recording but I was not able to get it. How did you arrange to get 5 space 5... I can't.

Enter 555 then press once [<<]



Re: Instant recording (with custom duration) faulty in nightly build #44 littlesat

  • PLi® Core member
  • 57,122 posts

+698
Excellent

Posted 23 August 2023 - 13:49

What do you mean with [<<]?


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Instant recording (with custom duration) faulty in nightly build #45 Stan

  • Senior Member
  • 380 posts

0
Neutral

Posted 23 August 2023 - 13:56

[<<] = Button "Previous"

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/StartEnigma.py", line 223, in processDelay
    callback(*retval)
  File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 2748, in inputCallback
ValueError: invalid literal for int() with base 10: '5 5'
[ePyObject] (CallObject(<bound method Session.processDelay of <__main__.Session object at 0xb1903310>>,()) failed)

 


Edited by Stan, 23 August 2023 - 14:01.


Re: Instant recording (with custom duration) faulty in nightly build #46 mrvica

  • Senior Member
  • 1,259 posts

+86
Good

Posted 23 August 2023 - 13:57

Stan was quicker


Edited by mrvica, 23 August 2023 - 13:57.


Re: Instant recording (with custom duration) faulty in nightly build #47 tension

  • Senior Member
  • 119 posts

+4
Neutral

Posted 23 August 2023 - 14:14

I just tried to verify the issue with the 5 space 5... but I tried with instant recording but I was not able to get it. How did you arrange to get 5 space 5... I can't.

It comes from old bugged call in infobarGenerics

self.session.openWithCallback(self.inputCallback, InputBox, title=_("How many minutes do you want to record?"), text="5  ", maxSize=True, type=Input.NUMBER)

now fixed by @ims



Re: Instant recording (with custom duration) faulty in nightly build #48 tension

  • Senior Member
  • 119 posts

+4
Neutral

Posted 23 August 2023 - 14:36

Perhaps it could be escluded the digit of "tab" in inputBox when input is not text

	def keyTab(self):
		if self["input"].type == Input.TEXT:
			self["input"].tab()

but t i do not know other remote controls chance than mine old vuduo2's one. That is: I have not a blank space (" ") button on the remote control...

 



Re: Instant recording (with custom duration) faulty in nightly build #49 ims

  • PLi® Core member
  • 13,781 posts

+214
Excellent

Posted 23 August 2023 - 15:03

So I suggest we should revert this: https://github.com/O...edd07a67ba42f38 it does not have any added value as I cannot verify how to get it not being a number in the first place.....

this code is not more there... but my fix is in develop only, not in 9rc, imho...


Kdo nic nedělá, nic nezkazí!

Re: Instant recording (with custom duration) faulty in nightly build #50 Stan

  • Senior Member
  • 380 posts

0
Neutral

Posted 23 August 2023 - 15:10

Are RC9 and develop now drifting apart? What is the difference?


Edited by Stan, 23 August 2023 - 15:18.


Re: Instant recording (with custom duration) faulty in nightly build #51 ims

  • PLi® Core member
  • 13,781 posts

+214
Excellent

Posted 23 August 2023 - 15:32

 

[<<] = Button "Previous"

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/StartEnigma.py", line 223, in processDelay
    callback(*retval)
  File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 2748, in inputCallback
ValueError: invalid literal for int() with base 10: '5 5'
[ePyObject] (CallObject(<bound method Session.processDelay of <__main__.Session object at 0xb1903310>>,()) failed)

it was fixed 3 days ago, it is impossible type anything than numbers yet there.

 

RC9 is fixed to date release and develop goes ahead ( only WW can shift a pin of enigma in RC).


Edited by ims, 23 August 2023 - 15:35.

Kdo nic nedělá, nic nezkazí!

Re: Instant recording (with custom duration) faulty in nightly build #52 littlesat

  • PLi® Core member
  • 57,122 posts

+698
Excellent

Posted 23 August 2023 - 15:37

I see it...

 

Nice...

 

https://github.com/O...288e3e377c90ecb

 

Actually the initial default value was set wrong.... creasy...


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Instant recording (with custom duration) faulty in nightly build #53 WanWizard

  • PLi® Core member
  • 70,409 posts

+1,808
Excellent

Posted 23 August 2023 - 15:46

Are RC9 and develop now drifting apart? What is the difference?

 

No, but syncing is a manual operation, and only happens when changes in develop are proven to be stable.

 

And the rc build doesn't run continuously, but is started manually to (we run develop builds in a CI environment, 24/7).


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Instant recording (with custom duration) faulty in nightly build #54 ims

  • PLi® Core member
  • 13,781 posts

+214
Excellent

Posted 23 August 2023 - 15:53

I see it...

 

Nice...

 

https://github.com/O...288e3e377c90ecb

 

Actually the initial default value was set wrong.... creasy...

What ? It is fuly fixed now. Is possible put numbers only and remove numbers ... no spaces more.


Kdo nic nedělá, nic nezkazí!

Re: Instant recording (with custom duration) faulty in nightly build #55 Stan

  • Senior Member
  • 380 posts

0
Neutral

Posted 23 August 2023 - 15:56

Does this mean, that bugs reported for RC9 get fixed in develop first? It's difficult to keep track in terms of testing.


Edited by Stan, 23 August 2023 - 15:58.


Re: Instant recording (with custom duration) faulty in nightly build #56 ims

  • PLi® Core member
  • 13,781 posts

+214
Excellent

Posted 23 August 2023 - 15:59

Does this mean, that bugs reported for RC9 get fixed in develop first?

yes ... work on develop (nightly builds) continues ...


Kdo nic nedělá, nic nezkazí!

Re: Instant recording (with custom duration) faulty in nightly build #57 WanWizard

  • PLi® Core member
  • 70,409 posts

+1,808
Excellent

Posted 23 August 2023 - 16:14

Indeed.

 

Besides that, rebasing the rc branch with the develop updates is easier than backport fixes in the rc branch that could collide with ongoing development.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Instant recording (with custom duration) faulty in nightly build #58 littlesat

  • PLi® Core member
  • 57,122 posts

+698
Excellent

Posted 24 August 2023 - 14:12

But I also looked for the reason why the "5  " was in there for the first place,,,

 

The "issue" was introduced here: https://github.com/O...0343341603eaba5

 

"InfoBarGenerics - restrict minutes for changeDuration and addRecordingTime to 3 digits.


This avoids that users set incredible amount of minutes (e.g. 99999999) which then creates a BS in TimerList
ValueError: timestamp out of range for platform time_t"
 
So the issue that was tried to resolve with this is back in.... maybe we should make maxSize not only True/False, but also allow that it is a number (e.g. 3) and arrange the number could not be more than 3 digits...
 
And I see that complete Inbox stuff... that is not a nice code... maxSize is a bool here and the size is defined by the initial string... I would expect this should be a simple number... and the maxsize in the code is therefore determined by the lenght of the string... I hope this can be one or less easily changed... or we capture it when the number became too high that removed/block the latest digit....

Edited by littlesat, 24 August 2023 - 14:21.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Instant recording (with custom duration) faulty in nightly build #59 ims

  • PLi® Core member
  • 13,781 posts

+214
Excellent

Posted 24 August 2023 - 15:32

about limit ... may be limited to 1440 minuts, as it exist for "infinity".


Kdo nic nedělá, nic nezkazí!

Re: Instant recording (with custom duration) faulty in nightly build #60 Stan

  • Senior Member
  • 380 posts

0
Neutral

Posted 24 August 2023 - 15:36

If Input is > 1440, then display a message about the maximum allowed and clear inputbox.




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users