Fix size computing for packages with /latest route #1693
Merged
Conversation
This file contains 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
sajjaphani
changed the title
mwrock
approved these changes
Jan 12, 2022
Signed-off-by: Phani Sajja <psajja@progress.com>
sajjaphani
force-pushed
the
psajja/fix-fetching-size
branch
from
15de465
to
457d8c3
Compare
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.
We can get the package metadata with the /latest route with the omission of the version and or release options.
This PR fixes getting package HART size as part of package metadata in those situations.
It also updates a few functional tests to check the size attribute in the response JSON.
Signed-off-by: Phani Sajja psajja@progress.com