-
-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot execute arm64 release binaries #2520
Labels
t/bug
Something isn't working
Comments
Any update on this? It seems https://github.com/stoplightio/spectral/releases/download/v6.11.0/spectral-linux-arm64 (
Please update npm in those latest packages and re release. |
Glad it worked! Apologies it took so long |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hello, Spectral folks. 👋 I receive the error "Error: Cannot find module '/snapshot/project/node_modules/tslib/tslib.js'" when executing the macos-arm64 binary at https://github.com/stoplightio/spectral/releases/tag/v6.10.0 . The full error is:
The error happens on releases for 6.8.0 and 6.9.0 as well. I have also run into this error when running
spectral-alpine-arm64
from an Alpine container. I suspect the problem has been here since arm64 releases were published starting with the 6.8.0 release.Also to note, I had to sign the macOS release via
codesign --sign - ./spectral-macos-arm64
to prevent my kernel from killing the program.Thanks for looking and for the help!
To Reproduce
codesign
if you're on a macExpected behavior
I expect to receive a usage statement since I'm not passing in any command arguments:
Environment
Additional context
I originally introduced arm64 builds in #2492.
pkg
execution worked fine locally on my macOS laptop. Looking at e9edd2e's build,pkg
executed with no error, but there are a large number of warnings in the build's output:There are 5,472 instances of these "Failed to make bytecode node18-arm64" warnings. I suspect this is the problem.
I was unable to reproduce the same build warnings following the same build steps in docker locally with CircleCI's
cimg/node:lts
container. The only differences between my setup and CircleCI's are the container runtime and that I don't have yarn dependencies cached.I can see if I can reproduce the same warnings and debug
pkg
, but if y'all have seen this before and know a quick fix then I'd be grateful. Thanks again for checking this out!The text was updated successfully, but these errors were encountered: