Skip to content

Release the GIL before any call to async methods #123

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 2 commits into from
May 25, 2023

Conversation

merlimat
Copy link
Contributor

Fix #122

When call an async method on Pulsar C++ client, we need to be releasing the GIL to avoid a deadlock between that and the producer lock.

@merlimat merlimat added the bug Something isn't working label May 24, 2023
@merlimat merlimat added this to the 3.2.0 milestone May 24, 2023
@merlimat merlimat requested a review from BewareMyPower May 24, 2023 20:41
@BewareMyPower BewareMyPower merged commit ce25b36 into apache:main May 25, 2023
@merlimat merlimat deleted the fix-deadlock branch May 25, 2023 00:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deadlock in python client when using send_async with flush
2 participants