Skip to content

chore: update googleapis and regenerate#17138

Open
suztomo wants to merge 1 commit into
googleapis:mainfrom
suztomo:librarianops-generateall-20260514T162407Z
Open

chore: update googleapis and regenerate#17138
suztomo wants to merge 1 commit into
googleapis:mainfrom
suztomo:librarianops-generateall-20260514T162407Z

Conversation

@suztomo
Copy link
Copy Markdown
Member

@suztomo suztomo commented May 14, 2026

Update googleapis to the latest commit and regenerate all client libraries.

@suztomo suztomo requested review from a team as code owners May 14, 2026 17:01
@snippet-bot
Copy link
Copy Markdown

snippet-bot Bot commented May 14, 2026

Here is the summary of changes.

You are about to add 8 region tags.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

@suztomo suztomo requested a review from chalmerlowe May 14, 2026 17:11
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates several Google Cloud client libraries, adding new features and methods for Google Apps Chat, Compute Engine, Kubernetes Engine, Gemini Data Analytics, and Cloud Support. Notable changes include new message notification options, capacity advice functionality, and enhanced GKE cluster configurations. Feedback focuses on correcting errors in the REST transport layer where the wrong object was passed to JSON serialization methods. Additionally, the reviewer recommended replacing broad or bare exception handlers with more specific ones that include proper logging to improve debuggability and prevent silent failures.

Comment on lines +648 to +649
response_payload = compute.CapacityAdviceResponse.to_json(response)
except:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

There are two issues here: 1. The to_json method is being called with the HTTP response object (a requests.Response instance) instead of the parsed message object resp. 2. Avoid broad except Exception: blocks that silently return None. Instead, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues.

Suggested change
response_payload = compute.CapacityAdviceResponse.to_json(response)
except:
response_payload = compute.CapacityAdviceResponse.to_json(resp)
except Exception as e:
logger.warning(f"Error occurred: {e}")
References
  1. Avoid broad except Exception: blocks that silently return None. Instead, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues.

Comment on lines +806 to +807
response_payload = compute.CapacityHistoryResponse.to_json(response)
except:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

The to_json method is called with the wrong object (response instead of resp). Additionally, avoid broad except Exception: blocks that silently return None. Instead, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues.

Suggested change
response_payload = compute.CapacityHistoryResponse.to_json(response)
except:
response_payload = compute.CapacityHistoryResponse.to_json(resp)
except Exception as e:
logger.warning(f"Error occurred: {e}")
References
  1. Avoid broad except Exception: blocks that silently return None. Instead, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues.

Comment on lines +751 to +752
response_payload = compute.Policy.to_json(response)
except:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

The to_json method is called with the wrong object (response instead of resp). Additionally, avoid broad except Exception: blocks that silently return None. Instead, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues.

Suggested change
response_payload = compute.Policy.to_json(response)
except:
response_payload = compute.Policy.to_json(resp)
except Exception as e:
logger.warning(f"Error occurred: {e}")
References
  1. Avoid broad except Exception: blocks that silently return None. Instead, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues.

Comment on lines +425 to +426
response_payload = attachment.Attachment.to_json(response)
except:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

The to_json method is called with the wrong object (response instead of resp). Additionally, avoid broad except Exception: blocks that silently return None. Instead, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues.

Suggested change
response_payload = attachment.Attachment.to_json(response)
except:
response_payload = attachment.Attachment.to_json(resp)
except Exception as e:
logger.warning(f"Error occurred: {e}")
References
  1. Avoid broad except Exception: blocks that silently return None. Instead, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues.

method = transcoded_request["method"]
try:
request_payload = type(request).to_json(request)
except:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

Avoid using bare except: blocks. Catching Exception is preferred to avoid intercepting system-level signals. Additionally, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues, as per the repository's guidelines.

Suggested change
except:
except Exception as e:
logger.warning(f"Error occurred: {e}")
References
  1. Avoid broad except Exception: blocks that silently return None. Instead, log the exception (e.g., using logger.warning) to aid in debugging and prevent masking underlying issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant