Skip to content

Conversation

@Mairuis
Copy link
Collaborator

@Mairuis Mairuis commented Jan 12, 2026

Summary

  • Fix unhandled exception in get_trigger_event_handler_safely() that broke dynamic select options
  • Added try-except block to gracefully handle cases where trigger provider is not registered

Problem

When using dynamic-select parameter type in tools or models, the plugin executor attempts to get a trigger event handler even when no trigger is registered. The _get_entry() method raises a ValueError when the provider is not found, and this exception was not caught, breaking the entire dynamic select functionality.

Solution

Wrapped the method body in a try-except block to catch any exceptions and return None gracefully. This allows dynamic select to function correctly even when triggers are not involved.

Closes #280

…egistered

When using dynamic select options in tools/models, the plugin executor
tries to get a trigger event handler even if no trigger is registered.
This caused an unhandled exception that broke the dynamic select
functionality.

Added try-except block to get_trigger_event_handler_safely() to catch
and log any exceptions, returning None instead of propagating the error.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Mairuis, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical bug affecting dynamic select options. Previously, if a trigger provider was not registered, the system would encounter an unhandled exception, leading to a breakdown in functionality. The change introduces robust error handling by wrapping the problematic logic in a try-except block, allowing the system to gracefully manage missing trigger providers and maintain the stability of dynamic select features.

Highlights

  • Exception Handling: Implemented a try-except block within the get_trigger_event_handler_safely() method to gracefully handle exceptions.
  • Dynamic Select Options Fix: Resolved an issue where dynamic select options would break due to an unhandled ValueError when a trigger provider was not registered.
  • Robustness: Ensured that the system can now handle scenarios where trigger providers are not found without crashing, returning None instead.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
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 correctly fixes an unhandled exception in get_trigger_event_handler_safely by wrapping the logic in a try-except block. My review includes one suggestion to improve the implementation by using the standard logging module for error messages instead of print, which is a best practice for libraries.

_, event_cls = entry.events[event]
return event_cls(runtime)
except Exception as e:
print(f"Error getting trigger event handler: {e!s}")
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

Using print() for errors in a library is not a best practice. It's better to use the logging module. This allows developers using your library to configure how and where logs are handled (e.g., setting log levels, redirecting to a file or a logging service), which is much more flexible than printing to standard output.

You'll need to add import logging at the top of the file.

As a side note, catching a broad Exception is powerful for a 'safe' function like this, but it can sometimes mask unexpected issues. It's worth being aware of this trade-off.

Suggested change
print(f"Error getting trigger event handler: {e!s}")
logging.warning(f"Error getting trigger event handler: {e!s}")

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.

Dynamic select options broken when trigger throws exception

2 participants