-
Notifications
You must be signed in to change notification settings - Fork 20
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
Main update 12 Aug #215
Merged
Main update 12 Aug #215
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Correctly handle new directory structure of zipfiles provided in the b3499 release.
…3499_release moxin-runner: on Windows, support WasmEdge no-avx WASI-nn plugin (release b3499)
Modals revision
Signed-off-by: csh <458761603@qq.com>
Signed-off-by: csh <458761603@qq.com>
Signed-off-by: csh <458761603@qq.com>
fix issue 132
Fix button hovers issues
…conversations Stop chat streaming when switching conversation
Signed-off-by: csh <458761603@qq.com>
…itch Fix loading animation model switch
Feat/ctx size
readme: mention that Windows is now supported
Also, improve the error output for developers using moxin-runner to explicitly state when the main moxin binary hasn't yet been built before running moxin-runner.
Update to robius-open v0.1.1, which properly opens file URIs on Windows
moxin-runner: support installing no-AVX versions of WasmEdge on Linux
Relying on the system-wide installation has myriad problems; this avoids those many problems entirely by only checking the app's data directory for a WasmEdge installation and installing WasmEdge there if it is missing, which guarantees that the specific version and build characteristics of the WasmEdge installation is always under the sole control of Moxin.
…app_data_dir Use (or install) WasmEdge in the app-specific data directory *ONLY*
fix issue 186
There was an issue where the title or description of some models in the main listing were not visible. The root problem was we were using similar identifiers for the title and description labels in ModelCard and ModelCardViewAllModal widgets (which is a nested view under the model card view). The solution is to use unique identifiers, so the widget lookup retrieves what we expect in each case..
…iption Fix intermittent issue with model card title and description labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.