kgo: fix cancellation of a fetch in manageFetchConcurrency #921
+3
−2
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.
I discovered a "bug" in the code responsible for handling the cancellation of a fetch request. Fortunately, it doesn’t seem to cause any immediate issues (if I’ve correctly understood the relationship between
manageFetchConcurrency
andfetchLoop
). However I think it’s better to fix it now to prevent potential problems in the future when changes are made.In this snippet, instead of deleting the
i
-th element, the last element is being removed:I also attempted to write a test to cover this case, but it would require a significant redesign of
manageFetchConcurrency
so I’ve set this idea aside.