Skip to content
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

[Bug]: spawn openssl ENOENT #35211

Closed
3 tasks done
Coldplayer1995 opened this issue Aug 3, 2022 · 2 comments
Closed
3 tasks done

[Bug]: spawn openssl ENOENT #35211

Coldplayer1995 opened this issue Aug 3, 2022 · 2 comments
Labels

Comments

@Coldplayer1995
Copy link

Preflight Checklist

Electron Version

19.0.1

What operating system are you using?

Windows

Operating System Version

Windows 10

What arch are you using?

x64

Last Known Working Electron version

19.0.1

Expected Behavior

This command should work as expected.

Actual Behavior

No problems in dev environment, once build I am getting above error:
Error:spawn openssl ENOENT

openssl(openssl x509 -pubkey -noout -in ${certPath} -out ${pubKeyPath}, function (err, buffer)

Testcase Gist URL

No response

Additional Information

No response

@codebytere
Copy link
Member

Thanks for reporting this and helping to make Electron better!

Because of time constraints, triaging code with third-party dependencies is usually not feasible for a small team like Electron's.

Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

I'm adding the blocked/need-repro label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.

@codebytere codebytere added blocked/need-repro Needs a test case to reproduce the bug platform/windows 19-x-y labels Aug 4, 2022
@codebytere
Copy link
Member

We haven't gotten a response to our questions in our comment above. With only the information that is currently in the issue, we don't have enough information to take action. In this event, i'm going to go ahead and close this but can reopen should you follow up with more info!

@codebytere codebytere closed this as not planned Won't fix, can't repro, duplicate, stale Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants