Fix Google Cloud Batch error messages to include job name#69783
Open
parkhojeong wants to merge 2 commits into
Open
Fix Google Cloud Batch error messages to include job name#69783parkhojeong wants to merge 2 commits into
parkhojeong wants to merge 2 commits into
Conversation
The missing f-string prefixes caused Cloud Batch errors to display the
literal `{job_name}`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add missing f-string prefixes so Cloud Batch errors display the actual job
name instead of
{job_name}.f"Batch job with name {job_name} has failed its execution."f"Unexpected error in the operation: Batch job with name {job_name} is being deleted."Test:
breeze run pytest providers/google/tests/unit/google/cloud/hooks/test_cloud_batch.py -xvsWas generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.