Skip to content

handle unparseable stack trace better#24

Merged
jduthon merged 2 commits into
mainfrom
dev/avoid-throwing-if-stack-trace-not-parseable
Mar 5, 2026
Merged

handle unparseable stack trace better#24
jduthon merged 2 commits into
mainfrom
dev/avoid-throwing-if-stack-trace-not-parseable

Conversation

@jduthon

@jduthon jduthon commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

We are receiving rollbar errors caused by unhandled promise rejections originating from the library.

The issue seems to be some errors we are sending in do not have a stack trace (or at least a stack trace considered valid from the perspective of the error-stack-parser library, so we receive this error.

This is not ideal as it adds unactionnable noise and we don't know what error we sent in caused the problem.

This PR proposes to avoid throwing errors and letting the errors be reported with empty stack frames.

Changes:

  • Avoid throwing if the stack trace isn't parseable

@jduthon
jduthon marked this pull request as ready for review March 4, 2026 06:58
@jduthon
jduthon requested a review from mangs as a code owner March 4, 2026 06:58
@jduthon jduthon changed the title adds failing test for unparseable stack trace handle unparseable stack trace better Mar 4, 2026

@mangs mangs left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the catch, looks good

@jduthon
jduthon merged commit 9e6bca3 into main Mar 5, 2026
4 checks passed
@jduthon
jduthon deleted the dev/avoid-throwing-if-stack-trace-not-parseable branch March 5, 2026 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants