-
Notifications
You must be signed in to change notification settings - Fork 177
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
Stopping server instance produces "unclosed file" warning #264
Comments
Please see the section "General Support" at https://pylonsproject.org/community-support.html |
You're on a roll @stevepiercy but I think this one counts more in the issue category than in the question category despite their nicely assuming it's user error. @everdimension Does it shutdown immediately or after a few seconds? In general I don't usually see resource warnings when killing the server but they are notoriously difficult to reproduce/track down. |
Hm, I think I caught it once not stopping immediately (could not restart the server). But I cannot reproduce it. But I see the unclosed file almost every time I interrupt the server with |
This happens to me 100% as well. It shutdowns right away. I'm running in a Raspberry Pi, FYI. I've been looking for a cleanup method where I can call in the signal handler, but I don't see one in init.py or anywhere. |
waitress doesn't have any signal handlers defined and there are no cleanup methods or anything along those lines either, instead it relies on normal interrupts happening to the loop that is running, and which point it waits a little bit (unless there is no request being handled) before shutting the app down. The file it's warning about is an |
@everdimension, i face the same problem, did you find a solution ? |
Hi! Thanks you for making this library.
I have code like this in my
main.py
file:I run file from the terminal like this:
Everything works fine. Then I want to shutdown the server. I press command + c
I see this warning:
I'm not sure if this is intended. "Unclosed file" doesn't sound that good. Am I doing something wrong when I stop the server or is this intended behavior?
Thank you.
The text was updated successfully, but these errors were encountered: