-
Notifications
You must be signed in to change notification settings - Fork 72
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
Better error handling/user guidance for missing local models #53
Comments
I can see that the instructions are in the README here: Which suggests I need to run I wonder if it might make more sense to have the local model download as a sub-command of
There also seems to be very minimal information output during the download. It might be nice to know a bit more about which model is being downloaded, from where, where it's being saved, how large it is, etc: ⇒ npx humanifyjs download 2b
(node:97932) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Downloaded 1.63 GB I guess it does provide slightly more info when the download is completed: ⇒ npx humanifyjs download 2b
(node:97932) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Model "2b" downloaded to /Users/devalias/.humanifyjs/models/Phi-3.1-mini-4k-instruct-Q4_K_M.gguf I can see it's downloaded here:
And the code for that is here: Lines 13 to 25 in 85d17e7
I also notice that It seems the humanify/src/plugins/local-llm-rename/llama.ts Lines 19 to 22 in 85d17e7
Which only seems to work for model aliases defined in Lines 69 to 75 in 85d17e7
Even though the error text for Lines 77 to 85 in 85d17e7
And usually for LLM apps, the Edit: Created a new issue related to the download progress/etc: |
Currently when trying to run with a local model that isn't downloaded, the app crashes with an error such as the following:
It might be useful to give a more user friendly error that explains how to resolve the issue.
I ran into this while trying to test/replicate the following:
The text was updated successfully, but these errors were encountered: