Skip to content

Conversation

timfish
Copy link
Collaborator

@timfish timfish commented Aug 27, 2024

This is to replace #13418 because I couldn't push to that fork. Thanks to @Bruno-DaSilva

Closes #13416.

We ignore debugger call stacks in the worker that don't match the original error's call stack.

@timfish timfish changed the title Timfish/local variables rethrow fix(node): ignore error rethrows in local variables integration Aug 27, 2024

This comment was marked as off-topic.

@timfish
Copy link
Collaborator Author

timfish commented Aug 27, 2024

The tests that are failing in CI are passing locally 🤦🏻‍♂️. It looks like in CI there are no variables attached to frames at all.

@Bruno-DaSilva
Copy link

Just thinking out loud because I ran into this again in my local as I was testing #13501 -- if the work we're doing in #13501 goes through, a really easy check is to see if the local vars were already captured on the error (either check LOCAL_VARIABLES_KEY or a separate boolean flag on the error object). If so -> skip doing the local vars again.

Overall the new approach is a very nice simplification 👏

@timfish timfish closed this Sep 10, 2024
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.

LocalVariables integration - re-thrown errors can completely mess up frame variables

2 participants