Skip to content

fix(wasm): use latest forked libmimalloc and update deps - #2517

Merged
xusd320 merged 2 commits into
nextfrom
fix/libmimalloc-sys-v2
Jan 16, 2026
Merged

fix(wasm): use latest forked libmimalloc and update deps#2517
xusd320 merged 2 commits into
nextfrom
fix/libmimalloc-sys-v2

Conversation

@xusd320

@xusd320 xusd320 commented Jan 16, 2026

Copy link
Copy Markdown
Contributor

Changes

  • Update tokio-fs-ext to 0.7.1
  • Fix mimalloc patch configuration (remove explicit package name)
  • Enable nodePolyFill in utooweb-demo config
  • Include package-lock.json in demo files
  • Update next.js submodule

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @xusd320, 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 primarily focuses on maintaining the project's dependencies and configurations. It updates several key libraries to their latest versions, refines the WASM build process by fixing a mimalloc configuration, and enhances the WASM tracing capabilities. Additionally, it includes minor adjustments to the demo application's build process and updates a core submodule, ensuring the project remains current and stable.

Highlights

  • Dependency Updates: Updated tokio-fs-ext to version 0.7.1 and refreshed the libmimalloc forked repository to its latest commit in Cargo.lock and Cargo.toml.
  • WASM Configuration Fixes: Corrected the mimalloc patch configuration by removing an explicit package name in Cargo.toml.
  • WASM Tracing Enhancement: Enabled span events logging in WASM tracing by setting FmtSpan::CLOSE in crates/utoo-wasm/src/lib.rs, providing more detailed logging for span closures.
  • Demo Application Configuration: Enabled nodePolyFill in the utooweb-demo configuration and included package-lock.json in the demo files, which was previously excluded.
  • Submodule Update: Updated the next.js submodule to its latest commit.
  • WASM Bindings Update: Updated the packages/utoo-web/src/utoo/index.d.ts file to reflect new initLogFilter and init_pack functions in the WASM InitOutput interface, along with reordering some wasm_bindgen closure definitions.
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.

- Update tokio-fs-ext to 0.7.1
- Fix mimalloc patch (remove explicit package name)
- Enable span events logging in WASM tracing
- Enable nodePolyFill in utooweb-demo config
- Include package-lock.json in demo files
@xusd320
xusd320 force-pushed the fix/libmimalloc-sys-v2 branch from 399e5d9 to b10cd34 Compare January 16, 2026 10:44

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

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 primarily focuses on updating dependencies, including libmimalloc and tokio-fs-ext, and refining configurations for the WASM build. The changes align well with the description, such as enabling span event logging for better debugging and adjusting the mimalloc patch. My review includes a minor suggestion to improve code cleanliness by removing commented-out code instead of leaving it in the codebase. Overall, the changes are straightforward and beneficial.

Comment thread examples/utooweb-demo/src/demoFiles.ts
@xusd320
xusd320 merged commit 23444cb into next Jan 16, 2026
22 checks passed
@xusd320
xusd320 deleted the fix/libmimalloc-sys-v2 branch January 16, 2026 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants