Conversation
Summary of ChangesHello, 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 race conditions occurring during PTY resizing, particularly when a PTY is in the process of exiting. By suppressing specific EBADF and PTY-related errors, the application avoids unnecessary crashes caused by frequent UI layout updates. Highlights
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. Footnotes
|
|
Size Change: +312 B (0%) Total Size: 33.9 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Code Review
This pull request aims to suppress EBADF (Bad File Descriptor) errors on Windows and Linux, which can occur as a race condition when resizing a node-pty terminal that has already exited. However, globally swallowing all EBADF errors in the uncaughtException handler is highly risky as it can mask critical bugs from other parts of the application. It is recommended to restrict this suppression specifically to errors originating from node-pty by checking the error's stack trace.
Summary
Matches upstream node-pty fix for issue #827. Suppresses crashes when resizing a PTY that is in the process of exiting. This issue was exacerbated by recent UI layout changes that increased resize frequency.
Related Issues
b/516018762