This repository was archived by the owner on Oct 23, 2023. It is now read-only.
Invert the direction of the auto-log traces so they match those given by Exceptions and culprit determination works properly. #12
Merged
dcramer merged 1 commit intogetsentry:masterfrom Oct 22, 2011
ahknight:master
Merged
Invert the direction of the auto-log traces so they match those given by Exceptions and culprit determination works properly. #12dcramer merged 1 commit intogetsentry:masterfrom ahknight:master
dcramer merged 1 commit intogetsentry:masterfrom
ahknight:master
Conversation
… by Exceptions and culprit determination works properly.
Closed
dcramer
added a commit
that referenced
this pull request
Oct 22, 2011
Invert the direction of the auto-log traces so they match those given by Exceptions and culprit determination works properly.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
When using SENTRY_AUTO_LOG_STACKS the resulting traces in Sentry are bottom-to-top whereas the traces from an exception are top-to-bottom. This is not only very confusing, but it causes Sentry to identify the WSGI handler as the cause of all errors in logging statements.