Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

fix: add minimum timeout to getQueryResults API requests#444

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

@tswast
Copy link
Contributor

Since successful responses can still take a long time to download, have
a minimum timeout which should accomodate 99.9%+ of responses.

I figure it's more important thatany timeout is set if desired than
it is that the specific timeout is used. This is especially true in
cases where a short timeout is requested for the purposes of a progress
bar. Making forward progress is more important than the progress bar
update frequency.

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 abug/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#438 🦕

Since successful responses can still take a long time to download, havea minimum timeout which should accomodate 99.9%+ of responses.I figure it's more important that *any* timeout is set if desired thanit is that the specific timeout is used.  This is especially true incases where a short timeout is requested for the purposes of a progressbar. Making forward progress is more important than the progress barupdate frequency.
@tswasttswast requested review froma team andshollyman and removed request fora teamDecember 21, 2020 18:12
@google-clagoogle-clabot added the cla: yesThis human has signed the Contributor License Agreement. labelDec 21, 2020
@product-auto-labelproduct-auto-labelbot added the api: bigqueryIssues related to the googleapis/python-bigquery API. labelDec 21, 2020
Copy link
Contributor

@shollymanshollyman left a comment

Choose a reason for hiding this comment

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

one minor question about documenting behavior.

}

iftimeoutisnotNone:
timeout=max(timeout,_MIN_GET_QUERY_RESULTS_TIMEOUT)
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we document this in the methods? e.g. timeout less than the _MIN_GET_QUERY_RESULTS_TIMEOUT are ignored?

tswast reacted with thumbs up emoji
@tswasttswast merged commit015a73e intogoogleapis:masterJan 8, 2021
@tswasttswast deleted the issue438-getQueryResults-timeout branchJanuary 8, 2021 22:57
shollyman pushed a commit to shollyman/python-bigquery that referenced this pull requestFeb 12, 2021
…rm/python-docs-samples#444)Put them in their own directory, since they duplicate the content fromthe existing samples that use the generated libraries.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@shollymanshollymanshollyman approved these changes

@steffnaysteffnayAwaiting requested review from steffnay

Assignees

No one assigned

Labels

api: bigqueryIssues related to the googleapis/python-bigquery API.cla: yesThis human has signed the Contributor License Agreement.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

TQDM progress bar causes ReadTimeout error

2 participants

@tswast@shollyman

[8]ページ先頭

©2009-2025 Movatter.jp