Skip to content

Comments

Close yang library writer#2401

Merged
ihrasko merged 1 commit intoPANTHEONtech:mainfrom
Tobianas:close_yang_library_writer
Oct 15, 2025
Merged

Close yang library writer#2401
ihrasko merged 1 commit intoPANTHEONtech:mainfrom
Tobianas:close_yang_library_writer

Conversation

@Tobianas
Copy link
Contributor

This resource was not being closed which caused
ClusterSingletonServiceProvider to not be closed properly. This caused test failures as ClusterSingletonServiceProvider expected the yang library writer to be closed and failed to close.

JIRA: LIGHTY-340

This resource was not being closed which caused
ClusterSingletonServiceProvider to not be closed properly.
This caused test failures as ClusterSingletonServiceProvider
expected the yang library writer to be closed and failed to
close.

JIRA: LIGHTY-340
Signed-off-by: tobias.pobocik <[email protected]>
@gemini-code-assist
Copy link

Summary of Changes

Hello @Tobianas, 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 resource management issue where the yangLibraryWriter was not being closed, leading to cascading problems with the ClusterSingletonServiceProvider and causing test failures. The fix ensures proper shutdown behavior by explicitly closing the yangLibraryWriter when the controller stops, thereby improving system stability and test reliability.

Highlights

  • Resource Closure: The yangLibraryWriter resource is now explicitly closed during the controller's stop procedure to prevent resource leaks.
  • Test Stability: This change resolves test failures where the ClusterSingletonServiceProvider was unable to close properly due to the yangLibraryWriter remaining open.
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

@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 adds the closing of yangLibraryWriter during shutdown, which resolves an issue with ClusterSingletonServiceProvider not being closed properly. My review includes a suggestion to improve the overall robustness of the shutdown procedure by handling potential exceptions during resource cleanup to prevent the process from aborting prematurely. This will make the controller shutdown more resilient.

@ihrasko ihrasko merged commit 5201e2a into PANTHEONtech:main Oct 15, 2025
6 checks passed
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.

2 participants