Dispose related readers in GroupBySplitQueryingEnumerable #36484
+32
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndriySvyryd
approved these changes
Aug 1, 2025
roji
added a commit
to roji/efcore
that referenced
this pull request
Aug 2, 2025
Fixes dotnet#34280 (cherry picked from commit 08f094b)
roji
added a commit
to roji/efcore
that referenced
this pull request
Aug 2, 2025
Fixes dotnet#34280 (cherry picked from commit 08f094b)
roji
added a commit
to roji/efcore
that referenced
this pull request
Aug 2, 2025
Fixes dotnet#34280 (cherry picked from commit 08f094b)
|
cc @artl93 |
roji
added a commit
that referenced
this pull request
Aug 4, 2025
roji
added a commit
that referenced
this pull request
Aug 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding test coverage here is quite difficult/impractical - the bug is that a certain internal resource (DbDataReader) doesn't get disposed, which isn't something visible we can check. In any case, the fix is quite trivial and follows the same pattern as for the very similar SplitQueryingEnumerable (non-GroupBy).
Fixes #34280