Only log fatal stack trace once in user log #4856
Merged
Conversation
This file contains 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
jakewins
force-pushed
the
2.3-dontlogstacktracethrice
branch
4 times, most recently
from
ef36a7d
to
06f5716
Compare
jakewins
force-pushed
the
2.3-dontlogstacktracethrice
branch
from
06f5716
to
345623f
Compare
technige
pushed a commit
that referenced
this pull request
Jul 1, 2015
Only log fatal stack trace once in user log
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.
Currently we print out a stack trace twice whenever a fatal error occurs in GAP. This cuts it down to one stack trace.