Skip to content

Test if closing explicitly solves recursive lock issues #13304

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Feb 5, 2024
Merged

Test if closing explicitly solves recursive lock issues #13304

merged 1 commit into from
Feb 5, 2024

Conversation

danieldk
Copy link
Contributor

@danieldk danieldk commented Feb 5, 2024

Description

Cherry-pick from main.

Types of change

Checklist

  • I confirm that I have the right to submit this contribution under the project's MIT license.
  • I ran the tests, and all new and existing tests passed.
  • My changes don't require a change to the documentation, or if they do, I've added all required information.

@danieldk danieldk added bug Bugs and behaviour differing from documentation feat / pipeline Feature: Processing pipeline and components labels Feb 5, 2024
@danieldk danieldk merged commit e1249d3 into explosion:master Feb 5, 2024
@danieldk danieldk deleted the maintenance/cherry-pick-concurrency-fix branch February 5, 2024 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
bug Bugs and behaviour differing from documentation feat / pipeline Feature: Processing pipeline and components
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@danieldk