Skip to content
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

Change hash to digest for consistent terminology across runner logs #1991

Merged
merged 1 commit into from
Mar 12, 2025

Conversation

GhadimiR
Copy link
Contributor

With the introduction of digest validation on artifact download, taking this opportunity to change the message printed during upload to use the same terminology.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@GhadimiR GhadimiR requested a review from a team as a code owner March 12, 2025 08:00
@@ -98,7 +98,7 @@ export async function uploadZipToBlobStorage(

hashStream.end()
sha256Hash = hashStream.read() as string
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this apply to the variable names too?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a great question that I'm sure we could spend a lot of time thinking about. My view is that we're using a hashing algorithm, so hashStream is the correct term, the hash stream produces a hash, which can also be referred to as a digest, so we could probably go either way on whether or not to rename sha256hash here.

I'd generally lean towards the minimal change as it intuitively makes sense to me that a hashStream would produce a hash, but I'm open to renaming it if you have a more appropriate name for this variable in mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants