Open a2lin opened 10 years ago
does it stop after a certain amount of time, a specific action (tied to twilio maybe?), or is it just a random but consistent interrupt of some sort?
From my experience it seems like it stops randomly (could be a frontend bug or a thread-safety issue), or it could be tied to disconnects (this is what we were seeing during the demo).
probably both. this is likely very intertwined with #24
afaict the audio daemon's file creation bit is stable, which means it's either a problem with audio.py -> firebase, or firebase -> js
we can tell which it is probably by opening up firebase's forge webui thing and seeing if the audio daemon's file creations are matched up to new tracks entries.
but again the fix for #24 will probably remove this issue.
Random stopping is probably due to server-side dc's locally, we throw an error and never recover on disconnect (max retries on firebase). We can do some exponential backoffs or just say #shipit and forget about it now that we know the root cause.
Alternatively we could make it crash all the way out... (fail fast)
I'm not sure if it's an internet problem, but either the javascript or the server stops constantly. We either need to make it respond more quickly upon reconnection, or resolve the underlying issues that cause the application to become unresponsive.