check _editor validity before attempt to disconnect gutter_clicked, etc.

[d4lton]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @d4lton, I'm Gemini Code Assist¹! 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 enhances the stability of the diff-margin plugin by introducing a crucial validity check for the _editor object. By ensuring the editor instance is still active before performing cleanup operations, the change prevents potential crashes and improves the overall robustness of the plugin when handling script changes.

Highlights

• Editor Instance Validity: Implemented a check for the validity of the _editor instance before attempting to disconnect signals and remove gutters in the _on_editor_script_changed function. This prevents potential runtime errors if the editor object is no longer valid.

🧠 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. ↩

[gemini-code-assist]

Code Review

This pull request correctly adds a validity check for the _editor instance in _on_editor_script_changed before attempting to disconnect signals or remove the gutter. This is a good defensive measure to prevent potential crashes if the editor instance has been freed. The change is logical and well-implemented. For future improvement, you might consider applying a similar is_instance_valid(_editor) check in the _exit_tree function, which has similar code and could be susceptible to the same issue.