perf(wasm): update tokio-fs-ext & opfs-project

[xusd320]

This pull request primarily updates dependencies and makes a minor adjustment to the logging filter in the utoo-wasm crate. The changes ensure compatibility with newer versions of libraries and improve the clarity of log output.

Dependency updates:

• Updated tokio-fs-ext from version 0.6.5 to 0.6.9 in the workspace root Cargo.toml for improved stability and bug fixes.
• Updated opfs-project from 0.1.15 to 0.1.16 and changed tokio-fs-ext to use the workspace version in crates/utoo-wasm/Cargo.toml, ensuring consistency and up-to-date dependencies. [1] [2]

Logging improvements:

• Changed the default log filter in init_log_filter to use utoo_wasm=info instead of the removed pack_napi=info, ensuring log output is relevant to the current crate.

Other updates:

• Updated the next.js submodule to a new commit, pulling in the latest changes from that dependency.

[gemini-code-assist]

Summary of Changes

Hello @xusd320, 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 primarily focuses on maintenance and performance by updating key Rust dependencies, refining logging behavior within the utoo-wasm crate, and syncing an external next.js submodule. These changes aim to enhance stability, ensure compatibility with newer library versions, and keep the project's dependencies up-to-date, contributing to overall project health and potential performance improvements.

Highlights

• Dependency Updates: Updated tokio-fs-ext from version 0.6.5 to 0.6.9 in the workspace root and opfs-project from 0.1.15 to 0.1.16 in crates/utoo-wasm/Cargo.toml, ensuring the project uses the latest stable versions of these libraries.
• Logging Filter Adjustment: Modified the default log filter in crates/utoo-wasm/src/lib.rs to use utoo_wasm=info instead of the removed pack_napi=info, improving the relevance and clarity of log output for the utoo-wasm crate.
• Submodule Update: The next.js submodule has been updated to a newer commit, pulling in the latest changes from that external dependency.
• Dependency Lock File Synchronization: The Cargo.lock file was updated to reflect the new dependency versions and removed entries for libz-rs-sys and zlib-rs, ensuring consistent and reproducible builds.
• WASM Bindings Regeneration: The TypeScript definition file for WASM bindings (packages/utoo-web/src/utoo/index.d.ts) was updated, likely due to the dependency changes, which involved reordering and adding some function declarations within the InitOutput interface.

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

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 updates several dependencies, notably tokio-fs-ext and opfs-project, and makes a corresponding adjustment to the logging filter. The changes are clear and align with the description. Moving tokio-fs-ext to a workspace dependency is a good step for maintainability. I have one suggestion to replace a hardcoded string with a constant to further improve code clarity.