Skip to content
This repository was archived by the owner on Mar 6, 2026. It is now read-only.

fix: remove default timeout - #974

Merged
gcf-merge-on-green[bot] merged 2 commits into
mainfrom
issue970-default-timeout
Sep 21, 2021
Merged

fix: remove default timeout#974
gcf-merge-on-green[bot] merged 2 commits into
mainfrom
issue970-default-timeout

Conversation

@tswast

Copy link
Copy Markdown
Contributor

Internal folks, see: go/microgenerator-retries

"Methods will not hedge by default." (emphasis mine)

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes#970 🦕

Internal folks, see: go/microgenerator-retries "Methods will **not** hedge by default." (emphasis mine)
@tswast
tswast requested review from a team and stephaniewang526September 17, 2021 16:46
@google-clagoogle-claBot added the cla: yes This human has signed the Contributor License Agreement. label Sep 17, 2021
@product-auto-labelproduct-auto-labelBot added the api: bigquery Issues related to the googleapis/python-bigquery API. label Sep 17, 2021

@plamutplamut left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Has this been confirmed internally as the root cause for the issue the user was facing?

The code change itself looks good.

@tswast

Copy link
Copy Markdown
ContributorAuthor

SRE and API core teams recommends not setting default timeout. Client should still be able to set timeouts in the case when an operation needs to finish within a certain time or else fail.

@tswast

Copy link
Copy Markdown
ContributorAuthor

In the internal go/microgenerator-retries document, default timeouts + retrying on timeout error is defined as a form of hedging, which is not supposed to happen in our clients.

@plamut

Copy link
Copy Markdown
Contributor

Thanks for elaborating, let's merge it then.

@plamutplamut added automerge Merge the pull request once unit tests and other checks pass. kokoro:force-run Add this label to force Kokoro to re-run the tests. labels Sep 21, 2021
@gcf-merge-on-green
gcf-merge-on-greenBot merged commit 1cef0d4 into mainSep 21, 2021
@gcf-merge-on-green
gcf-merge-on-greenBot deleted the issue970-default-timeout branch September 21, 2021 07:18
@gcf-merge-on-greengcf-merge-on-greenBot removed the automerge Merge the pull request once unit tests and other checks pass. label Sep 21, 2021
abdelmegahedgoogle pushed a commit to abdelmegahedgoogle/python-bigquery that referenced this pull request Apr 17, 2023
Internal folks, see: go/microgenerator-retries
> "Methods will **not** hedge by default." (emphasis mine)
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
- [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/python-bigquery/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
- [ ] Ensure the tests and linter pass
- [ ] Code coverage does not decrease (if any source code was changed)
- [ ] Appropriate docs were updated (if necessary)
Fixesgoogleapis#970 🦕
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

api: bigqueryIssues related to the googleapis/python-bigquery API.cla: yesThis human has signed the Contributor License Agreement.kokoro:force-runAdd this label to force Kokoro to re-run the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Python to construct CASE WHEN update SQL statement

2 participants

@tswast@plamut