Closed georgy7 closed 2 months ago
runtime errors will be handled, and thrown to the GUI layer
I confirm in commit 4dec09db5a991d21628afe4612de77ff6883643a
It is displayed in the UI:
However, it seems to show internal error upon completion. The progress bar, by the way, does not update the percentages.
It would be useful to capture the output of catframes and allow it to be opened in case of an error to get more details. This is quite easy to do, except that the temporary folder with these logs must live all the time while the main window is open.
If you stretch these Task rows horizontally, there is enough space for a button/link (or two buttons/links) to open txt-logs using a simple form with monospaced font or a standard text editor.
Steps to reproduce Internal process error:
Update: Can not reproduce on catframes.py with #26
The file is ready, ffmpeg and catframes have completed, but the task is supposedly not completed. The progress is displayed as 0%.
Update: Can not reproduce on catframes.py with #26
This is not how the subprocess should be started.
shell=True
. You get too attached to the platform. And it may cause security problems. You also get the terminal's PID instead of PID of the script.stderr
.