python traceback locals cut off after a variable fails repr

[agroszer]

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Version

9.1.2

Steps to Reproduce

python-pseudo code:

def test():
    a = 1
    b = ObjectThatRaisesOnRepr()
    c = 3
    1 / 0  # raise, cause a sentry

Expected Result

locals list of:

a           1
c           3

or even better, ideally

a           1
b           <variable failed repr>
c           3

Actual Result

locals list of:

a           1

[getsentry-release]

Routing to @getsentry/team-web-backend for triage. ⏲️

[sl0thentr0py]

thx for reporting @agroszer, we'll take a look eventually but PRs always welcome!

[github-actions[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[szokeasaurusrex]

@agroszer I attempted to reproduce this bug in the current latest version of the Python SDK, and it appears to be working as expected, with "<broken repr>" being output for the variable whose __repr__ function fails. So, I am closing this issue.

If you continue to experience the problem when using the latest Python SDK, please reopen the issue and provide a code snippet I can run to observe the same result that you are. Any additional information about your configuration that you are able to share would help me to reproduce the bug.