Skip to content
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

Make debugging under WSGI easier by allowing exceptions through #562

Closed
dataflake opened this issue Apr 26, 2019 · 1 comment

Comments

@dataflake
Copy link
Member

commented Apr 26, 2019

Right now if you have blanket exception views registered or if you have a standard_html_error (also a blanket exception view) all exceptions will stop there. This is fine and expected in production, but inconvenient for developers:

  • errors are masked in the browser unless the error view exposes the traceback; which would be unusual because that's an information leak
  • you cannot use debugging middleware like the nifty werkzeug debugger because the exceptions never get there
  • potentially helpful waitress settings like expose_tracebacks become meaningless because, again, the exception never gets there

I propose to change the behavior for debug_mode. If an instance is running in debug mode with bin/runwsgi -d ... or, in the case of plone.recipe.zope2instance, bin/zopeinstance fg, to allow exceptions to propagate and not look for/execute configured exception views.

@d-maurer

This comment has been minimized.

Copy link
Contributor

commented Apr 26, 2019

@icemac icemac moved this from To do to In progress in Zope 4 final release May 2, 2019

Zope 4 final release automation moved this from In progress to Done May 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
2 participants
You can’t perform that action at this time.