-
Notifications
You must be signed in to change notification settings - Fork 28
Bugfixes, tests, and tools around checksums #2259
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
} | ||
|
||
// Test behavior when checksum is missing | ||
func TestChecksumMissing(t *testing.T) { |
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.
Each of these new checksum tests is largely a copy-paste-tweak of the others. Instead of using three separate tests, can you create one test that handles a slice of test cases?
- Export checksum type / name information outside the client library. - Add standardized error types and singletons for failure checking. - Do not overwrite checksum mismatch error once it occurs. - Truncate checksum byte array to provided data length.
139d3d5
to
5e99561
Compare
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.
LGTM. I'll add this as a 7.16 patch as well.
This PR improves the checksum functionality:
pelican object stat
that allows CLI users to get a checksum back.Example: