-
Notifications
You must be signed in to change notification settings - Fork 1
Implement fetching by doi and custom hashes #61
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
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
710500e
initial implementation of zenodo fetching and custom hash checking
j-wags a1d0800
format and clean up
j-wags 68524b6
fill out docstring
j-wags ff6fd70
Create custom exception for file hash comparison failures and test
j-wags e064711
beef up docstrings and add tests
j-wags f9856db
cosmetic commit to kick ci
j-wags 57f222e
remove dependency on openff-utilities
j-wags 9522d57
remove redundant typing from docstring
j-wags f560c1f
fix return type
j-wags c6eb311
don't define unnecessary variable check_hash
j-wags 1d67899
infer sandbox-ness by checking doi prefix
j-wags 4c00163
avoid duplicating downloading and hash checking code
j-wags 4389a51
clarify where zenodo record came from
j-wags d5eb021
black
j-wags File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
This record must be sand-box only? This is my first Google result, which seems unlikely to be what you actually want to point to: https://zenodo.org/records/14335473
A comment or note about where this lives and how the hash was generated would be useful for future developers, I don't think anything else would be necessary here