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 the managing of the session dictionary when you have nested wrappers #10345

Open
wants to merge 1 commit into
base: stable/20240723
Choose a base branch
from

Conversation

jimingham
Copy link

From (llvm#132846)

Since the inner wrapper call might have removed one of the entries from the global dict that the outer wrapper ALSO was going to delete, make sure that we check that the key is still in the global dict before trying to act on it.

(cherry picked from commit 8704635)

@jimingham jimingham requested a review from a team as a code owner March 25, 2025 18:51
@jimingham jimingham requested a review from JDevlieghere March 25, 2025 18:51
@jimingham
Copy link
Author

@swift-ci please test

@jimingham
Copy link
Author

The two failing checks lead nowhere. Let's try this again.

@jimingham
Copy link
Author

@swift-ci please test macOS Windows

@jimingham
Copy link
Author

@swift-ci please test

@jimingham
Copy link
Author

One test failure is that the SBThread.stop_info_data was not found. I'll try regenerating the python bindings to see if that fixes that one. The other is a swift test failure that doesn't look related.

…ers (llvm#132846)

Since the inner wrapper call might have removed one of the entries from
the global dict that the outer wrapper ALSO was going to delete, make
sure that we check that the key is still in the global dict before
trying to act on it.

(cherry picked from commit 8704635)
@jimingham jimingham force-pushed the swiftlang-python-callbacks branch from bb1370a to 91be248 Compare April 1, 2025 23:39
@jimingham
Copy link
Author

I had made the original cherry-pick against stable/20240723 at a point when there was an unrelated failing test still in the branch. That was why I was getting the stop_reason_data not found issue. Rebasing the patch to a newer source base should fix that failure.

@jimingham
Copy link
Author

@swift-ci please test

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.

2 participants