can't install prebuilt binary, server response is 403 Forbidden

[azmy60]

Hey!

Using this repo, I got 403 forbidden error after running yarn install:

I'm not sure if anyone else also experienced this, or my IP region is not allowed for some reason?

[carlopi]

How did you got that? v0.0.2 looks wrong, need to double check.

[carlopi]

Links should be in the form:
duckdb-v0.10.2-dev5.0-node-v108-linux-x64.tar.gz

Can you share some more context?

[azmy60]

I cloned this repo, and I just simply run yarn. Also tried npm install after I realized it uses package-lock.json, but still got the same result.

NPM: 9.5.1
Node: 18.16.0

[azmy60]

So the version in package.json is 0.0.2-dev5.0. Changing it to 0.10.2-dev5.0 fixes it for me.

duckdb-node/package.json

Line 5 in a5ec8f3

"version": "0.0.2-dev5.0",

I feel like this could be the reason why when I installed duckdb last time it took 20 minutes or so? #70

[ryan-williams]

This Gitlab action just got a 403 from duckdb-node.s3.amazonaws.com/duckdb-v0.10.0-node-v127-linux-x64.tar.gz, output this line:

Pre-built binaries not installable for duckdb@0.10.0 and node@22.2.0 (node-v127 ABI, glibc) (falling back to source compile with node-gyp) 

and has been slowly compiling for 18 mins. This job usually finishes in under a minute.

Update: previous successful run fetched from duckdb-node.s3.amazonaws.com/duckdb-v0.10.0-node-v120-linux-x64.tar.gz, which also 200's for me now.

Seems like maybe my Gitlab runner is using a newer Node today, and there's not a v0.10.0 for that version? Not sure how to interpret node-v120 vs. node-v127, but the error message above implies the latter corresponds to node@22.2.0?

[azmy60]

So it looks like node-pre-gyp looks for version in package.json and we need a way to match that and the actual pre-built binaries version. If that's the issue, I have two solutions I can think of:

1. Just update the version in package.json to match with the binaries version.
2. Or specify the version when building the binaries following the package.json version, like how grpc works on their build script.

• build version matching package.json version https://github.com/grpc/grpc-node/blob/a4c2106e63064070f3b9e580b2d1c74b0a9503a4/packages/grpc-tools/build_binaries.sh#L24

[azmy60]

Ok. It works fine if I install duckdb from npm, but the weird thing is the version in npm is different from this repo.

package.json in npmjs.com

package.json in duckdb-node repo

[Pertempto]

the weird thing is the version in npm is different from this repo.

Yeah, this is really strange to me.

We're blocked from using duckdb because we can't install it on our linux servers without getting an error

npm error command sh -c node-pre-gyp install --fallback-to-build

from what we can tell this is directly connected to this issue