beginErrorHandlingTransaction called in two contexts with fragile discriminator
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope 3 |
Won't Fix
|
Undecided
|
Unassigned | ||
zope.app.publication |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
We have code in our error reporting utility that records what happened in a request. Then, before getting the exception view, we need to reset our records, so if something goes wrong there, the delineation is clear when we record *that* in our error reporting utility as well.
In zope.app.
We need to leave our "what happened" data structure intact for the first call to beginErrorHandl
Right now, our only choices are to override handleException, which is unappealing because then we would have to copy all of the method's code to insert our logic in the right place; or to override beginErrorHandl
We would prefer to have a documented way to distinguish between the contexts in which beginErrorHandl
tags: | added: tech-debt |
Changed in zope3: | |
status: | New → Won't Fix |
Changed in zope.app.publication: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |