Repository navigation
Conversation
Closed
Contributor
Author
|
Closing in favor of catching exceptions in the front-end. In this solution, the error data transferred over to the front-end was the input to the flask exception handler rather than the output, so we did not get the nice werkzueg error pages. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This solution uses the flask
got_request_exceptionmethod to call a block of code before an exception is raised in the Dash backend whendebug=True. In this block of code, we use socket.io (Flask-SocketIO) to emit an 'error' event from the namespace/{prefix}_dash-errorsendpoint which includes error information like the Exception name, message, and traceback.Still need to figure out:
socketio = SocketIO(self.server)break anything in servers which use Dash plus some other Flask plugins?