You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's probably not a "bug", but <PATH TO WEIGHTS> in the docs should probably be <ABSOLUTE PATH TO WEIGHTS>. I tried to run lmql serve-model llama.cpp:vicuna-13b-v1.5-16k.Q4_K_M.gguf inside a directory with vicuna-13b-v1.5-16k.Q4_K_M.gguf, but I got a ValueError: Model path does not exist: vicuna-13b-v1.5-16k.Q4_K_M.gguf. Providing the full absolute path solves the problem.
The reason is that, in my case, the current directory gets changed to <root directory of the virtual environment>/lib/python3.11/site-packages when running the lmql command. Maybe that's the expected behavior, but at least specifying that the path should be absolute could cause less head-scratching for newbies :)
The text was updated successfully, but these errors were encountered:
It's probably not a "bug", but
<PATH TO WEIGHTS>
in the docs should probably be<ABSOLUTE PATH TO WEIGHTS>
. I tried to runlmql serve-model llama.cpp:vicuna-13b-v1.5-16k.Q4_K_M.gguf
inside a directory withvicuna-13b-v1.5-16k.Q4_K_M.gguf
, but I got aValueError: Model path does not exist: vicuna-13b-v1.5-16k.Q4_K_M.gguf
. Providing the full absolute path solves the problem.The reason is that, in my case, the current directory gets changed to
<root directory of the virtual environment>/lib/python3.11/site-packages
when running thelmql
command. Maybe that's the expected behavior, but at least specifying that the path should be absolute could cause less head-scratching for newbies :)The text was updated successfully, but these errors were encountered: