Ergebnis 1 bis 9 von 9
-
17.02.2020, 17:32 #1
- Registriert seit
- 27.03.2018
- Beiträge
- 101
- Thanks (gegeben)
- 22
- Thanks (bekommen)
- 8
- Total Downloaded
- 511,4 KB
- Total Downloaded
- 511,4 KB
question for oATV developers - Where is the source code translation log file located?
Hi,
I'm currently using openATV 6.2 system.
I modified a bit in one of the source files (TimerEntry.py) and copied it to the correct location on the box (/usr/lib/enigma2/python/Screens).
After rename TimerEntry.pyo to TimerEntry.old. Then I restarted the system on the box.
Unfortunately, the system does not boot and the TimerEntry.py file does not compile. No TimerEntry.pyo file.
I think the modifications in TimerEntry.py file are good.
My question is:
- Where is the source code translation log file located? Where can I find the log file that shows what the problem is?
There is no crash log file in the home directory.
Only the openATV logo appears on the screen.
If I copy the original TimerEntry.pyo file back to its place, the system will work properly after restarting.
I would like to make sure that _("Location") is displayed immediately after _("Timer type") on the _("Timer entry") screen.
I think this would be more useful.
Awaiting response.
Regards,
Alec
-
Advertising
-
17.02.2020, 17:50 #2
- Registriert seit
- 02.01.2017
- Ort
- Slovakia
- Beiträge
- 1.460
- Thanks (gegeben)
- 91
- Thanks (bekommen)
- 418
- Total Downloaded
- 323,0 KB
- Total Downloaded
- 323,0 KB
Box 1:Vu+ Zero 4KBox 2:Vu+ Solo SE V2Box 3:Formuer F4-TURBOHi.
First, you must first enable DebugLOG in OpenATV via the GUI in the OpenATV MENU. Then restart the set top box and DebugLOG will automatically be created in the "/home/root/logs" folder.
Second, as for the OpenATV source code, it is hosted on the GitHub server. There you can request corrections and directly edit the source code or just report the BUG indicating the sources (LOGs, screenshots, etc.). Of course you need to know Enigma well to be sure of a modification that a developer will check. You can write there about changing the code. You can also switch source code BRANCH - for example: DEV; 6.1; 6.2; 6.3; etc. .
It is also quite possible that if you have found a bug in version 6.2, the bug will be fixed in the next 6.4 branch or DEV branch. The current stable OpenATV version is 6.3 and it is possible that the bug has been fixed there.
openatv * GitHub
GitHub - openatv/enigma2: openatv-gui - Enigma2 / OpenATV source code itself
Sign in to GitHub * GitHub
enigma2/PowerTimerEntry.py at DEV * openatv/enigma2 * GitHubGeändert von s3n0 (17.02.2020 um 18:31 Uhr)
-
Danke - 1 Thanksalec-cs bedankten sich
-
17.02.2020, 19:14 #3
- Registriert seit
- 15.06.2013
- Beiträge
- 2.359
- Thanks (gegeben)
- 287
- Thanks (bekommen)
- 1399
- Total Downloaded
- 1,32 MB
- Total Downloaded
- 1,32 MB
Box 1:hd51Box 2:vuduo4kseBox 3:und noch 20-30 andereOther way is to stop e2 by typing “init 4” in Telnet. Then start e2 manually by executing “enigma2” in Telnet. You should now see at the end the error message. If you fix your problem and e2 runs, you can stop it by pressing ctrl+c.
Then restart the box (“restart”) or execute “init 3”.
In python you have to be really careful with spaces and tabs (or better indentation in generell). A single space can make problems.hd51, vuduo4se,....
-
Danke - 1 Thanksalec-cs bedankten sich
-
18.02.2020, 10:54 #4
- Registriert seit
- 27.03.2018
- Beiträge
- 101
- Thanks (gegeben)
- 22
- Thanks (bekommen)
- 8
- Total Downloaded
- 511,4 KB
- Total Downloaded
- 511,4 KB
Themenstarter@s3n0, @betacentauri thanks.
I did the check you suggested.
My code is correct!
The bug can be found in the original source at line 148.
Here: enigma2/TimerEntry.py at 63b70cbd48e192b4a44e89ede09e03d566c533d5 * openatv/enigma2 * GitHub
Bad indentation.
I fixed the bug and then compiled the source code. The system is working properly again!
I'll post my change on GitHub.
I have another question: What should I use for indenting, space or tab in the python source?
Awaiting response.
Regards,
Alec
-
Danke - 1 ThanksPapi2000 bedankten sich
-
18.02.2020, 12:04 #5
- Registriert seit
- 02.01.2017
- Ort
- Slovakia
- Beiträge
- 1.460
- Thanks (gegeben)
- 91
- Thanks (bekommen)
- 418
- Total Downloaded
- 323,0 KB
- Total Downloaded
- 323,0 KB
Box 1:Vu+ Zero 4KBox 2:Vu+ Solo SE V2Box 3:Formuer F4-TURBOThis type of indentation you found in the code does not interfere. It does not matter. It will also work in this code syntax (although there is nothing to do with proper identation).
Identation in Python code must be the same everywhere. It does not matter how long (number of empty spaces or tabs) will be used, but the same. Usually 4x empty spaces or 1x tabulator are used.
More info, for example, here: 2.1.7 Indentation
Empty spaces and tabs must not be combined as the same identation in the same file. Most interpreters cannot then read this and do not automatically translate empty spaces into tabs or vice versa. For example, in Windows, you can use Notepad++ to make these edits. You set how many blank characters will have identation and can then do blank operations (change identation: "tab -> empty spaces" or vice versa: "empty spaces -> tab").
If you found a code error, feel free to edit it directly on GitHub with your "pull request" or write a simple info to "issues".
Working example from the Shell (Python):
Code:root@formuler3ip:~# python Python 2.7.15 (default, Jun 10 2019, 18:26:17) [GCC 8.2.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> >>> >>> c = 0 >>> while c < 3: ... print(c) ... c += 1 ... 0 1 2 >>> c = 0 >>> while c < 3: ... print(c) ... c += 1 ... 0 1 2 >>>
Geändert von s3n0 (18.02.2020 um 12:10 Uhr)
-
Danke - 1 Thanksalec-cs bedankten sich
-
18.02.2020, 15:37 #6
- Registriert seit
- 27.03.2018
- Beiträge
- 101
- Thanks (gegeben)
- 22
- Thanks (bekommen)
- 8
- Total Downloaded
- 511,4 KB
- Total Downloaded
- 511,4 KB
Themenstarterokay thank you.
-
18.02.2020, 18:17 #7
- Registriert seit
- 02.01.2017
- Ort
- Slovakia
- Beiträge
- 1.460
- Thanks (gegeben)
- 91
- Thanks (bekommen)
- 418
- Total Downloaded
- 323,0 KB
- Total Downloaded
- 323,0 KB
Box 1:Vu+ Zero 4KBox 2:Vu+ Solo SE V2Box 3:Formuer F4-TURBOAnd in your case, somehow modifying the code helped ? Did the error correct ? Or how do I understand that, hmm ? Because you mentioned some problem and its correction :-P.
So did you just missed identation the source code ? If that helps, of course, it can be adjusted. However, this should not affect problems. Identation in the source code is fine, I think.
-
18.02.2020, 19:06 #8
- Registriert seit
- 27.03.2018
- Beiträge
- 101
- Thanks (gegeben)
- 22
- Thanks (bekommen)
- 8
- Total Downloaded
- 511,4 KB
- Total Downloaded
- 511,4 KB
ThemenstarterHi,
As I mentioned, I fixed the bug and then compiled the source code. The system is working properly again!
The error occurred at the above location as I reported. I went through all the indentations, set everything to tab. It works!
My modification, development, works well for me.
Because I use the timer many times for recordings, it can be used much better. So it's more practical.
I posted my change on GitHub.
Here: Update TimerEntry.py by alec-cs * Pull Request #1530 * openatv/enigma2 * GitHub
Thanks for your help.
Regards,
Alec
-
18.02.2020, 20:18 #9
- Registriert seit
- 02.01.2017
- Ort
- Slovakia
- Beiträge
- 1.460
- Thanks (gegeben)
- 91
- Thanks (bekommen)
- 418
- Total Downloaded
- 323,0 KB
- Total Downloaded
- 323,0 KB
Box 1:Vu+ Zero 4KBox 2:Vu+ Solo SE V2Box 3:Formuer F4-TURBOOh, OK ... thanks. So I understand.
Lesezeichen