-
-
Notifications
You must be signed in to change notification settings - Fork 199
Change debug trace limit in makeAnEducatedGuessIfTheExceptionMaybeWasHandled method
#622
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
Change debug trace limit in makeAnEducatedGuessIfTheExceptionMaybeWasHandled method
#622
Conversation
cleptric
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the current default is very reasonable.
Can you provide us with some concrete example of where this would not work?
|
I don't think this is an individual case. |
You are the first to report this, so unless we have a lot more people chip in, it might be. In a "normal" Laravel application we expect the stack to be around 5-6 long before hitting the report helper frame so you are definitly doing a lot of indirection. Regardless, we limit the amout of stack frames to prevent doing work that is not needed, Sentry threads a fine line between reporting accurate errors and being performant enought to not cause more problems than it's reporting. That said, I'd be willing to bump it to 20 because I can see 10 might be a little on the thin side, but making it unbounded is not a good idea since not all errors go through report and the loop is not "free" especially with your example where you have 80+ stackframes :) 20 seems to also cover your case and then some, sounds good? |
|
Sure, I will change the limit count to 20. |
f4a0adc to
2600663
Compare
makeAnEducatedGuessIfTheExceptionMaybeWasHandled methodmakeAnEducatedGuessIfTheExceptionMaybeWasHandled method
stayallive
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
2600663 to
764c5df
Compare
|
Hi @cleptric, Is there any plan to release a new tag recently? |
|
@kayw-geek We'll get something out this week. |
Thanks! |
|
Thanks, I see it! |


The current method to limiting the call stack is not suitable for all users of the Sentry SDK, for example, some users have added additional logic based on Sentry, which can cause the call stack to exceed the limit and result in an unexpected unhandled flag.