Skip to content

Avoid concurrent access to multibuffer entity iterator #1016

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 1 commit into from
May 26, 2025

Conversation

l-trotta
Copy link
Contributor

As reported in #1003, it appears that the list of Buffers in MultiBufferEntity can be accessed by multiple threads in case of frequent connection exceptions, by calling the functions init() and produceContent() at the same time. This PR introduces a local iterator in init() so that it will not try to call next() on an empty iterable.

@l-trotta l-trotta merged commit c36d6a3 into 7.17 May 26, 2025
4 checks passed
@l-trotta l-trotta deleted the concurrency-error-fix branch May 26, 2025 15:56
l-trotta added a commit that referenced this pull request Jun 24, 2025
l-trotta added a commit that referenced this pull request Jun 24, 2025
l-trotta added a commit that referenced this pull request Jun 24, 2025
l-trotta added a commit that referenced this pull request Jun 24, 2025
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.

1 participant