-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Handle Mimic missing properly #2718
Handle Mimic missing properly #2718
Conversation
If Mimic was not found at all the LOG message would raise an exception, this fixes that issue and cleans up Exception chain
Voight Kampff Integration Test Succeeded (Results) |
Still a possible error. Steps to reproduce:
Strangely in |
Likely the mimic path is None... The issue is that the fallback_tts object shouldn't be created at all in this case since the validation should fail (since mimic doesn't exist) will investigate |
Verify that the fallback object can execute when creating it
ffe3ef5
to
1ae6271
Compare
So the root issue seem to be that the fallback_tts was never validated. I moved things around a little and added the validation for the fallback. |
Voight Kampff Integration Test Succeeded (Results) |
1 similar comment
Voight Kampff Integration Test Succeeded (Results) |
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.
Looks good, thanks Ake!
Description
I got an error report on chat with the following error:
So the error message in the exception handler throws an exception making the real exception not show.
I also went through the module with pylint and fixed the issues that could be fixed without breaking backwards compatibility.
How to test
Make sure Mimic still works and unittests works. You can also set
BIN
toNone
and check that the correct exception is shown.Contributor license agreement signed?
CLA [ Yes ]