-
Notifications
You must be signed in to change notification settings - Fork 12
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
Suggestion: safe precache #15
Comments
What is bad with crash? |
I think its wrong if plugin crashes server. Typical example: you are testing plugin locally, works fine, then you uploading it to dedicated server and server crashed. You need to enable condebug and check what happened, then you like "oh crap, i forgot to upload a model!" |
So, we can solve this problem by automatically forced crash log, isn't it?
And ... you didn't see that, because you just installed the plugin and forgot about it. This also is a problem, plugin crashes should be more noticeable, server crash is very noticeable, error messages in console aren't noticeable. Yeah server crash isn't the best way, but I don't know about the other noticeable ways. |
Notification to front menu that some plugin is crashed? |
Description
Check if file exists before precache, so server wont crash if user forgot to put resource in folder. But we need to stop plugin if resource not precached(SetFailState)
Other Comments
The text was updated successfully, but these errors were encountered: