Closed joanise closed 4 weeks ago
Review changes with SemanticDiff.
Analyzed 1 of 2 files.
Filename | Status | |
---|---|---|
:grey_question: | make-everyvoice-env | Unsupported file format |
:heavy_check_mark: | everyvoice/demo/app.py | Analyzed |
CLI load time: 0:00.25
Pull Request HEAD: 61abbd4a887650d5b4ef32d411441fb9edce61e7
Imports that take more than 0.1 s:
import time: self [us] | cumulative | imported package
Attention: Patch coverage is 0%
with 10 lines
in your changes missing coverage. Please review.
Project coverage is 74.23%. Comparing base (
3830a83
) to head (61abbd4
). Report is 6 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
everyvoice/demo/app.py | 0.00% | 10 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
PR Goal?
Make sure ffmpeg is installed, and error out for a clear message if not
two changes:
make-everyvoice-env
now just always installs ffmpegeveryvoice demo
exits right away if ffmpeg is not found, since we know we'll crash when the user eventually clicks onsynthesize
Fixes?
Fixed #527
Feedback sought?
general validation
Priority?
beta
Tests added?
no, because we don't have any CI for
everyvoice demo
at the moment.How to test?
1) get yourself an environment where ffmpeg is not installed (
which ffmpeg
will return nothing) and runeveryvoice demo fp.ckpt vocoder.ckpt
and see it exit with clear instructions.2) create a new environment with
make-everyvoice-env
and see thatwhich ffmpeg
is right in your conda env.Confidence?
high
I tested this thoroughly, with ffmpeg not on my path, and with ffmpeg on my path but corrupted (and thus not runnable) and you get the error message each time, whereas with a good ffmpeg things proceed normally.
Version change?
no
Related PRs?