-
Notifications
You must be signed in to change notification settings - Fork 80
Support on-demand content in repair_metadata #848
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fc1102d to
99180e4
Compare
9e27aaf to
04c2e4f
Compare
9875d50 to
925e392
Compare
2b14e83 to
79d7acf
Compare
79d7acf to
b2b74fa
Compare
42e9834 to
0b91e31
Compare
7c3cb5c to
95f6e5f
Compare
gerrod3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work on the logic, the grouping of the packages by name-version and then further grouping by shared url of the RAs looks right (it is definitely a bit complex!)
95f6e5f to
b0b12d9
Compare
b0b12d9 to
308b353
Compare
308b353 to
1cdff86
Compare
ab59d2d to
ecb804f
Compare
ecb804f to
154f96a
Compare
gerrod3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thank you!
This PR extends the
repair_metadataendpoint for repositories to also support on-demand content if the associated remote supports the PyPI json version API.For on-demand content, we expect that:
PythonPackageContentalways has correctnameandversionRemoteArtifactalways has correctsha256Closes #849