-
Notifications
You must be signed in to change notification settings - Fork 110
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
getaddrinfo EAI_AGAIN github.com in electron@11.0.3~postinstall #173
Comments
Since it's a modern electron which probably uses |
That worked! Thanks! |
Is --xdg-layout something that should be on by default now?
…On Thu, Dec 10, 2020, 9:32 AM xcffl ***@***.***> wrote:
Closed #173 <#173>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#173 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM4YSJ22DQSGBREQZLSBB3SUDSZJANCNFSM4UT4XRRQ>
.
|
@refi64 Looks like it. But it would be a breaking change for existing apps with older electron. Maybe print a warning when modern electron is detected, but xdg-layout not enabled? |
@gasinvein
|
@proletarius101 I think npm/yarn doesn't make difference here, the error as @xcffl reported originates from a postinstall script, not from the package manager. |
@proletarius101 Your error in flathub/flathub#2086 comes from |
Well I did it, as shown above. |
Can you please point me to the exact errors you're getting?
It comes from node-gyp unable to find node headers, and it's a different one from what was reported in this issue. |
Yes. I faced two issues... keytar is the first one. Another is what was reported in this issue. I can't bypass both, although the keytar one (as shown in the build server log) could be bypassed locally by removing this step. |
You shouldn't remove this step, otherwise keytar likely won't work (node abi versions must match for native modules). Better figure out why node-gyp doesn't pick up cached headers. |
Obviously all three |
|
That's right. But |
Oh, I see. It's |
Dest |
Well, that didn't work. But I found a solution: |
Just to add another note here, in case someone meet the same problem. If you see electron-builder triggers
which requires internet access, the cause is some of your |
I generated a
generated-sources.json
for https://github.com/yang991178/fluent-reader, and wrote the build yaml as per the sample. But when it runs'npm install --offline --prefix=fluent-reader --verbose --cache=$FLATPAK_BUILDER_BUILDDIR/flatpak-node/npm-cache'
, it raises an error:The build yaml file:
The text was updated successfully, but these errors were encountered: