1 Like
It looks very much like this case… Specifically, it seems to be more likely to occur when Gradio4 is unintentionally upgraded to Gradio5.
I can’t tell without the code, so it would be easier if you could show me the parts of the code that would not be a problem to disclose.
Oh 
, I hope that the Gradio4 & Gradio5 rendezvous gets situated aka fixed very soon frfr:100:
1 Like
Well, Gradio is a good library, but it’s always fickle!
Gradio5 itself hasn’t changed as drastically as it did from 3 to 4, and most of the existing code works as is, but it seems that only proprietary components won’t work outside of Gradio4 unless the component author modifies them, since they specify Gradio “4”. In most cases, it seems that all we need to do is loosen the version specification, but if the maintainer is not active, we are stuck.
As a last resort, we can duplicate and modify Spaces as in the case below.