[help needed] Problems accessing Gladys

[bertrandda]

@pierre-gilles

(@bertrandda, while I’m at it, for now the MCP integration doesn’t have a stop function and therefore stopping the service only has an effect on restart!)

I’ll take care of it, but I have a problem with your latest changes on master. When I run npm install it loops and never finishes, and when I force it to stop this error message appears

npm error path /Users/bertrand/Documents/perso/Gladys/server/node_modules/duckdb
npm error command failed
npm error signal SIGINT
npm error command sh -c node-pre-gyp install --fallback-to-build
npm error CXX(target) Release/obj.target/duckdb/src/duckdb_node.o
npm error   CXX(target) Release/obj.target/duckdb/src/database.o
npm error   CXX(target) Release/obj.target/duckdb/src/data_chunk.o
npm error   CXX(target) Release/obj.target/duckdb/src/connection.o

it continues for dozens of lines.
Am I the only one?

[pierre-gilles]

It works for me, which OS are you on? What version of Node.js?

[bertrandda]

On macOS Tahoe with an Intel Mac and Node.js 22.21.1. It worked very well yesterday when I tested the latest power-related changes.

[pierre-gilles]

In the meantime I just updated DuckDB from v1.4.1 to v1.4.3!

Very likely that this version isn’t compiled for your architecture, but it’s strange that this would be the case only for this specific version…

I’m on macOS Sequoia, Node 22, but on an Apple Silicon Mac

[Terdious]

Hello @pierre-gilles,
Okay I just tested.

The chart transitions (8 curves) like this one:

• Take roughly exactly the same time for the 1h, 12h, 24h, 7 days, 30 days and 3 months views, i.e. 1 to 3s.
• Take slightly more time for the 1 year view, but it’s on the order of 2s more for an initial display time of 8–10s, so not penalizing.

On resources:

• I used to go from 5.9GB to a fixed 9.9GB before
• I now go from 5.9GB to 8.1GB of RAM.

Maybe an impression that the CPU is under load a bit longer at 100% but nothing obvious.

So this seems appropriate regarding the change. And as you say we can always optimize the requests in a later dev.

[pierre-gilles]

Thanks for the feedback!

I’ll merge this then

@Terdious

Takes slightly longer to display 1 year, but it’s on the order of ~2s more for an initial display time of 8–10s, so not penalizing.

For this topic, can you create a dedicated post with the exact parameters of the request?

[bertrandda]

@pierre-gilles

In the meantime, I just updated DuckDB from v1.4.1 to v1.4.3!

It’s very likely that this version wasn’t built for your architecture, but it’s strange that it’s the case only for this specific version…

I did some tests — it’s indeed 1.4.3 that won’t install. I waited 45 minutes for it to compile and that doesn’t work either.
1.4.2 installs correctly; there must be an issue with the 1.4.3 release for my architecture. I wonder if this PR fixing osx runners, macos-13 is gone by hannes · Pull Request #176 · duckdb/duckdb-node · GitHub might fix that.

For information, I don’t know if you saw the note (see above https://www.npmjs.com/package/duckdb and Node.js API – DuckDB) but it seems the client we’re using is deprecated and will no longer be updated in 2026. The new one is this https://www.npmjs.com/package/@duckdb/node-api — we’ll need to migrate to it.

[pierre-gilles]

@bertrandda

Version 1.4.2 installs correctly, there must be a problem with the 1.4.3 release for my architecture. I wonder if this PR fixing osx runners, macos-13 is gone by hannes · Pull Request #176 · duckdb/duckdb-node · GitHub will fix that.

That looks a lot like it, yes!

@bertrandda

it seems that the client we’re using is deprecated and will no longer be updated in 2026. The new one is this https://www.npmjs.com/package/@duckdb/node-api we’ll have to switch to it

I saw, we’ll have to migrate, yes ^^