Spaces:
Running
on
Zero
[solved]
Hey! Thanks for sharing, noticed this as well (if this happened a few hours ago) it's possibly due to trying a parsing method lacking conventional support yet in gradio sdk and furthermore it seems like the "opportunity window" of that to happen is when task HW resources are reassigned. I rebased that version of the code so others shouldn't be able to take advantage in other space instances. I'll make further modifications and prepare disclosure to Gradio maintainers, but until then please let me know if you can still replicate :) (as it would indicate a larger issue at hand)
[update: video is now available again! Even though the code in question wasn't improper, as space owner I'm committed to avoid any possible interactions which may cause issues and have taken a different route when reimplementing]