Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix line/column/url extraction from some eval frames #907

Merged
merged 2 commits into from
Mar 28, 2017

Conversation

benvinegar
Copy link
Contributor

@benvinegar benvinegar commented Mar 24, 2017

This mirrors the behavior in stacktracejs/error-stack-parser (from where I borrowed the tests). The eval "source" line/column is thrown out, and the invocation line (and column, on Chrome) is used instead.

Before we were pulling out URLs that were unusable, so we weren't fetching the source content associated with these eval frames anyways. There is a question of whether Sentry itself should have an "is_eval" meta attribute on frames, or perhaps just a "meta" attribute where we can note in the UI what's going on (cc @mitsuhiko).

cc @LewisJEllis @MaxBittker

@benvinegar benvinegar changed the title Initial work on fixing eval frame regexes [WIP] Fix line/column/url extraction from some eval frames Mar 26, 2017
@benvinegar benvinegar requested a review from LewisJEllis March 26, 2017 16:39
@benvinegar benvinegar merged commit cb5e0df into master Mar 28, 2017
@benvinegar benvinegar deleted the fix-eval-frames branch March 28, 2017 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants