AWS 403 error for prebuilt binaries on node 7.0.0

I am getting this error after upgrading to node 7.0.0:

ERR! Tried to download(403): https://nodegit.s3.amazonaws.com/nodegit/nodegit/nodegit-v0.16.0-node-v51-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for nodegit@0.16.0 and node@7.0.0 (node-v51 ABI) (falling back to source compile with node-gyp)

The install works in node 6.9.1.
Tested on Windows 10.

Have the same

me too https://travis-ci.org/thisconnect/nodegit-kit/jobs/173458364 thisconnect/nodegit-kit#19

Nearly the same here, 403ing on ERR! Tried to download(403): https://nodegit.s3.amazonaws.com/nodegit/nodegit/nodegit-v0.16.0-node-v45-linux-x64.tar.gz

same here

System: Linux
Node: 7.2.0
Npm: 3.10.10 / Yarn: 0.17.9
Nodegit: 0.16.0

node-pre-gyp ERR! Tried to download(403): https://nodegit.s3.amazonaws.com/nodegit/nodegit/nodegit-v0.16.0-node-v51-linux-x64.tar.gz node-pre-gyp ERR! Pre-built binaries not found for nodegit@0.16.0 and node@7.2.0 (node-v51 ABI) (falling back to source compile with node-gyp)

Then it builds successfully and works.

Same here cannot install nodegit because of the missing binaries.

Looks like NodeGit doesn't build on node v7 at all right now. We have to figure out a way to link to OpenSSL better. Fix should be incoming soon. Thanks!

@johnhaley81

@johnhaley81 ha just hit this myself >_< damn arch linux bumping to 7

Wait, whats the openssl bug?

@johnhaley81

Yeah, master builds for me on node 7.4 on osx. Playing with it now to test, but so far so good. I'd be curious to see your logs @johnhaley81 @tbranyen

@maxkorp

@maxkorp check latest master, we merged 7.4.0 support ^_^

It's causing problem on alpine linux within a container

test.js

require('nodegit').Repository.open('tmp')

Dockerfile

FROM mhart/alpine-node:7.4
RUN apk add --update --no-cache make gcc g++ python libssh2-dev file git openssl-dev file git openssl-dev
RUN npm install nodegit@0.17.0
RUN mkdir -p /app
COPY test.js /app
CMD node /app/test.js

running the container

docker build -t ngtest . && docker run --rm ngtest

exact same cause as : #1039

/node_modules/nodegit/dist/nodegit.js:15
    throw ex;
    ^

Error: Error relocating /node_modules/nodegit/build/Release/nodegit.node: __rawmemchr: symbol not found
    at Object.Module._extensions..node (module.js:598:18)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/node_modules/nodegit/dist/nodegit.js:11:12)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)

I'm guessing because it's not using glibc, but musl libc

Would it be possible to do something regarding that?

I'm not sure, but that seems likely.

Thats probably the issue, and it's really probably out of our scope to fix that, unfortunately, unless we wanna custom roll some CI.

Your call :-) But since Alpine kind of became the de facto base image for Docker, you should think about it.

NOTE: It does build from source within the container on 0.16 so it is possible to get 0.17 built within it as well.

I would be happy to be able to help you getting this done. PM me if you are interested.

Thanks for the quick reply!

@cnadeau

@cnadeau definitely! i personally don't know how we could support this without bulking up our already large build matrix. if you can find a non-intrusive resolution that would be super ideal :)

I'll see what I can do next week :-)

@tbranyen

@tbranyen I have not experience with travis and thought it would not be that complicated, but after reading a bit, aside manually spinning up a container to build it, I don't see a good solution.

My guess would be to define CXX flag to g++ for a new platform

https://github.com/nodegit/nodegit/blob/master/.travis.yml#L49

to get

https://github.com/nodegit/nodegit/blob/master/generate/templates/templates/binding.gyp#L108

used by node-gyp

but again, no travis neither C++ expert.

Any comments/reactions/suggestions are welcomed

The other problem with using a newer libgc is that actually kills a lot of older app builds on LTS ubuntu etc :/

Node 7 is end of life, this issue should be closed.

Yeah we build 6, 8 and 9 now.

I am still getting this error on Node v10.13.0

What version of NodeGit are you using? Earlier versions do not have prebuilts for node 10.

Navigation Menu

Repository navigation

AWS 403 error for prebuilt binaries on node 7.0.0 #1157

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

AWS 403 error for prebuilt binaries on node 7.0.0 #1157

Description

Activity

aspirisen commented on Nov 14, 2016

thisconnect commented on Nov 15, 2016

dukeofsussex commented on Nov 16, 2016

michael34435 commented on Nov 21, 2016

matteocng commented on Nov 28, 2016

akougblenou commented on Dec 21, 2016

johnhaley81 commented on Jan 27, 2017

tbranyen commented on Jan 29, 2017

maxkorp commented on Jan 30, 2017

maxkorp commented on Jan 30, 2017

tbranyen commented on Jan 30, 2017

cnadeau commented on Feb 8, 2017

tbranyen commented on Feb 8, 2017

maxkorp commented on Feb 9, 2017

cnadeau commented on Feb 10, 2017

tbranyen commented on Feb 10, 2017

cnadeau commented on Feb 10, 2017

cnadeau commented on Feb 21, 2017

maxkorp commented on Feb 21, 2017

Croydon commented on Jul 27, 2018

maxkorp commented on Sep 4, 2018

rut-shah commented on Dec 5, 2018

implausible commented on Dec 10, 2018

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions