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.

Sign up for GitHub

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

Jump to bottom

storage: a way to abort a request #600

Closed
gmiroshnykov opened this issue May 15, 2015 · 3 comments
Closed

storage: a way to abort a request #600

gmiroshnykov opened this issue May 15, 2015 · 3 comments
Assignees
@gmiroshnykov
Labels
api: storage Issues related to the Cloud Storage API. type: question Request for information or clarification. Not an issue.
Milestone
Storage Future

Comments

@gmiroshnykov
Copy link

It seems there is no way to abort an upload or download request created by file.createWriteStream() and file.createReadStream() respectively.

Node's native HTTP client has request.abort(), but as far as I can tell the above methods return simple through2 streams and keep the raw HTTP requests / responses hidden.

So is there a way to abort a request in progress?
@jgeewax jgeewax added type: question Request for information or clarification. Not an issue. api: storage Issues related to the Cloud Storage API. labels May 15, 2015
@jgeewax jgeewax added this to the Storage Future milestone May 15, 2015
@ryanseys
Copy link
Contributor

You should be able to destroy the stream with stream.destroy() and assuming that validation is turned on (on by default), the upload/download will fail. Can you try that and let us know how that works?

@gmiroshnykov
Copy link
Author

stream.destroy() seems to work great, thanks!

@ryanseys
Copy link
Contributor

Perfect! Glad we could help! 😄

@sofisl sofisl mentioned this issue Oct 11, 2022
Merged
4 tasks
sofisl pushed a commit that referenced this issue Oct 11, 2022
@gcf-owl-bot
fix: Updating WORKSPACE files to use the newest version of the Typesc…
52770fa 
…ript generator. (#600)

Also removing the explicit generator tag for the IAMPolicy mixin for the kms and pubsub APIS as the generator will now read it from the .yaml file.

PiperOrigin-RevId: 385101839

Source-Link: googleapis/googleapis@80f4042

Source-Link: googleapis/googleapis-gen@d3509d2
sofisl pushed a commit that referenced this issue Oct 11, 2022
@release-please
chore: release 4.2.8 (#601)
752c6b6 
🤖 I have created a release \*beep\* \*boop\*
---
### [4.2.8](https://github.com/googleapis/nodejs-language/compare/v4.2.7...v4.2.8) (2021-07-21)


### Bug Fixes

* Updating WORKSPACE files to use the newest version of the Typescript generator. ([#600](https://github.com/googleapis/nodejs-language/issues/600)) ([9f31d3f](https://github.com/googleapis/nodejs-language/commit/9f31d3f510c1628d610633d4ec749abdf66d73f3))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
@release-please release-please bot mentioned this issue Oct 11, 2022
Closed
sofisl pushed a commit that referenced this issue Oct 13, 2022
@gcf-owl-bot @sofisl
fix: Updating WORKSPACE files to use the newest version of the Typesc…
901abf3 
…ript generator. (#600)

Also removing the explicit generator tag for the IAMPolicy mixin for the kms and pubsub APIS as the generator will now read it from the .yaml file.

PiperOrigin-RevId: 385101839

Source-Link: googleapis/googleapis@80f4042

Source-Link: googleapis/googleapis-gen@d3509d2
sofisl pushed a commit that referenced this issue Oct 13, 2022
@release-please @sofisl
chore: release 4.2.8 (#601)
b560cae 
🤖 I have created a release \*beep\* \*boop\*
---
### [4.2.8](https://github.com/googleapis/nodejs-language/compare/v4.2.7...v4.2.8) (2021-07-21)


### Bug Fixes

* Updating WORKSPACE files to use the newest version of the Typescript generator. ([#600](https://github.com/googleapis/nodejs-language/issues/600)) ([9f31d3f](https://github.com/googleapis/nodejs-language/commit/9f31d3f510c1628d610633d4ec749abdf66d73f3))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
sofisl pushed a commit that referenced this issue Nov 11, 2022
@release-please
chore(main): release 4.1.0 (#600)
1b83e00 
🤖 I have created a release *beep* *boop*
---


## [4.1.0](googleapis/nodejs-dataproc@v4.0.1...v4.1.0) (2022-09-22)


### Features

* Add support for Dataproc metric configuration ([#626](googleapis/nodejs-dataproc#626)) ([79a4958](googleapis/nodejs-dataproc@79a4958))
* Support regapic LRO ([350626e](googleapis/nodejs-dataproc@350626e))


### Bug Fixes

* Allow passing gax instance to client constructor ([#612](googleapis/nodejs-dataproc#612)) ([caba80a](googleapis/nodejs-dataproc@caba80a))
* **deps:** Do not depend on protobufjs ([#607](googleapis/nodejs-dataproc#607)) ([4b62ef6](googleapis/nodejs-dataproc@4b62ef6))
* **deps:** Roll back dependency @google-cloud/dataproc to ^4.0.0 ([#627](googleapis/nodejs-dataproc#627)) ([e1c6d8b](googleapis/nodejs-dataproc@e1c6d8b))
* Do not import the whole google-gax from proto JS ([#1553](https://github.com/googleapis/nodejs-dataproc/issues/1553)) ([#617](googleapis/nodejs-dataproc#617)) ([2e2bea1](googleapis/nodejs-dataproc@2e2bea1))
* Preserve default values in x-goog-request-params header ([#620](googleapis/nodejs-dataproc#620)) ([484a023](googleapis/nodejs-dataproc@484a023))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
@sofisl sofisl mentioned this issue Nov 11, 2022
Merged
4 tasks
sofisl pushed a commit that referenced this issue Nov 17, 2022
@renovate-bot
chore(deps): update dependency @types/sinon to v10 (#600)
6eb1d03
@sofisl sofisl mentioned this issue Nov 17, 2022
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gmiroshnykov gmiroshnykov

Labels
api: storage Issues related to the Cloud Storage API. type: question Request for information or clarification. Not an issue.
Projects
None yet
Milestone
Storage Future
Development

No branches or pull requests
3 participants
@gmiroshnykov @jgeewax @ryanseys