-
Notifications
You must be signed in to change notification settings - Fork 3.8k
[Web][Version] Fix WebLLM vision model issues #18680
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
base: main
Are you sure you want to change the base?
Conversation
akaashrp
commented
Jan 22, 2026
- Rename FTVMFFIErrorSetRaisedFromCStr to TVMFFIErrorSetRaisedFromCStr
- Try multiple candidates for maxComputeInvocationsPerWorkgroup
- Update tvmjs version to 0.23.0-dev2
Summary of ChangesHello @akaashrp, 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 aims to resolve issues impacting WebLLM vision models by performing a version bump for the Highlights
🧠 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 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 introduces fixes for WebLLM vision models, including updating the package version, renaming an FFI function, and adding logic to dynamically select maxComputeInvocationsPerWorkgroup based on device limits. The changes are generally good, but I've found a couple of areas for improvement. Specifically, there's an incomplete refactoring where a function rename was not propagated to its type cast, which could lead to build or runtime errors. I've also pointed out a small code redundancy that can be simplified. Please see the detailed comments.
| (this.lib.exports.TVMFFIErrorSetRaisedFromCStr as ctypes.FTVMFFIErrorSetRaisedFromCStr)( | ||
| stack.ptrFromOffset(errKindOffset), | ||
| stack.ptrFromOffset(errMsgOffset) | ||
| ); |
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.
The function name has been updated to TVMFFIErrorSetRaisedFromCStr, but it's being cast to the old type ctypes.FTVMFFIErrorSetRaisedFromCStr. This is inconsistent and suggests an incomplete refactoring. The type definition in ctypes.ts and this cast should be updated to use the new name TVMFFIErrorSetRaisedFromCStr for consistency.
| (this.lib.exports.TVMFFIErrorSetRaisedFromCStr as ctypes.FTVMFFIErrorSetRaisedFromCStr)( | |
| stack.ptrFromOffset(errKindOffset), | |
| stack.ptrFromOffset(errMsgOffset) | |
| ); | |
| (this.lib.exports.TVMFFIErrorSetRaisedFromCStr as ctypes.TVMFFIErrorSetRaisedFromCStr)( | |
| stack.ptrFromOffset(errKindOffset), | |
| stack.ptrFromOffset(errMsgOffset) | |
| ); |
|
|
||
| const candidates = [1024, 512, 256]; | ||
| const limit = adapter.limits.maxComputeInvocationsPerWorkgroup; | ||
| const requiredMaxComputeInvocationsPerWorkgroup = candidates.find(x => x <= limit) || undefined; |
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.
The || undefined is redundant here. Array.prototype.find() already returns undefined if no element satisfies the testing function.
| const requiredMaxComputeInvocationsPerWorkgroup = candidates.find(x => x <= limit) || undefined; | |
| const requiredMaxComputeInvocationsPerWorkgroup = candidates.find(x => x <= limit); |
|
@akaashrp we need a rebase |