Code not working on ubuntu?

[semisenioritis]

For some reason no matter what i do the code keeps on crashing on a ubuntu os. I thought that maybe it was the most recent merges, but then I tested a new code snapshot on my windows machine, and it seems to work pretty well.

Is this some bug or am I missing something?

The reason for the crashing is when I run: npm run dec I get: [nodemon] app crashed - waiting for file changes before starting

[karger]

nb's main deployment is on ubuntu, so i'm not sure where the problem is.

On 1/6/2023 12:55 PM, semisenioritis wrote:

For some reason no matter what i do the code keeps on crashing on a ubuntu os. I thought that maybe it was the most recent merges, but then I tested a new code snapshot on my windows machine, and it seems to work pretty well.

Is this some bug or am I missing something?

— Reply to this email directly, view it on GitHub https://github.com/haystack/nb/issues/262, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIWSXVQHABUBVPRBRPULVDWRBMBLANCNFSM6AAAAAATTJ6GZI. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[semisenioritis]

Hmm, weird. I tried reinstalling all libraries and even postgres but still have the same error.

[JumanaFM]

Hello! As David mentioned, our servers are running on Ubuntu so there should be no problems. Can you share more details or screenshots of the errors your getting?

[semisenioritis]

Right now im trying to do npm start and even that is throwing an error.

This is the error for the previous npm run dev

[semisenioritis]

This is the log for the npm start

[JumanaFM]

It's look like you're running Node v10, which doesn't support Optional chaining. Try upgrading your Node to v16 or newer version (I updated the README to include this info). Let me know how it goes.

[semisenioritis]

Wow, worked a charm thanks!! Turns out that for some reason when you install node from the command line, v10 is what gets downloaded. Id suggest that maybe putting this in some warning or faq might help future developers too.

Edit: Nope celebrated too early. npm run dev works, but now the issue is in npm run serve .

[semisenioritis]

So update, it turns out that node v17 had a patch update that closed a security hole in the SSL provider. This results in the error above. Link : https://stackoverflow.com/a/73027407

You can try to solve this issue by npm audit fix --force but the command can potentially break the system. I tried it and it did endup pushing another error. Now i have reverted back to node v16.19.0 and trying to run it

[semisenioritis]

Yup, v16.19.0 works quite well without any errors