Skip to content

Add BigQuery example to README.md. - #1902

Merged
daspecster merged 2 commits into
googleapis:masterfrom
daspecster:add-bigquery-example-to-readme
Jun 27, 2016
Merged

Add BigQuery example to README.md.#1902
daspecster merged 2 commits into
googleapis:masterfrom
daspecster:add-bigquery-example-to-readme

Conversation

@daspecster

Copy link
Copy Markdown
Contributor

@tseaver there might be a better example to throw in here. If so just let me know and I'll add it.

/cc @dhermes

@googlebotgooglebot added the cla: yes This human has signed the Contributor License Agreement. label Jun 24, 2016
Comment threadREADME.rst
from gcloud import bigquery
client = bigquery.Client()
dataset = client.dataset('dataset_name')
dataset.create() # API request

This comment was marked as spam.

@tseaver

Copy link
Copy Markdown
Contributor

@daspecster similar reminder to close #1899 after merge.

@tseaver

Copy link
Copy Markdown
Contributor

LGTM.

@daspecster
daspecster merged commit dbb05e5 into googleapis:masterJun 27, 2016
@daspecster
daspecster deleted the add-bigquery-example-to-readme branch June 27, 2016 18:27
@tseavertseaver mentioned this pull request Jun 29, 2016
parthea pushed a commit that referenced this pull request Nov 24, 2025
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
parthea pushed a commit that referenced this pull request Mar 2, 2026
Improved error handling in `google/auth/compute_engine/_metadata.py` to
provide more informative error messages when retries are exhausted.
The logic now handles two distinct failure modes:
1. **Connection Errors (Exceptions):**
- Exceptions caught during the request (e.g., connection refused) are
stored in `last_exception`.
- If the retry loop exhausts and `last_exception` is set, a
`TransportError` is raised that chains the original exception. This
preserves the stack trace and specific error type for debugging.
2. **Retryable HTTP Status Codes:**
- If a request completes but returns a retryable status code (e.g., 500,
503), `last_exception` is cleared (set to `None`).
- If the retry loop exhausts due to repeated retryable status codes, a
`TransportError` is raised that includes the `response.status` and the
response body (`error_details`). This ensures the specific server error
message is visible.
This addresses feedback from PR 1637 by ensuring that "Ran out of
retries" scenarios provide the most relevant context: either the
underlying exception or the final HTTP error response.
---
*PR created automatically by Jules for task
[6226991344715693997](https://jules.google.com/task/6226991344715693997)
started by @chalmerlowe*
---------
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
Co-authored-by: Chalmer Lowe <chalmerlowe@google.com>
parthea pushed a commit that referenced this pull request Apr 1, 2026
* feat: support date data type for to_datetime()
* add test preconditions
* fix test
* fix lint
* fix tests
* fix lint
* fix test
* update docstring
* update docstring
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yesThis human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@daspecster@tseaver@googlebot