-
Notifications
You must be signed in to change notification settings - Fork 161
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
Preserve nicely formatted timeout exception #1187
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-bigquery contributing guide. |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.7.latest 1.7.latest
# Navigate to the new working tree
cd .worktrees/backport-1.7.latest
# Create a new branch
git switch --create backport-1187-to-1.7.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b62ce7469a47de4e1f526fc551817b3e0919ddb2
# Push it to GitHub
git push --set-upstream origin backport-1187-to-1.7.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.7.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-1187-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b62ce7469a47de4e1f526fc551817b3e0919ddb2
# Push it to GitHub
git push --set-upstream origin backport-1187-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest Then, create a pull request where the |
* use dynamic schema in test_grant_access_to.py * use dynamic schema in test_grant_access_to.py * revert setup * Add descriptive error message on query timeout * Add descriptive error message on query timeout (cherry picked from commit b62ce74)
* use dynamic schema in test_grant_access_to.py * use dynamic schema in test_grant_access_to.py * revert setup * Add descriptive error message on query timeout * Add descriptive error message on query timeout (cherry picked from commit b62ce74)
* use dynamic schema in test_grant_access_to.py * use dynamic schema in test_grant_access_to.py * revert setup * Add descriptive error message on query timeout * Add descriptive error message on query timeout (cherry picked from commit b62ce74)
* use dynamic schema in test_grant_access_to.py * use dynamic schema in test_grant_access_to.py * revert setup * Add descriptive error message on query timeout * Add descriptive error message on query timeout (cherry picked from commit b62ce74)
Add descriptive error message on query timeout
It appears that in 3.21.0 of python-bigquery the error handling was changed and the descriptive error message was dropped. This message is useful for users and we rely on it for testing purposes.
Likely PR that introduced the change: googleapis/python-bigquery#1900
resolves #
docs dbt-labs/docs.getdbt.com/#
Problem
Solution
Checklist