-
Notifications
You must be signed in to change notification settings - Fork 3
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
[WIP] Error handling #132
base: main
Are you sure you want to change the base?
[WIP] Error handling #132
Conversation
TODO: TESTING config setting isn't applying as expected
TODO: TESTING config setting isn't applying as expected
1c681c9
to
dcf8bc3
Compare
docker-compose.dev.yml
Outdated
@@ -21,7 +21,9 @@ services: | |||
- "USAON_VTA_LOGIN_DISABLED=true" | |||
# Use a local file DB instead of a remote one: | |||
- "USAON_VTA_DB_SQLITE=true" | |||
# Enable the in-browser debugger: | |||
# Disable error handlers and allow exceptions to propagate: | |||
- "USAON_VTA_TESTING=True" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably be lower-case true
for consistency
@rmarow this is in a good place for you to pick it up. The general behavior works but the switch to disable it for development doesn't. Looking to the future, I think we should not rely on this error page as a catch-all; we should catch errors that we expect and deliver them to users in a more user-friendly way, like flashing, so they don't get taken out of what they were doing. But some errors we won't expect until they happen, and this page can be our safety net. |
35f3e6f
to
b8cff54
Compare
We need some environment variable that can be set to disable the error-handling and allow exceptions to propagate fully so (a) we can see the traceback without going to the logs, and (b) use the browser debugger. I set that envvar up, but it doesn't work as I expected. Some investigation needs to be done there.
resolves #73