Adjust LiveSession.isClosed to handle closure more correctly - #8511
Adjust LiveSession.isClosed to handle closure more correctly#8511emilypgoogle wants to merge 6 commits into
Conversation
Using Gemini Code AssistThe 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
Customization To customize the 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 Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. 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. |
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request refactors LiveSession.isClosed() to check the session's active status and close reason instead of consuming frames from the incoming channel. It also moves the doBlocking helper to a test utility file and adds comprehensive unit tests for LiveSession.isClosed(). The feedback recommends capturing the volatile session property in a local variable within isClosed() to prevent potential race conditions during concurrent updates.
…pe/LiveSession.kt Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Adjusts
isClosedtoAdded testing for this new behavior with mocked connections.
Additionally, moved the contents of the removed
kotlin.ktfile totests.ktbecause of class name collision that only appeared after adding testing. It shouldn't have been namedkotlin.ktin that package to begin with.