Open alioop222 opened 3 weeks ago
can you check if the server
file is actually located inside your ~/llamanet
path somewhere?
@cocktailpeanut ~/llamanet just has /models in it. I wanted to ask you also about using llamanet in conjunction with this https://discord.gg/uMaGSHNjzc. It is recommended to use it in a docker container and i was wondering if i should have llamanet on board already or if i add the lines to the docker initiation would it work anyway?
Title of the Issue: Issues with "no valid release" and missing imports Updated Description: Hello, I've encountered a persistent issue where I receive a "no valid release" message when trying to run Llamanet using npx llamanet@latest. Additionally, I've noticed that there are missing imports in the package which might be contributing to the problem. Details: Environment: macOS, Node.js v22.2.0, npm v10.7.0 Commands Run: npm cache clean --force npm install -g llamanet@latest Issues Encountered:
Hi, i tried the install on the command line
I got loads of the screenshot behaviour and then the following : (base) alimac@Alistairs-Mac-mini ~ % >....
./server -c 2048 --embeddings -m /Users/alimac/llamanet/models/huggingface/microsoft/Phi-3-mini-4k-instruct-gguf/Phi-3-mini-4k-instruct-q4.gguf --port 8000 node:events:498 throw er; // Unhandled 'error' event ^
Error: spawn ./server ENOENT at ChildProcess._handle.onexit (node:internal/child_process:286:19) at onErrorNT (node:internal/child_process:484:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) Emitted 'error' event on ChildProcess instance at: at ChildProcess._handle.onexit (node:internal/child_process:292:12) at onErrorNT (node:internal/child_process:484:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { errno: -2, code: 'ENOENT', syscall: 'spawn ./server', path: './server', spawnargs: [ '-c',
Any ideas?