Display errors in the UI
Opened this issue · 4 comments
felixbade commented
At the moment the errors only go to the console and the UI says ”Transcribing...” forever.
felixbade commented
This is annoying because sometimes the transcribing does take a long time.
ontl commented
Yeah I tried submitting an mp3 for translation, but it was over-quota for the key I was using (in fact, I hadn't properly enabled billing for that key).
No errors displayed in UI, but Console says:
Failed to load resource: the server responded with a status of 429 ()
That results in segments being undefined when we try to console.log it at line 72 of index.js, and also segments then not being iterable on line 76.
Would recommend passing along the error in the UI.
felixbade commented
Oh… I’ll remove the claim ”no quota” from README!
felixbade commented
Example situation, pretty common.
