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

[Infra]: Test check CI failed to execute because of npm package not found #42005

Closed
reitowo opened this issue Apr 30, 2024 · 3 comments · Fixed by #42006
Closed

[Infra]: Test check CI failed to execute because of npm package not found #42005

reitowo opened this issue Apr 30, 2024 · 3 comments · Fixed by #42006
Assignees

Comments

@reitowo
Copy link

reitowo commented Apr 30, 2024

The test CI seems failing because of some packages not found.

https://app.circleci.com/pipelines/github/electron/electron/80530/workflows/88430b3b-186b-41df-af9e-bc31e0616c28/jobs/1707653?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link&utm_content=summary

warning package.json: No license field
warning electron-test-main@0.1.0: No license field
[1/4] Resolving packages...
warning Resolution field "xml2js@0.5.0" is incompatible with requested version "xml2js@^0.4.17"
warning Resolution field "minimist@1.2.7" is incompatible with requested version "minimist@~0.0.1"
[2/4] Fetching packages...
error https://registry.yarnpkg.com/@nut-tree/nut-js/-/nut-js-3.1.2.tgz: Request failed "404 Not Found"
error https://registry.yarnpkg.com/@nut-tree/libnut-darwin/-/libnut-darwin-2.5.2.tgz: Request failed "404 Not Found"
error https://registry.yarnpkg.com/@nut-tree/libnut-linux/-/libnut-linux-2.5.2.tgz: Request failed "404 Not Found"
error https://registry.yarnpkg.com/@nut-tree/libnut-win32/-/libnut-win32-2.5.2.tgz: Request failed "404 Not Found"
error https://registry.yarnpkg.com/@nut-tree/node-mac-permissions/-/node-mac-permissions-2.2.1.tgz: Request failed "404 Not Found"
info fsevents@2.3.3: The platform "linux" is incompatible with this module.
info "fsevents@2.3.3" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
error An unexpected error occurred: "ENOENT: no such file or directory, open '/home/builduser/.cache/yarn/v4/npm-@nut-tree-libnut-darwin-2.5.2-83f091969912bf0d808ecebbab40423f6d30a660/node_modules/@nut-tree/libnut-darwin/.yarn-metadata.json'".
info If you think this is a bug, please open a bug report with the information provided in "/home/builduser/project/src/electron/spec/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
✗ Failed to yarn install in '/home/builduser/project/src/electron/spec'
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: exit status 123
Error: exit status 123

Exited with code exit status 1
@reitowo reitowo changed the title [Infra] Test check CI failed to execute because of npm package not found [Infra]: Test check CI failed to execute because of npm package not found Apr 30, 2024
@ckerr
Copy link
Member

ckerr commented Apr 30, 2024

nut-tree/nut.js#587

https://nutjs.dev/blog/i-give-up

All of my packages around nut.js will cease to exist publicly on npm. Ready-to-use packages will only be available through the private nut.js package registry, which requires an active subscription to be used.

The GitHub repo will remain public, so if you want to continue using nut.js on your own, you'll have to take care of building, testing and hosting packages yourself.

If you want to save yourself some time and work, you should grab a license today, because prices will also increase with the release of additional plugins. Existing subscribers will not be affected by this increase.

@ckerr
Copy link
Member

ckerr commented Apr 30, 2024

Happily for us, this dependency is only to enable a test that was added by @samuelmaddock for the feature he added in #41127. In the immediate term to unblock everything, we should remove the dependency & disable/remove the test, and then we should find an open source alternative that we can replace it with.

@reitowo
Copy link
Author

reitowo commented Apr 30, 2024

Sad to know a open source maintainer broke heart :(

Anyway it blocks my PR for now. I'll wait for you guys make changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants