Skip to content

Revert "Implement PEP3134 to discover underlying problems with python 3 (#355)" #371

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

Merged
merged 4 commits into from
Dec 27, 2022

Conversation

michael-k
Copy link
Contributor

Issue #, if available: #370

Description of changes: This reverts commit 4660169 (PR #355)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@michael-k michael-k requested a review from a team as a code owner November 29, 2022 11:29
Copy link
Contributor

@carolabadeer carolabadeer left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for the context on the previous PR! It is definitely much more helpful to be able to see the full stack trace.

@carolabadeer
Copy link
Contributor

Before closing this PR, I was curious if there is another workaround to fix the issues with python3 mentioned in the previous PR #355? I think it would be beneficial to implement that, unless it will always result in the X-Ray portion of the stack trace to be omitted

@michael-k
Copy link
Contributor Author

another workaround

PR #355 is not a workaround or solution. I don't know what caused sentry being hidden from the stacktrace. I don't have a way to reproduce this.

@carolabadeer carolabadeer merged commit 9db6571 into aws:master Dec 27, 2022
@michael-k michael-k deleted the revert-355 branch January 10, 2023 10:28
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.

3 participants