Skip to content

Conversation

@stephenplusplus
Copy link
Contributor

Picking up from #299, where we're implementing integrity checks for uploads.

@stephenplusplus stephenplusplus force-pushed the spp--storage-download-integrity branch 2 times, most recently from 64aa8dc to b4f3d8d Compare November 24, 2014 17:33
@ryanseys
Copy link
Contributor

Does this depend on #299 being merged first?

On Monday, November 24, 2014, Stephen Sawchuk [email protected]
wrote:

Picking up from #299
#299, where

we're implementing integrity checks for uploads.

You can merge this Pull Request by running

git pull https://github.com/stephenplusplus/gcloud-node spp--storage-download-integrity

Or view, comment on, or merge it at:

#310
Commit Summary

  • storage: download integrity check

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#310.

@stephenplusplus
Copy link
Contributor Author

No, sir.

This comment was marked as spam.

@stephenplusplus stephenplusplus force-pushed the spp--storage-download-integrity branch from 6021be0 to 9367598 Compare November 24, 2014 18:26

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

@stephenplusplus stephenplusplus force-pushed the spp--storage-download-integrity branch from 9eaef75 to 14b48b5 Compare November 25, 2014 20:01
@stephenplusplus
Copy link
Contributor Author

@ryanseys going to re-answer your earlier question. It probably makes sense to wait for #299 to go before merging this one, since there will be some shared functions I can make use of in this PR that are going to go with that PR.

Left a note to hold off in the description 👍

@stephenplusplus stephenplusplus force-pushed the spp--storage-download-integrity branch from a1b2671 to 3df8817 Compare December 5, 2014 18:50
@stephenplusplus
Copy link
Contributor Author

This one should be ready for another look.

This comment was marked as spam.

This comment was marked as spam.

@ryanseys
Copy link
Contributor

ryanseys commented Dec 8, 2014

I've looked at this. It looks overall good, just a few notes you may wish to address. If you make those small changes and squash, I'll be happy to merge.

@stephenplusplus
Copy link
Contributor Author

Thanks for the review! I squashed and tried to make the docs a little more clear in 88e9eab

@stephenplusplus stephenplusplus force-pushed the spp--storage-download-integrity branch from 9802af2 to c7c6e60 Compare December 10, 2014 17:43
@stephenplusplus
Copy link
Contributor Author

@ryanseys squashed and fixed the logic line you left a comment on. Merging!

stephenplusplus added a commit that referenced this pull request Dec 10, 2014
…tegrity

storage: download integrity check
@stephenplusplus stephenplusplus merged commit 23d399c into googleapis:master Dec 10, 2014
sofisl pushed a commit that referenced this pull request Jan 10, 2023
sofisl pushed a commit that referenced this pull request Jan 24, 2023
sofisl pushed a commit that referenced this pull request Jan 25, 2023
GautamSharda pushed a commit that referenced this pull request Jan 14, 2026
* chore: upgrade to gts 1.0.0

* chore: run `gts fix`

* chore: fix `gts check` errors
GautamSharda pushed a commit that referenced this pull request Jan 20, 2026
* chore: upgrade to gts 1.0.0

* chore: run `gts fix`

* chore: fix `gts check` errors
GautamSharda pushed a commit that referenced this pull request Jan 21, 2026
* chore: upgrade to gts 1.0.0

* chore: run `gts fix`

* chore: fix `gts check` errors
sofisl pushed a commit that referenced this pull request Jan 27, 2026
sofisl pushed a commit that referenced this pull request Jan 27, 2026
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.

3 participants