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.
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
add tests for some solver behaviour known issues #197
add tests for some solver behaviour known issues #197
Changes from all commits
8e8e5be
f08beb3
4efb504
bfcabbf
1c2b07e
ccef7a9
bff65c1
a5a8b38
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@dhirschfeld - I think you might want to see this script, given your message at Quansight-Labs/czi-conda-forge-mgmt#5 (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.
Nice, especially the correct handling of the patches 🚀
One minor quibble would be that the timestamp in question is the build time (IIUC) and not the time that the package was uploaded to the package registry (i.e. not the time that it was available for users to download/install). Though, with automated build infrastructure the build time is probably a close-enough proxy for the
uploaded_timestamp
.The only other observation is that this is an enormous amount of effort (development/CPU) to go to to support something as simple as
...if the package information was stored in a database rather than a JSON blob.
i.e. I think the JSON blob format is much more complex and must be much less performant than storing the information in a proper database.
That's just my intuition, and might well be wrong, but is why I was interested in the other PR.