-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Failing to execute correct node file #538
Comments
I had this issue as well ( Setting |
Hi @Gabe-Ambrosio, we will take a look at this, thanks for your report. |
Hello everyone. The issue comes from these lines. Internally it uses spawn method to execute it. But toolcache node versions are not compatible with alpine that is why the command getting error on the process level and it produces the issue. We prepared a pull request to fix it #540. But as temporary workaround for alpine images you can remove node-version input, because it does not affect installed node version. |
Hi @vsafonkin , I just wanted to say thank you for the prompt response and for your team's help in fixing the issue! |
Hello @Gabe-Ambrosio. The fix was merged to the main branch. Could you please confirm that it works as expected ? |
Hi @dmitry-shibanov , yep it looks like that fixed it! And just to be sure, I pinned the latest commit SHA when I used the action like this:
And it successfully setup node without a problem with this output:
|
Hello @Gabe-Ambrosio. Thank you for response. I'll prefer to keep the issue open until new release. |
@dmitry-shibanov, do you have an ETA for the release? Thanks in advance for maintaining it. |
Hello everyone. We released a new version and updated the major tag with fix. Could you please confirm that everything works as expected ? |
I can confirm the new release fixed the issue. Many thanks for the quick hot-fix! |
Получите Outlook для Android<https://aka.ms/AAb9ysg>
…________________________________
From: Daniel G. Aubert ***@***.***>
Sent: Friday, July 15, 2022 5:07:24 PM
To: actions/setup-node ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [actions/setup-node] Failing to execute correct node file (Issue #538)
I can confirm the new release fixed the issue. Many thanks for the quick hot-fix!
—
Reply to this email directly, view it on GitHub<#538 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AS7HKF3FQ3EK3K56NZ472C3VUFWBZANCNFSM53IF2YLA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hello @dgaubert. Thank you for your response. For now I'm going to close the issue. If you have any concerns feel free to ping us. |
Bumps [typescript](https://github.com/Microsoft/TypeScript) from 5.1.6 to 5.2.2. - [Release notes](https://github.com/Microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v5.1.6...v5.2.2) --- updated-dependencies: - dependency-name: typescript dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Description:
When this action is run on actions/setup-node@v3.4.0 it fails to execute node with:
Action version:
actions/setup-node@v3.4.0
Platform:
Runner type:
Tools version:
yarn v1.22.19
node 14.20.0
Repro steps:
Adding an action with:
Will trigger the issue.
Expected behavior:
I expect the install to succeed without any errors.
Actual behavior:
The installation fails when it tries to execute the node executable, specifically running the command:
Edit:
It also looks like this is only occurring with the docker container:
The text was updated successfully, but these errors were encountered: