- Notifications
You must be signed in to change notification settings - Fork370
Only enable symfony error handler in debug mode#513
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
acasademont commentedAug 10, 2020
Not so sure about this one, if the server crashes (during the bridge bootstrap, for example) there might be very little info about what happened. Did you run some tests on it? |
jkrzefski commentedAug 10, 2020
No, I did not run any tests on my end. I only looked through the code, spotted this and thought it looked wrong. The travis build seems fine, though. I am totally ok with leaving it the way it was. I would merely like a short explanation on why the error handler is enabled in production. Maybe a comment in the code would be nice, so others don't get confused like I was. |
andig commentedAug 12, 2020
Enable during startup and disable after first client answer sent? |
andig commentedJan 8, 2022
Could you propose what you'd expect? |
I don't know why the Symfony error handler is always enabled. Maybe there is a deeper meaning behind it that I don't see. But if not, I propose to only use
Debugwhen debugging is requested (via config or command option).