Closed JimStanford99 closed 8 years ago
msg: "Unfortunately, there was an error running your job for Clip1LisaBud_Audio. Alignment and extraction process failed."
@irenelfeng can you look into this? Did you make any changes that might be causing this new behavior?
I didn't make any changes yesterday but yes I can look into it.
Jim, when was the last time you ran a job and it did work?
On Thu, Apr 7, 2016 at 8:11 AM, Sravana Reddy notifications@github.com wrote:
@irenelfeng https://github.com/irenelfeng can you look into this? Did you make any changes that might be causing this new behavior?
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/127#issuecomment-206843376
Seems like a code/data error rather than a system one. I'll look at it.
Should be fixed now.
It was a strange error. We're adding G2P-predicted pronunciations to the dictionary each time a user uploads a file with OOV words. Someone seems to have uploaded a file with a ton of really large numbers, and somehow, the dictionary got corrupted. I reset the dictionary to its original state.
Perhaps we should only use the OOV pronunciations for that user's job and discard them after.
Yes, it's working now on general jobs using Boundaries. Thanks. Problem solved.
On Thu, Apr 7, 2016 at 11:27 AM, Sravana Reddy notifications@github.com wrote:
Should be fixed now.
It was a strange error. We're adding G2P-predicted pronunciations to the dictionary each time a user uploads a file with OOV words. Someone seems to have uploaded a file with a ton of really large ones, and somehow, the dictionary got corrupted. I reset the dictionary to its original state.
Perhaps we should only use the OOV pronunciations for that user's job and discard them after.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/127#issuecomment-206952685
It looks like we have a problem today. I ran a simple test job with the Boundaries option and it failed. Several other users had errors with Boundaries overnight.