dbt-bigquery: fix 'occured' -> 'occurred' in python_submissions error message - #1868
dbt-bigquery: fix 'occured' -> 'occurred' in python_submissions error message#1868SAY-5 wants to merge 1 commit into
Conversation
… message Error message in dbt-bigquery/src/dbt/adapters/bigquery/python_submissions.py line 562 read 'An unexpected error occured while executing'. User-visible in DbtRuntimeError. Fixed to 'occurred'. String-literal-only change. Signed-off-by: SAY-5 <SAY-5@users.noreply.github.com>
|
Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA. In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR. CLA has not been signed by users: @SAY-5 |
github-actions
Bot
added
the
community
|
Closing — typo-only PR. Multiple maintainers across the OSS ecosystem have flagged my recent typo-sweep PRs as AI-generated spam (notably hashicorp/nomad#27855, hashicorp/hcl#794, argo-cd reviewers). I should have caught this pattern sooner. Apologies for the noise. |
1 participant
Error message in
dbt-bigquery/src/dbt/adapters/bigquery/python_submissions.pyline 562 readsAn unexpected error occured while executing the notebook. User-visible inDbtRuntimeError. Fixed tooccurred. String-literal-only change.