Catastrophic - CatAI is completely broken (Segmentation fault core dumped fatal error) about catai HOT 11 CLOSED

You only need to downgrade the node-llama packages to version 1.5, and this should work

from catai.

Version 1, is unstable and therefore in preview.
You can downgrade to version 0 with:

npm -g i catai@0

Then install one of the support models in this version

from catai.

from catai.

Downgrading does not help. I'm still getting the same error, even after downgrading straight to 0.3.12

from catai.

That may be because you use an unsupported model, use 'catai install' to install one of the supported models.

Probably the selected model is the model from version 1, you can do:
'catai use Vicuna-7B'
To change the selected model

from catai.

I'm facing same error on local run.
I use Windows 10, node.js v19.9.0
catai commit 4bed618

/d/demo/catai/server $ npm start
> [email protected] start
> node src/index.js

/c/Program Files/nodejs/npm: line 44:  3625 Segmentation fault      "$NODE_EXE" "$NPM_CLI_JS" "$@"

from catai.

from catai.

The library that binds CatAI with the model, stopped getting updates (node-llama). Now I am implementing, something like that, but this can take a while. For the meantime only old GGML will be supported :(

So catai version 1 and above is not recommended right now.

Use
npm i -g catai@0 to downgrade

from catai.

Thank you for the response. Perhaps I'm trying to run it locally from cloned repository as written in Development
Could you possibly suggest which commit should I checkout?

from catai.

Yes, Just did it. Fixed it by reverting package-lock.json in catai/server. Looks like problem in dependencies.

from catai.

This software is abandonware and relies on complicated package nonsense. Please consider using C++ or x86 assembly instead of a volatile language like Python. Might be painful, but at least it guarantees it actually bloody works instead of breaking CPU NX policies and segfaulting into /dev/null.

from catai.