[ViX_Misc] Debug logs time format

[Huevos]

How about this...

<03:08:18.3133> [ABM-Scheduler][Scheduleautostart] reason(0), session <__main__.Session instance at 0xb20ef490>
<03:08:18.3135> [ABM-Scheduler][Scheduleautostart] AutoStart Enabled
<03:08:18.3137> [ABM-Scheduler][AutoScheduleTimer] Schedule Disabled at Sun 12 Apr 2020 03:08:18 CEST
<03:08:18.3139> [XMLTVImport] autostart (0) occured at 1586653698.31
<03:08:18.3147> [XMLTVImport] WakeUpTime now set to -1 (now=1586653698)
<03:08:18.3152> [JoyneScan-Scheduler][Scheduleautostart] reason(0), session <__main__.Session instance at 0xb20ef490>
<03:08:18.3153> [JoyneScan-Scheduler][Scheduleautostart] AutoStart Enabled
<03:08:18.3155> [JoyneScan-Scheduler][AutoScheduleTimer] Schedule Disabled at Sun 12 Apr 2020 03:08:18 CEST
<03:08:18.3156> [ImageManager] AutoStart Enabled
<03:08:18.3157> [ImageManager] Backup Schedule Disabled at (now=Sun 12 Apr 2020 03:08:18 CEST)
<03:08:18.3158> [BackupManager] AutoStart Enabled
<03:08:18.3159> [BackupManager] Backup Schedule Disabled at (now=Sun 12 Apr 2020 03:08:18 CEST)
<03:08:18.3411> [Skin] Processing screen 'Screensaver', position=(0, 0), size=(1920 x 1080) for module 'Screensaver'.

https://github.com/Huevos/enigma2/commit/d97ae81e454d27b68f93dae8b566b9c300e78dcf

 

[abu baniaz]

Looks good. Can we try adding a date? No need for year, IMO.

 

[Huevos]

Not sure of the value of the date.

Options are here:
http://www.cplusplus.com/reference/ctime/tm/

 

[Huevos]

Date without year is a problem as it is not clear if it is mm/dd or dd/mm.

Also, adding pointless chars to the left of the log means the log is right shifted maybe making it necessary at times to scroll horizontally to read it.

 

[Huevos]

Also this has a big negative point which is, if you are trying to determine the time difference in seconds between one event and another having the log time in seconds is much easier to cope with.

e.g. if I want to know how long a blindscan took to complete I just subtract one stamp from another. In clock format that is not possible.

Probably better to have another field, I reckon the date isn't terribly important.

<4739496.666 09:58.03.324> [eDVBSectionReader] DMX_SET_FILTER pid=18

or

<4739496.666> 09:58.03.324 [eDVBSectionReader] DMX_SET_FILTER pid=18

The inclusion of the human readable time could be optional - the timestamp is on a flag

If we go with stamp and date we only need the u_sec on one field.

 

[simonc]

I got as far as this yesterday https://github.com/SimonCapewell/enigma2/tree/time-debug-logging, but as ever, getting the C++ build working again after an absence seems to be a black art. Main thing here is that you can chose to have either format or both.

 

[Huevos]

Simon can you make this configurable from the UI? If not how do we change from one to the other?

What box are you using? ARM or MIPS?

 

[simonc]

It'd be an environment variable, so perhaps the UI would be able to manipulate the current environment value. If not, you should be able to set it in the shell before starting the e2 executable.

I think mine is a MIPS box - it's an ET8500

 

[Huevos]

That variable is static ( static int debugTime = 3; ). Does that mean it is immutable? I have no idea of the rules of cpp.

Could be set in the shell script? The shell script can read the settings file to decide what value to send to enigma. That is more or less how debug logs are enabled/disabled at the current time.

 

[simonc]

Static just means it's shared across all instances, like Python's

class MyClass:
    myStatic = 5

    def __init__(self):
        print MyClass.myStatic
        myInstance = 23

Yes, you should be able to test the flag from the shell using

export ENIGMA_DEBUG_TIME=0
enigma2

 

[birdman]

Date without year is a problem as it is not clear if it is mm/dd or dd/mm.

??? Print the month as its short text form (as your original example did). strftime() lets you do anything you want from a template.

 

[Huevos]

Couple of build errors:
https://github.com/Huevos/enigma2/commit/c222ff6b7fec6288057272c88fd6713b9abca281
https://github.com/Huevos/enigma2/commit/51ec140196c3ad018af225799bac8b465844ecf3

Binary attached.

Output looks like this:

<    13.047> 14:21:06.2154 [fb] double buffering available!
<    13.069> 14:21:06.2365 [gFBDC] resolution: 1280x720x32 stride=5120, 17100kB available for acceleration surfaces.
<    13.069> 14:21:06.2366 [eInit] + (9) gLCD
<    13.069> 14:21:06.2367 [eFbLCD] /dev/fb1: No such file or directory
<    13.069> 14:21:06.2368 [eFbLCD] framebuffer /dev/fb1 not available
<    13.069> 14:21:06.2369 [eDboxLCD] xres=132, yres=64, bpp=8 lcd_type=2
<    13.069> 14:21:06.2369 [eLCD] (132x64x8) buffer 0x6c2aa8 8448 bytes, stride 132
<    13.069> 14:21:06.2369 [eLCD] (132x64x8) buffer 0x6b7198 8448 bytes, stride 132
<    13.069> 14:21:06.2369 [gLCDDC] resolution: 132x64x8 stride=132
<    13.069> 14:21:06.2370 [eInit] + (9) Font Render Class
<    13.069> 14:21:06.2370 [Font] Initializing lib...

Now we need to try make it configurable from UI.

 

[simonc]

MIPs one works great. Output with an export ENIGMA_DEBUG_TIME=2 is good:

15:07:31.634 [eInit] - (41) eServiceFactoryDVD
15:07:31.634 [eInit] - (41) eServiceFactoryWebTS
15:07:31.635 [eInit] - (41) eServiceFactoryTS
15:07:31.635 [eInit] - (41) eServiceFactoryHDMI
15:07:31.635 [eInit] - (41) eServiceFactoryM2TS
15:07:31.635 [eInit] - (41) eServiceFactoryMP3
15:07:31.636 [eInit] - (41) eServiceFactoryFS

 

[smipx]

I am appreciating all the work here everyone. I am really grateful this is going to happen.

 

[Huevos]

This adds configurable option from the user interface...
https://github.com/Huevos/enigma2/commit/55d5debb32323d7888dc323a1891e12d7d0c7511

 

[abu baniaz]

Would there be negative effects of making default = local time + boot?

 

[Huevos]

Abu, do whatever you think is good. I just set the default to the current format. In the end there is no default anyway because debug log is disabled by default. So this will only apply when enabling debug logs and saving that screen.

 

[ccs]

Would there be negative effects of making default = local time + boot?

Any chance of making this the default, most crash logs are being posted without this setting, but this format is so much easier to read.

 

[abu baniaz]

Please submit a pull request.

 

[ccs]

Please submit a pull request.

I haven't a clue how to do that. I know you've given details, but ......