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
Added Darwin ARM64 binaries #1594
Conversation
3bfe330
to
e145caa
Compare
e145caa
to
0dedf4a
Compare
376637a
to
832950b
Compare
Any update about that? It's seems one test failed because connection issues. |
569c198
to
009be58
Compare
Would be really good to merge this PR and have prebuilt version on M1 instead of building it from source. |
Hey all! 👋🏻 Whilst I would love to merge this, the generated binaries it produces get caught up with MacOS' quarantine flag, so the it requires you to remove the flag in order for it to be run, which is clearly not going to work from an end-user perspective. I can't tell if it's something I'm doing locally or whether there is some security issue I've missed. Any ideas welcome 🙂 |
Hello, thanks in advance for your efforts. Cheers :) |
3f074ce
to
771fe07
Compare
Hey @adrian-arapiles 👋🏻 I've just rebased the branch so the binaries are built against the latest and I can explain the problem.
I get the following popup: And the following error:
|
@bpasero can you or another member of the VS Code team provide any pointers to @daniellockyer about this? You likely have a pool of experience in dealing with Apple security architecture. I think VS Code depends on the sqlite3 package, right? Presumably at the moment the Darwin ARM64 binary has to be built on the user's machine, in which case it'd surely be a good thing to get this resolved. |
@deepak1556 can you chime in how we build SQLite for ARM. |
I think this only an issue if you are downloading non-notarized executable files from the browser which end up adding the
|
For VSCode the modules are built from source during application package generation in CI (there is no module build in users device, arm64 modules are cross compiled on x64 CI in our case)and the modules also get code signed along with the final package getting notarized. This is different from what is being accomplished in this PR, so expanding on our build process might not be of much help here. |
Oh! Very interesting - it works fine for me using wget. Do you have a reference for why that would be the case with downloading via the browser? I searched all over and never found that |
This seems good news though 🙂 |
- this adds support for supplying Darwin ARM64 prebuilt binaries for node-sqlite3
771fe07
to
117a4cc
Compare
I've merged this and will do some further testing before releasing - thanks all 🙂 |
@daniellockyer please can we also have the binary for Node v14? That is the version currently used by the mtxr/sqltools project which led me here. |
@gjsjohnmurray The binaries only vary on the Node-API version they're built against: https://nodejs.org/api/n-api.html#node-api-version-matrix. We support v3 and v6 right now. If you've got an ARM64 build of Node 14, it should work 🙂 |
Summary: `@redux-devtools/cli` is dependent on the `sqlite3` node package (https://github.com/TryGhost/node-sqlite3). There previously weren't aarch64 binaries available, so `sqlite3` had to be built from scratch which made `yarn cleaninstall` take a while. They recently added prebuilt binaries (TryGhost/node-sqlite3#1594), so we should bump the version to take advantage of this. On my machine this took `yarn cleaninstall` from ~90 seconds to under a minute (~58 seconds). Test Plan: Read through release notes and things should continue to work as expected. NOTE: This is unrelated to the SQLite client DB we use in the `native` app. This SQLite is solely to power Redux dev tools (which still work as expected). Reviewers: tomek, marcin, ginsu, rohan, varun, ashoat Reviewed By: ashoat Subscribers: abosh Differential Revision: https://phab.comm.dev/D5385
Please see this comment: