Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix for occasional errors likely due to the use of the remove() method within a lambda expression inside the thenAccept method. This lambda expression is executed asynchronously, which means that the iterator may not be in a consistent state when remove() is called.
Since thenAccept runs asynchronously, the iteration over stackedBlocks may continue before the lambda is executed, leading to an inconsistent state when it.remove() is called.
To fix this issue, you should collect the elements to be removed in a separate collection and remove them after the iteration is complete.
In this version, the elements to be removed are collected in a separate
List<Location> toRemove
, which is synchronized to handle concurrent access. After the iteration is complete and all asynchronous tasks have been executed, the collected elements are removed from stackedBlocks.