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(node): Local variables skipped after Promise #11234

Merged
merged 1 commit into from
Mar 22, 2024

Conversation

timfish
Copy link
Collaborator

@timfish timfish commented Mar 21, 2024

Closes #11194

The debugger call stack does not include the new Promise frames that are parsed from error.stack. This means that when we go through the frames to apply the local variables, the frames don't match up and we bail.

This PR ignores those frames when matching functions in the frames.

This comment was marked as outdated.

@Lms24 Lms24 merged commit 28db511 into develop Mar 22, 2024
63 checks passed
@Lms24 Lms24 deleted the timfish/fix/async-local-variables branch March 22, 2024 13:03
@Lms24 Lms24 mentioned this pull request Mar 22, 2024
AbhiPrasad pushed a commit that referenced this pull request Mar 22, 2024
c298lee pushed a commit that referenced this pull request Mar 22, 2024
The debugger call stack does not include the `new Promise` frames that
are parsed from `error.stack`. This means that when we go through the
frames to apply the local variables, the frames don't match up and we
bail.

This patch ignores those frames when matching functions in the frames.
c298lee pushed a commit that referenced this pull request Mar 23, 2024
The debugger call stack does not include the `new Promise` frames that
are parsed from `error.stack`. This means that when we go through the
frames to apply the local variables, the frames don't match up and we
bail.

This patch ignores those frames when matching functions in the frames.
cadesalaberry pushed a commit to cadesalaberry/sentry-javascript that referenced this pull request Apr 19, 2024
The debugger call stack does not include the `new Promise` frames that
are parsed from `error.stack`. This means that when we go through the
frames to apply the local variables, the frames don't match up and we
bail.

This patch ignores those frames when matching functions in the frames.
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.

includeLocalVariables fails to capture local variables across sync/async boundaries
2 participants