Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Proper servant-server exception handling for warp/wai #1192
I spent some time reading through issue #309 and the associated discussions in yesodweb/wai#496 and PR #954 about how
The unfortunate side effect of this behavior is that any uncaught exceptions within a Servant application will not be registered by any
As far as I can tell, the solution proposed in #309 around deeply evaluating
The machinery for forcing evaluation, catching exceptions, and generating correct
I'm opening a new issue since it seems as if the old ones have languished a bit, and the strategies for handling this problem outlined in them don't appear to actually address the core issue here.
Does anyone have thoughts on what a good architecture for this might look like?
Perhaps some pointers towards code paths within Servant that would allow us to implement the correct behavior, even just as an opt-in for users who want to ensure that middleware operates as-expected?