Looking at the code, I found a change in Gradio’s specifications.
I can’t believe it, but could Gradio’s repeated specification changes be causing code conflicts…?
Forgot to mention, but there’s a misunderstanding in this comment.
cache_examples still accepts “lazy” in gradio 5.x so that gradio 4.x Spaces that specify cache_examples=”lazy” won’t break when upgrading to gradio 5.x. It shows a warning that it will stop working in the future. You mentioned that we’ve changed it repeatedly, but that’s not the case.