zsh: illegal hardware instruction

[loretoparisi]

I get zsh: illegal hardware instruction when executing with v14.17.3 a inference script like

import { LLama } from "llama-node";
import { LLamaCpp } from "llama-node/dist/llm/llama-cpp.js";
import path from "path";

const model = path.resolve(process.cwd(), "../gpt4all/gpt4all-converted.bin");

const llama = new LLama(LLamaCpp);

const config = {
    path: model,
    enableLogging: true,
    nCtx: 1024,
    nParts: -1,
    seed: 0,
    f16Kv: false,
    logitsAll: false,
    vocabOnly: false,
    useMlock: false,
    embedding: false,
};

llama.load(config);

const template = `How are you`;

const prompt = `### Human:

${template}

### Assistant:`;

llama.createCompletion(
    {
        nThreads: 4,
        nTokPredict: 2048,
        topK: 40,
        topP: 0.1,
        temp: 0.2,
        repeatPenalty: 1,
        stopSequence: "### Human",
        prompt,
    },
    (response) => {
        process.stdout.write(response.token);
    }
);

I'm using

% tsc --version                        
Version 5.0.4
% npm --version
9.6.4
% node --version
v14.17.3

[hlhr202]

are you using alpine linux? we are currently compiling for GNU linux actually since alpine has a different libc.

[loretoparisi]

are you using alpine linux? we are currently compiling for GNU linux actually since alpine has a different libc.

no I'm on macOS, Apple Silicon.

[hlhr202]

@loretoparisi This is a bug from CI cross compiling process and I m investigating it. for temporary solution, you need to build it manually. the process is to prepare rust and clone this project, locate packages/llama-cpp and run "npm run build", then collect the binary from @llama-node folder (under packages/llama-cpp)

[hlhr202]

@loretoparisi I have publish 0.0.26 to fix this temporarily, but you still need to upgrade to node.js 16 or higher version. I will leave this issue open untill I fix the CI pipeline for cross compiling.

[loretoparisi]

@loretoparisi I have publish 0.0.26 to fix this temporarily, but you still need to upgrade to node.js 16 or higher version. I will leave this issue open untill I fix the CI pipeline for cross compiling.

okay thank you! I think node16 is ok. I have problems with WASM modules and node >=17, so just for test it should be fine. Right now I'm still stuck to node 14.7.3 for that reason!

[hlhr202]

@loretoparisi this issue has been fully resolved since v0.0.27