8000 fix: Don't use event.stacktrace by untitaker · Pull Request #112 · getsentry/sentry-python · GitHub
[go: up one dir, main page]

Skip to content

fix: Don't use event.stacktrace #112

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

Merged
merged 1 commit into from
Oct 9, 2018
Merged

Conversation

untitaker
Copy link
Member

No description provided.

@untitaker untitaker requested a review from bruno-garcia October 9, 2018 07:56
@codecov-io
Copy link
codecov-io commented Oct 9, 2018

Codecov Report

Merging #112 into master will decrease coverage by 0.51%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #112      +/-   ##
==========================================
- Coverage   68.76%   68.25%   -0.52%     
==========================================
  Files          25       25              
  Lines        2347     2353       +6     
  Branches      319      319              
==========================================
- Hits         1614     1606       -8     
- Misses        620      632      +12     
- Partials      113      115       +2
Impacted Files Coverage Δ
sentry_sdk/client.py 58.27% <100%> (-2.42%) ⬇️
sentry_sdk/utils.py 67.01% <0%> (-1.66%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5805bff...40636ee. Read the comment docs.

@untitaker untitaker merged commit 8aa0446 into master Oct 9, 2018
@untitaker untitaker deleted the fix/dont-use-event.stacktrace branch October 9, 2018 10:48
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.

3 participants
0