-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FFmpeg Writer: handle redirected logs when checking for errors #890
FFmpeg Writer: handle redirected logs when checking for errors #890
Conversation
* Previously we were looking for `'foo' in None` resulting in a TypeError (Zulko#877) * Now, if an `IOError` occurs when running FFmpeg to write video clips, **but** there is no output returned, assume we are redirected, and give the user a helpful message about where to look for errors (i.e. in the logs), instead of throwing a secondary `TypeError`. * Add test for this case. Fixes Zulko#877.
For some reason Pytest on Python 2 is not catching this, even though they are aliases in the code, and Python 3.4 - 3.6 all do...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made some quick feedback, could you also read the contents of the logfile instead of the telling the user to do it ? It would be more transparent and easier. Thanks again for your contrib !
@Overdrivr Sorry - I never saw the feedback. I've updated as suggested... |
@declension this is ok for me and I would like to merge it. Could you fix the conflicts? |
maybe we should rebase it against |
That's the conflicts fixed (just through the web editor). If the tests pass, feel free to merge. |
I can't say I love its newlines, but hey it's here now...
@tburrows13 @mgaitan fixed the remaining PR bits up now, please merge whenever. |
Great, thanks for fixing it up. It will be released with v2.0. |
'foo' in None
resulting in a TypeError (FFMPEG VideoWriter throws TypeError on error when logged. #877)IOError
occurs when running FFmpeg to write video clips, but there is no output returned, assume we are redirected, and give the user a helpful message about where to look for errors (i.e. in the logs), instead of throwing a secondaryTypeError
.Fixes #877.