-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INFO: Could not find files for the given pattern(s) message appears on Windows #9974
Comments
Hi @JackismyShephard I can't repro this issue locally, I'm pretty sure this is not gradio-related! See similar issues on Stack Overflow, for example: https://stackoverflow.com/questions/68412439/info-could-not-find-files-for-the-given-patterns-error (If I'm wrong and you can share in a reproducible environment such as a Colab notebook, please share here and we can reopen this issue!) |
@abidlabs The thing is that this logging message only occurs after upgrading to gradio 5.6.0. Running on gradio 4.44.1 I get nothing. That leads me to believe that the issue is at least partially due to some changes you have implemented. Did you try and test this on windows? I see that I am not the only one getting this logging message. For example, see here: #9809 |
@yvrjsharma could you see if you can reproduce this issue on Windows? |
@abidlabs fyi I have tested now on linux (Ubuntu 22.04) and the INFO message indeed does not show up there. |
Ok reopening while we investigate |
Describe the bug
I noticed that
INFO: Could not find files for the given pattern(s).
is printed to the console whenever starting a gradio application. What is really strange is that this log message is still printed even when I disable python logging, so it seems the message is not being emitted by python code. It is not too big of a deal but it is a bit annoying. Also, I am not sure whether this message can be safely ignored or not (I assume it can since it is has log level INFO).Have you searched existing issues? 🔎
Reproduction
Screenshot
No response
Logs
No response
System Info
Severity
I can work around it
The text was updated successfully, but these errors were encountered: