fix(api): populate items_count in list_operations#1164
Merged
nicoloboschi merged 1 commit intomainfrom Apr 20, 2026
Merged
Conversation
list_operations was hardcoding items_count to 0 instead of reading it from result_metadata, which is already fetched by the query and correctly populated during retain/batch_retain submission. Fixes #1146
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
list_operationswas hardcodingitems_count: 0for every operation instead of reading it fromresult_metadata, which is already fetched by the query and correctly populated during retain/batch_retain submissionresult_metadataand extractsitems_count, falling back to0for operation types that don't store it (e.g. consolidation)Fixes #1146
Test plan
test_async_batch_retain.pytests pass (13/13)