-
Notifications
You must be signed in to change notification settings - Fork 1.3k
"Binary has a problem" with 4.13.1 #2822
Comments
Did you clear your node_modules or vendor folder? The binding code was changed so it won't be able to reusing the binding.node from 4.13.0 |
We got this in a docker build as well. We aren't using any lock files. Changed the package.json from Our npm installs were complaining about python 2 not being found... |
@xzyfer Are you guys fixing this? |
Logs from npm install in a Docker image from
|
Seeing the same. Putting "node-sass": "4.13.0" into the package.json allowed me to build the project. |
Seeing in the same problem in our docker build using
|
Thanks for looking at this.
This is still failing:
|
This is still occurring for us as well. Binary has a problem: Error: Error relocating /node_modules/node-sass/vendor/linux_musl-x64-64/binding.node: _ZNSt7__cxx1118basic_stringstreamIcSt11char_traitsIcESaIcEEC1Ev: symbol not found |
Ok thanks. Nothing has changed in how we build binaries for a couple
releases now so this could take a while. I don't have time to look into for
a day or two.
…On Fri, 17 Jan 2020, 8:53 am chrflo, ***@***.***> wrote:
This is still occurring for us as well.
Binary has a problem: Error: Error relocating
/node_modules/node-sass/vendor/linux_musl-x64-64/binding.node:
_ZNSt7__cxx1118basic_stringstreamIcSt11char_traitsIcESaIcEEC1Ev: symbol not
found
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2822?email_source=notifications&email_token=AAENSWBRP5OAEU243BTIGSDQ6DJMVA5CNFSM4KHXYZ3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJFV2JQ#issuecomment-575364390>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAENSWCJXKVNNTNN2WHG6O3Q6DJMVANCNFSM4KHXYZ3A>
.
|
Seeing the same issue here in our CI/CD. Alpine Linux, was ^4.11.0 in the package.json file, will pin as per some other suggestions and report back. EDIT: Previous build was running 4.13.0 with no issues, todays was 4.13.1, reverting to 4.13.0 resolved the issue. Logs from failure:
|
I had the same problem on Alpine. I guess it may be caused by different versions of Alpine. |
…ue: sass/node-sass#2822" This reverts commit 75e4ee9.
I've digging into this. It looks an issue with node:-alpine containers < 10.18. Something may have changed in with the newer containers which is causing incompatibilities with older node:-alpine containers. This works fine
Where this fails with the errors reported here
Judging by the reports in this issue this isn't isolated to Node 10 builds since we have reports from Node 8 also. |
I've rebuilt the Node 10 alpine binary with node 10.16. This appears to address this issue. |
Are you sure that the problem is related to Node 10 Alpine? I encountered it running a Python Alpine (3.7.2-alpine3.8) onto which we installed Node. |
This works fine |
@xzyfer Retried a build with 4.13.1 today, and still getting the bad binary issue:
|
Also having this problem with node:8.12-alpine image:
[email protected] works fine |
Initially, I was able to resolve by also explicitly using However, one of the architects on my team ran |
@anthonycarella Ah, excellent point. We have a private registry that serves as a proxy, and I bet it has the old 4.13.1 cached. I'll see if we can get that cleared. |
- Bump from alpine 3.10 to 3.11 to avoid compiling node-sass. It's important to avoid this as it decreased the build time to ~2 mintues :/. See sass/node-sass#2822 (comment) - CI: cache node modules using the github action cache.
- Bump from alpine 3.10 to 3.11 to avoid compiling node-sass. It's important to avoid this as it decreased the build time to ~2 mintues :/. See sass/node-sass#2822 (comment) - CI: cache node modules using the github action cache.
- Bump from alpine 3.10 to 3.11 to avoid compiling node-sass. It's important to avoid this as it decreased the build time to ~2 mintues :/. See sass/node-sass#2822 (comment) - CI: cache node modules using the github action cache.
- Bump from alpine 3.10 to 3.11 to avoid compiling node-sass. It's important to avoid this as it decreased the build time to ~2 mintues :/. See sass/node-sass#2822 (comment) - CI: cache node modules using the github action cache.
- Bump from alpine 3.10 to 3.11 to avoid compiling node-sass. It's important to avoid this as it decreased the build time to ~2 mintues :/. See sass/node-sass#2822 (comment) - CI: cache node modules using the github action cache.
I've updated the Node 8 binary. It should work now. |
I had this problem with linux kernel 5.0.0-38-generic. My coleagues, while building the same Dockerfile, did not encounter this error (with the version 4.13.1). They were running kernels version 5.3+. I had to downgrade to 4.13.0. |
Updating |
I used npm and had the same issue after I run "yarn add node-sass" and it's worked. |
same for me |
I'm using some other libraries that require a newer version of node.js (not 10.14-alpine). Has there been any progress in fixing this bug? Logs:
|
@KingOfCramers We don't know what the bug really is, sorry. Most certainly not in the node-sass JavaScript or even C++ code. |
We're getting the following during builds with 4.13.1 - if we go back to 4.13.0 everything is fine.
2020-01-16T17:04:44.3993932Z > [email protected] postinstall /node_modules/node-sass
2020-01-16T17:04:44.4010867Z > node scripts/build.js
2020-01-16T17:04:44.4016913Z
2020-01-16T17:04:44.5530663Z Binary found at /node_modules/node-sass/vendor/linux_musl-x64-64/binding.node
2020-01-16T17:04:44.5548706Z Testing binary
2020-01-16T17:04:44.6559773Z Binary has a problem: Error: Error relocating /node_modules/node-sass/vendor/linux_musl-x64-64/binding.node: _ZNSt7__cxx1118basic_stringstreamIcSt11char_traitsIcESaIcEEC1Ev: symbol not found
2020-01-16T17:04:44.6609834Z at Object.Module._extensions..node (internal/modules/cjs/loader.js:718:18)
2020-01-16T17:04:44.6623255Z at Module.load (internal/modules/cjs/loader.js:599:32)
2020-01-16T17:04:44.6640744Z at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
2020-01-16T17:04:44.6653951Z at Function.Module._load (internal/modules/cjs/loader.js:530:3)
2020-01-16T17:04:44.6667669Z at Module.require (internal/modules/cjs/loader.js:637:17)
2020-01-16T17:04:44.6681340Z at require (internal/modules/cjs/helpers.js:22:18)
2020-01-16T17:04:44.6696639Z at module.exports (/node_modules/node-sass/lib/binding.js:19:10)
2020-01-16T17:04:44.6713582Z at Object. (/node_modules/node-sass/lib/index.js:14:35)
2020-01-16T17:04:44.6730091Z at Module._compile (internal/modules/cjs/loader.js:689:30)
2020-01-16T17:04:44.6743279Z at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
The text was updated successfully, but these errors were encountered: