-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
First run of template project fails with WatchfilesRustInternalError #2785
Comments
Thanks for reporting - so running it again solves the issue? Seems like some misconfiguration in our uvicorn on Windows - we shouldn't be watching the Perhaps we need to explicitly set the watch dir. If anyone has any ideas, would welcome a fix here |
Correct, the exception only happens on the first "Reflex run". |
Just saw the exception happen again but this time after it had been running a while. So it looks like while this exception happens every time when executing "reflex run" for the very first time on a project, it can also very rarely happen in other cases. |
Weird, but I am having the same error quite often on the latest version (0.5.9):
|
Ok, its not exactly the reflex problem. It can only be solved in uvicorn. See the class definition there:
Even if you set excluded folders, it does not exclude them from watcher: it just ignores them. So if watcher fails, it fails. And for some reason it watches all files in the directory, even if you told it only to watch the code folder. It quite implicit, and bad approach IMHO. |
The problem is listed in uvicorn repository: encode/uvicorn#1785 |
Describe the bug
WatchfilesRustInternalError exception occurs immediately after the first init/run of the sidebar template.
Exception does not occur on subsequent runs
The exception doesn't stop the app from working. I.e. I can view the app at http://localhost:3000/
To Reproduce
Steps to reproduce the behavior:
EXCEPTION:
Expected behavior
No exception
Screenshots
If applicable, add screenshots to help explain your problem.
Specifics (please complete the following information):
Additional context
Exception Stack.txt
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: