⚡ Optimize synchronous file check in native worker

[zknpr]

• 💡 What: Replaced the synchronous fs.existsSync call with fs.promises.access in getNativeBinaryPath within src/nativeWorker.ts. Also updated isNativeAvailable and createNativeDatabaseConnection to be asynchronous, and propagated these changes to src/workerFactory.ts.
• 🎯 Why: The synchronous file system check blocks the Node.js event loop, potentially causing UI freezes if the file system is slow (e.g., network drives). Making this check asynchronous improves the responsiveness of the extension during initialization.
• 📊 Measured Improvement:
  • Baseline (Sync): ~0.0053 ms/op (latency) in a tight loop.
  • Optimized (Async): ~0.103 ms/op (latency) in a tight loop.
  • Trade-off: While the raw execution time of the async version is higher due to Promise overhead, it is non-blocking. This prevents the extension host from freezing, which is the primary goal for UI responsiveness. In a real-world scenario (single call during init), the difference in wall-clock time is negligible, but the non-blocking nature is critical.

---

PR created automatically by Jules for task 4677007369115403045 started by @zknpr

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sq-lite-explorer	Ready	Preview, Comment	Feb 7, 2026 1:13pm

[gemini-code-assist]

Summary of Changes

Hello @zknpr, 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 focuses on enhancing the responsiveness of the extension by converting blocking file system operations into non-blocking asynchronous calls. The primary goal is to prevent potential UI freezes, especially during the extension's initialization phase, by ensuring that file existence checks do not monopolize the event loop. While the raw execution time for asynchronous operations might be slightly higher, the critical benefit lies in maintaining a fluid user experience.

Highlights

• Asynchronous File System Checks: The synchronous fs.existsSync call in getNativeBinaryPath has been replaced with the asynchronous fs.promises.access to prevent blocking the Node.js event loop.
• Function Signature Updates: The getNativeBinaryPath, isNativeAvailable, and createNativeDatabaseConnection functions in src/nativeWorker.ts have been updated to be asynchronous, returning Promises.
• Propagation of Asynchronous Changes: The changes to asynchronous operations have been propagated to src/workerFactory.ts, ensuring that calls to isNativeAvailable are correctly awaited.

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

Changelog

• src/nativeWorker.ts
  • Changed getNativeBinaryPath function signature to async and its return type to Promise<string | null>.
  • Replaced fs.existsSync(binaryPath) with a try-catch block using await fs.promises.access(binaryPath, fs.constants.F_OK).
  • Updated isNativeAvailable function signature to async and its return type to Promise<boolean>, now awaiting the result of getNativeBinaryPath.
  • Modified createNativeDatabaseConnection to await getNativeBinaryPath.
• src/workerFactory.ts
  • Updated the type definition for nativeSupport.isNativeAvailable to return Promise<boolean>.
  • Added await when calling nativeSupport.isNativeAvailable(extensionPath).

Activity

• The pull request was automatically created by Jules for task 4677007369115403045, initiated by @zknpr.

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 successfully replaces a synchronous file system check (fs.existsSync) with an asynchronous one (fs.promises.access) to prevent blocking the Node.js event loop. The changes are correctly implemented, and the async nature is properly propagated up the call stack to dependent functions. This is an excellent optimization for UI responsiveness, especially in scenarios with slow file systems. The code is clean, and the reasoning provided in the pull request description is thorough. Great work!