-
-
Notifications
You must be signed in to change notification settings - Fork 759
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
Feature Request: reload after error #425
Comments
Slightly depends on what you mean. Incidentally, how is the subprocess crashing? Python exceptions from the child application should just end up logging as errors. Is it something more serious than that? |
It reliably crashes from syntax errors in my code. This would be a pure development feature, as the whole 'reload after file change' logic should have nothing to do with production code in any way. When the subprocess crashes, the reloading after file changes is stopped, you have an explicit check In case anyone else finds this discussion, I monkeypatched it for my use case:
|
Ah right, I was misunderstanding slightly - I though you were talking about runtime errors in a deployed version, rather than syntax errors during development (which yes, will just quit the server). |
Can this issue be reopened? I am using |
Sure thing, let's put it on the list. |
+1 for this. |
Any update on this? |
Folks, if there's an update on a ticket, there'll be an update on the ticket. Please don't do issue-spam. |
It appears that this issue no longer exists as of Uvicorn 0.11. |
This is still an issue for me |
Still an issue for me in 0.16.0. This makes it unusable for me because I like to have autosave enabled in my code editor, so as I write code it restarts and crashes. |
It's not the same issue, but a fix is already provided on #1313 |
Even after the subprocess crashes, uvicorn should still reload, i.e. restart the process after the next file change. Maybe with an additional command line flag (--reload-after-error).
Not having to restart the server after every syntax error would help during development.
The text was updated successfully, but these errors were encountered: