Gradio. Could not find files for the given pattern(s)

Hi. Just installed Gradio, Wrote 3 or 4 test scripts and each one gives the error in the topic subject. All the apps I tested worked but don’t understand why im getting this message. I updated gradio with pip and i’ve tested both normal run and hot reload. Doesn’t matter if i start from .bat, cmd, or .py, the error still appears. Also, without creating a new topic, at times the app does not update and appears to use a cached previous version despite clearing the browser, changing the browser, rename the py, and even restarting the Win 10 PC…which I know doesn’t make any sense.

1 Like

Gradio seems to give that kind of error if the path is not passed.

Hi. And thanks for the quick reply. Which path? If my applications are functional then we have to conclude the paths are correct. I have 5 Stable Diffusion UIs, sharing the same checkpoints and Loras, and they all work perfectly from one python installation on the same drive. Am I missing something? Please note I mistakenly wrote “Error” in my OP, but it’s Info, not an error. Still I’d like to understand why given it is not a path issue, at least not one with python.

So is this it?
Because in Windows, if you call a batch file from Powershell or something like that, CMD will be launched.

Thank you for the link John. Unfortunately the “solution” doesn’t answer my question. As you know there are dozens of ways to launch a python app. You can do it from CMD in explorer, from a .bat file, from powershell, by double clicking on the .py file itself, from a VS Code terminal, and on and on. This doesn’t explain why I’m getting this info message on a fresh install.

Edit: also the link you read isn’t related to Gradio. It is a generic error, and in this case was related to web3 and/or c++ tools, rather than Gradio which has different requirements and dependencies.
Cheers

It is indeed strange that there is an error message instead of a warning or notice even though it works.
Since I am also in a Windows environment, I often encounter phenomena that are difficult to encounter in Linux or Mac.
In the case of Python, when there are multiple Pythons in the environment, and sometimes a different Python is called than expected. But even in this case, if an error occurs, we usually abort there.