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

Pretest command fails to install and run ipfs #1833

Open
c0rv0s opened this issue Mar 1, 2021 · 1 comment
Open

Pretest command fails to install and run ipfs #1833

c0rv0s opened this issue Mar 1, 2021 · 1 comment
Labels
🐛 bug An unexpected behavior of the API

Comments

@c0rv0s
Copy link
Contributor

c0rv0s commented Mar 1, 2021

🐛 Bug Report

Running yarn pretest causes the error to happen:

(node:5581) UnhandledPromiseRejectionWarning: Error: Error: Command failed with exit code 1: npm install [email protected] --save
npm WARN deprecated [email protected]: The 'go-ipfs' module is now a drop-in replacement for 'go-ipfs-dep', please use that instead
npm ERR! code 1
npm ERR! path /Users/nathanaelmueller/Documents/dOrg/aragon/aragon-cli/.tmp/setup/ipfs-project/node_modules/go-ipfs
npm ERR! command failed
npm ERR! command sh -c node link-ipfs.js
npm ERR! ipfs binary not found. maybe go-ipfs-dep did not install correctly?

Have you read the Contributing Guidelines on issues?

  • [ .] Yes

To Reproduce

  1. run yarn pretest

Expected behavior

I expected IPFS to install in the temp repo and the daemon to start

Actual Behavior

IPFS failed to install and the error mentioned above was logged to the console.

Context

Mainnet or testnet?

Devchain

Organization

(Enter the URL or ENS name of your organization.)

Environment

  • OS and OS version: macOS 11.2.2
  • Browser and browser version: N/A
  • Add any other context about the problem here.

Reproducible Demo

(Paste the link to an example repo, and exact instructions to reproduce the issue.)

@c0rv0s c0rv0s added the 🐛 bug An unexpected behavior of the API label Mar 1, 2021
@JeremyConnor
Copy link
Contributor

@c0rv0s I have solved this issue, I can create a pull request if you want (if the problem is still not taken care of in any of the branches)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug An unexpected behavior of the API
Projects
None yet
Development

No branches or pull requests

2 participants