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.
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
bug-1881575: support storing crashes in gcs #977
bug-1881575: support storing crashes in gcs #977
Changes from 1 commit
b2798c3
2d7b1bd
d66f6be
deebf64
c666425
85da340
eecba85
5054fd5
21fd732
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
unlike for pubsub in #974 (comment) the default retry and timeout behavior for google-cloud-storage is better defined. we use two network methods in this class:
Client.get_bucket
andBlob.upload_from_string
, both of which have a default timeout of 60 seconds.Blob.upload_from_string
is expected not to retry because the client assumes it is not an idempotent action.Client.get_bucket
may retry and I think that's fine given there is a default timeout set, and a default retry timeout of 120 seconds. Overall a single file upload is bounded to (bucket retry timeout)+(bucket rpc timeout)+(blob upload rpc timeout) => 120+60+60 => 240 seconds.tl;dr I think this client sets sane defaults for retry and timeout, and we shouldn't mess with them unless/until we see an issue.