-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Add missing await. #14910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add missing await. #14910
Conversation
Summary of ChangesHello @gundermanc, 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 resolves a subtle but critical bug within the 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 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 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
|
There was a problem hiding this 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 a critical bug where a missing await on an asynchronous call could lead to an unhandled promise rejection and a potential crash when the keychain is unavailable. The fix is simple, correct, and effectively resolves the issue. Additionally, a new unit test has been added that thoroughly validates the fix, ensuring this regression won't occur in the future. The changes are excellent and improve the robustness of the application.
|
Size Change: +4 B (0%) Total Size: 21.6 MB ℹ️ View Unchanged
|
Summary
Adds an await to clearSettings() function's
keychain.isAvailable()branch. Previously, this code was inadvertently checking the truthiness of the returned promise instead of the underlying boolean resulting in it never being run.I discovered this while trying to enable various eslint promise correctness rules. I am not sure there is user visible misbehavior but it looks as though it might cause an error to bubble up to the user when there is no keychain available.
As a follow up, we should enable a broader set of eslint rules to prevent similar pitfalls.
How to Validate
Run the provided unit test before and after the change.
Pre-Merge Checklist