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

Error can not install #67

Open
zeroXBami opened this issue Aug 31, 2018 · 54 comments
Open

Error can not install #67

zeroXBami opened this issue Aug 31, 2018 · 54 comments

Comments

@zeroXBami
Copy link

Hi,

I am trying to install ethereumjs-abi but always got this issues:
npm ERR! code 1
npm ERR! Command failed: /usr/local/bin/git clone -q https://github.com/ethereumjs/ethereumjs-abi.git /Users/trnhgquan/.npm/_cacache/tmp/git-clone-e6ae2501
npm ERR! /Users/trnhgquan/.npm/_cacache/tmp/git-clone-e6ae2501/.git: Permission denied
npm ERR!

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/trnhgquan/.npm/_logs/2018-08-31T16_15_05_558Z-debug.log

Does anyone here can help me to fix?

Thanks.

@holgerd77
Copy link
Member

You doesn't seem to have the proper rights to write in your given directory. This is nevertheless no abi library related issue, will close.

@bloodybit
Copy link

I faced the same problem and apparently there is a file that needs to be downloaded from git in "git ssh mode" not via https. Adding my github identity with ssh-add solved my issue. I don't think the pubkey is actually checked, it just needs to be non null.

@Resoguy
Copy link

Resoguy commented Mar 26, 2021

I am getting this Permission denied error on cypress github action while installing dependencies with the npm ci command

This is where the error occurs
/usr/bin/git ls-remote -h -t ssh://[email protected]/ethereumjs/ethereumjs-abi.git

This error makes the project untestable on github action. Any idea to how solve?

Here is the full log:

/usr/local/bin/npm ci
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://[email protected]/ethereumjs/ethereumjs-abi.git
npm ERR! 
npm ERR! Warning: Permanently added the RSA host key for IP address '140.82.113.3' to the list of known hosts.
npm ERR! [email protected]: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR! 
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR! 
npm ERR! exited with error code: 128

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2021-03-26T17_17_00_879Z-debug.log
Error: The process '/usr/local/bin/npm' failed with exit code 1

@Andrea-Dispe
Copy link

I am getting this Permission denied error on cypress github action while installing dependencies with the npm ci command

This is where the error occurs
/usr/bin/git ls-remote -h -t ssh://[email protected]/ethereumjs/ethereumjs-abi.git

This error makes the project untestable on github action. Any idea to how solve?

Here is the full log:

/usr/local/bin/npm ci
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://[email protected]/ethereumjs/ethereumjs-abi.git
npm ERR! 
npm ERR! Warning: Permanently added the RSA host key for IP address '140.82.113.3' to the list of known hosts.
npm ERR! [email protected]: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR! 
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR! 
npm ERR! exited with error code: 128

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2021-03-26T17_17_00_879Z-debug.log
Error: The process '/usr/local/bin/npm' failed with exit code 1

I am getting the same error on Mac and Ubuntu. Have you solved this issue @Resoguy

@bloodybit
Copy link

I think you can solve it this way: #67 (comment)

@Andrea-Dispe
Copy link

I think you can solve it this way: #67 (comment)

Thank you but I was able to solve this by updating npm to the latest version.

@RadioJulius
Copy link

I've noticed this occasionally happen when adding a new package with yarn. It will revert from the working:

"resolved": "https://registry.npmjs.org/ethereumjs-abi/-/ethereumjs-abi-0.6.8.tgz"

to the non-working:

"resolved": "git+ssh://[email protected]/ethereumjs/ethereumjs-abi.git#ee3994657fa7a427238e6ba92a84d0b529bbcde0"

Manually switching back fixes this headache for me.

@knzeng-e
Copy link

I've noticed this occasionally happen when adding a new package with yarn. It will revert from the working:

"resolved": "https://registry.npmjs.org/ethereumjs-abi/-/ethereumjs-abi-0.6.8.tgz"

to the non-working:

"resolved": "git+ssh://[email protected]/ethereumjs/ethereumjs-abi.git#ee3994657fa7a427238e6ba92a84d0b529bbcde0"

Manually switching back fixes this headache for me.

+1 this comment resolved my issue. Thanks !

@preconfxsd
Copy link

I faced the same problem and apparently there is a file that needs to be downloaded from git in "git ssh mode" not via https. Adding my github identity with ssh-add solved my issue. I don't think the pubkey is actually checked, it just needs to be non null.

Can you tell me how did you add your identity? Should I add it into workflow yaml file?

@creazy231
Copy link

Same problem using Vercel Deployment

laurensV added a commit to effectai/force-frontend that referenced this issue Nov 19, 2021
kartojal added a commit to aave/aave-v3-core that referenced this issue Nov 22, 2021
Generate a random SSH key at runtime to be able to ethereumjs-abi dependency from Github.

ethereumjs/ethereumjs-abi#67 (comment)
@valle-xyz
Copy link

I face this issue now.

@holgerd77
Copy link
Member

@Valentin-Seehausen hi there, I did a test clone + npm i on https://github.com/effectai/force-frontend-new - assuming that that's the repository from where your issue originated - but I couldn't even find the dependency, npm ls ethereumjs-abi is giving me nothing.

Can you give a short context description where the ethereumjs-abi dependency is actually coming from in your context?

@holgerd77
Copy link
Member

And for everyone reading along here: while we have deprecated this package if there is something with reasonable effort we can do here from our side we can very well do a bugfix release here.

It's generally helpful if you provide more context on where are you getting your errors. What Node version are you using? Are you using the ethereumjs-abi dependency directly or is it installed via another dependency? Optimally provide some reproduceable code example (or eventually some CLI command lineup in this context).

Thanks!

Will reopen this issue for now until this is settled in some way.

@holgerd77 holgerd77 reopened this Nov 29, 2021
@djmbritt
Copy link

We also encountered this issue last week, it was a deprecated dependency from WalletConnect.
This was still the 1.0 version of WalletConnect.
We dropped support for WalletConnect for now.

@holgerd77
Copy link
Member

Just to confirm: are there more people here where this problem is coming from the WalletConnect library?

@valle-xyz
Copy link

Yes, it originated from the WalletConnect library. I solved the issue by deleting my yarn.lock and reinstall.
Sorry that I cannot help to reproduce it. Super service, thanks a lot!

@Kamikozz
Copy link

@holgerd77

  • it is happened for me on Node v14.17.3
  • Installed via another dependency
  • Using npm

image

└─┬ @amfi/[email protected]
  └─┬ @walletconnect/[email protected]
    └─┬ [email protected]
      └─┬ [email protected]
        └── [email protected] (git+ssh://[email protected]/ethereumjs/ethereumjs-abi.git#ee3994657fa7a427238e6ba92a84d0b529bbcde0)

I have just created new app on heroku, then made a setup via github repository to deploy, and then it showed me these logs

Spoiler warning
-----> Building on the Heroku-20 stack
-----> Using buildpack: mars/create-react-app
-----> React.js (create-react-app) multi app detected
=====> Downloading Buildpack: https://github.com/heroku/heroku-buildpack-multi.git
=====> Detected Framework: Multipack
=====> Downloading Buildpack: https://github.com/heroku/heroku-buildpack-nodejs.git
=====> Detected Framework: Node.js
       
-----> Creating runtime environment
       
       NPM_CONFIG_LOGLEVEL=error
       NODE_VERBOSE=false
       NODE_ENV=production
       NODE_MODULES_CACHE=true
       
-----> Installing binaries
       engines.node (package.json):  unspecified
       engines.npm (package.json):   unspecified (use default)
       
       Resolving node version 14.x...
       Downloading and installing node 14.18.3...
       Using default npm version: 6.14.15
       
-----> Restoring cache
       - node_modules
       
-----> Installing dependencies
       Installing node modules
       npm ERR! Error while executing:
       npm ERR! /usr/bin/git ls-remote -h -t ssh://[email protected]/ethereumjs/ethereumjs-abi.git
       npm ERR! 
       npm ERR! Host key verification failed.
       npm ERR! fatal: Could not read from remote repository.
       npm ERR! 
       npm ERR! Please make sure you have the correct access rights
       npm ERR! and the repository exists.
       npm ERR! 
       npm ERR! exited with error code: 128
       
       npm ERR! A complete log of this run can be found in:
       npm ERR!     /tmp/npmcache.3QAnL/_logs/2022-01-19T07_02_45_160Z-debug.log
-----> Build failed
       
       We're sorry this build is failing! You can troubleshoot common issues here:
       https://devcenter.heroku.com/articles/troubleshooting-node-deploys
       
       Some possible problems:
       
       - Node version not specified in package.json
         https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
       
       Love,
       Heroku
       
 !     Push rejected, failed to compile React.js (create-react-app) multi app.
 !     Push failed

No matter what it says, there is no problem with buildpack, it's just something that is here git ls-remote -h -t ssh://[email protected]/ethereumjs/ethereumjs-abi.git

Anyway, you can try this command locally and it will show you this error.

But, if I run my project locally, everything is working (this could be the GitHub policy about SSH, dunno)

// SOLVED: using yarn instead of npm will give you the pleasure

@nbeuchat
Copy link

In my case, the problem comes from the @web3-onboard/walletlink package.

@ayudh37
Copy link

ayudh37 commented Mar 24, 2022

I had this issue as well, using when using @walletconnect/web3-provider and using npm as the package manager.

I deleted package-lock.json and node_modules and used yarn to install the modules. Verified that the resolve url for the dependency ethereumjs-abi begins with https:// instead of git+ssh:// in yarn.lock and everything works now

@mdarche
Copy link

mdarche commented Apr 19, 2022

For anybody struggling with this issue using pnpm, I fixed by adding an override to my root package.json:

"pnpm": {
    "overrides": {
      "ethereumjs-abi": "https://registry.npmjs.org/ethereumjs-abi/-/ethereumjs-abi-0.6.8.tgz"
    }
  }

Reference: https://pnpm.io/package_json#pnpmoverrides

@georgeperry1
Copy link

I was having this issue specifically when installing and deploying within an AWS Amplify build pipeline. Of the suggested fixes, moving from npm to yarn was the only thing that solved it for me.

@akorede12
Copy link

Same problem using Vercel Deployment

Yes I'm having this issue now trying to deploy my project on vercel. how do you solve the issue when deploying to vercel?

@Hazelwu2
Copy link

Same problem using Vercel Deployment

Yes I'm having this issue now trying to deploy my project on vercel. how do you solve the issue when deploying to vercel?

I'm using vercel cicd to deploy my project, has the same problem.
remove package.lock & yarn.lock, and yarn install reinstall again, that's work for me!

@rstellar
Copy link

rstellar commented Jun 27, 2022

Having this issue using npm ci via Cyclic.sh

@dcsan
Copy link

dcsan commented Oct 6, 2022

ok so the solution of deleting the git+ssh entry and manually hacking the yarn.lock and reinstalling seems to work.
but how fragile is this?
what are the cases that will cause the yarn.lock to be completely rebuilt?

@dcsan
Copy link

dcsan commented Oct 6, 2022

also, what can we recommend upstream packages to do that depend on this? even tho this package is deprecated as of a year ago, it seems very recent other modules still depend on it.

my deps path:

  • "wagmi#@coinbase#wallet-sdk#eth-json-rpc-filters#eth-json-rpc-middleware#eth-sig-util" depends on it

this issue says in fact that coinbase/wallet is the RIGHT thing to use...

blocknative/web3-onboard#885

@holgerd77
Copy link
Member

Hi there,
we are very open to do a quick bugfix release on our side if this helps, even if this package is deprecated, I just haven't identified if we can do something on our side.

If you follow-up the dependency path and find the right place where to post the issue "on the other side" feel free to mention me, then we can coordinate on how to fix this and see if we can also do something from the EthereumJS side of things.

@dcsan
Copy link

dcsan commented Oct 6, 2022

thanks @holgerd77 someone tracked the deps tree here for wagmi.
not sure how you could fix it at this end - can you replace the module/version and replace the git with https?

wevm/wagmi#1027

@masterbd
Copy link

masterbd commented Oct 20, 2022

What I've done to fix this on local and CI:

Replace in package-lock.json:
"ethereumjs-abi": "git+https://github.com/ethereumjs/ethereumjs-abi.git"
or
"ethereumjs-abi":"git+ssh://[email protected]/ethereumjs/ethereumjs-abi.git"
With:
"ethereumjs-abi": "^0.6.8"

Replace in package-lock.json:
"resolved": "git+https://[email protected]/ethereumjs/ethereumjs-abi.git#ee3994657fa7a427238e6ba92a84d0b529bbcde0"
or:
"resolved": "git+ssh://[email protected]/ethereumjs/ethereumjs-abi.git#ee3994657fa7a427238e6ba92a84d0b529bbcde0"
With:
"resolved": "https://registry.npmjs.org/ethereumjs-abi/-/ethereumjs-abi-0.6.8.tgz"

Replace in package-lock.json

"ethereumjs-abi": {
      "version": "git+https://[email protected]/ethereumjs/ethereumjs-abi.git#ee3994657fa7a427238e6ba92a84d0b529bbcde0",
      "from": "ethereumjs-abi@git+https://github.com/ethereumjs/ethereumjs-abi.git"
      ....
}

With:

"ethereumjs-abi": {
      "version": "^0.6.8",
      "resolved": "https://registry.npmjs.org/ethereumjs-abi/-/ethereumjs-abi-0.6.8.tgz",
      ....
}

@arshamg
Copy link

arshamg commented Oct 27, 2022

Is there a non-fragile/definitive solution to this using npm?

@eth0izzle
Copy link

Yes @arshamg. Delete your package-lock.json and yarn.lock files then simply add the below to your package.json. This will work regardless of npm/yarn.

  "resolutions": {
    "ethereumjs-abi": "https://registry.npmjs.org/ethereumjs-abi/-/ethereumjs-abi-0.6.8.tgz"
  },

@arshamg
Copy link

arshamg commented Nov 1, 2022

Thanks @eth0izzle

@lazy1523
Copy link

lazy1523 commented Nov 6, 2022

Why this damn problem hasn't been solved and it's holding the crypto industry back

@acolytec3
Copy link

Can someone on this thread who's encountered the issue provide an example repo where this issue occurs so I can reproduce locally? I've looked at the various dependencies in the stack that reference the old version of ethereumjs-abi that seems to be causing the issue and I'm not able to reproduce it. If I can indeed validate the issue (and which setup is causing it to break), I can try and work with whichever dependent module is causing things to break to update their deps. If I had to guess, I'd say it's most likely the eth-json-rpc-filters module since its most current version references older other libraries that in turn lead down to that git referenced version of ethereumjs-abi.

@aahna-ashina
Copy link

Solved by running yarn upgrade

@lucasuema
Copy link

Solved by running yarn upgrade

Thank you! 👹 - It solved it for me too.

@LintonAchmad
Copy link

LintonAchmad commented Nov 25, 2022

Had the same issue, switching to yarn from npm did the trick.

1 - Install yarn : npm install -g yarn
2 - Delete package lock file from root of project.
3 - Run yarn in root of project.

graphicmist pushed a commit to picklelabs-xyz/tijori that referenced this issue Nov 28, 2022
kewka added a commit to cruzocards/cruzo-contracts that referenced this issue Dec 9, 2022
@algmir
Copy link

algmir commented Dec 13, 2022

I try it by aboved answers and can not solve it , it cost about me 1.5days. I use next , it worked, share the website to help others.
npm i @truffle/hdwallet-provider@next
https://stackoverflow.com/questions/71396470/cannot-install-npm-package-code-128-an-unknown-git-error-occurred

kewka added a commit to cruzocards/cruzo-contracts that referenced this issue Dec 13, 2022
@Soecka
Copy link

Soecka commented Dec 14, 2022

For anybody struggling with this issue using pnpm, I fixed by adding an override to my root package.json:

"pnpm": {
    "overrides": {
      "ethereumjs-abi": "https://registry.npmjs.org/ethereumjs-abi/-/ethereumjs-abi-0.6.8.tgz"
    }
  }

Reference: https://pnpm.io/package_json#pnpmoverrides

I upgraded pnpm from 6.9 to 7.18 and then the bug was resolved

@AllanBUSI
Copy link

Même problème avec Vercel Deployment

Oui, j'ai ce problème en essayant de déployer mon projet sur vercel. comment résolvez-vous le problème lors du déploiement sur vercel ?

J'utilise Vercel Cicd pour déployer mon projet, j'ai le même problème. supprimer package.lock& yarn.lock, et yarn installréinstaller à nouveau, ça marche pour moi !

thanck you

@0xabz
Copy link

0xabz commented May 23, 2023

Yes @arshamg. Delete your package-lock.json and yarn.lock files then simply add the below to your package.json. This will work regardless of npm/yarn.

  "resolutions": {
    "ethereumjs-abi": "https://registry.npmjs.org/ethereumjs-abi/-/ethereumjs-abi-0.6.8.tgz"
  },

nice!!!!!!!! fix this problem!!! thank you!!!

@arsqu
Copy link

arsqu commented Aug 3, 2023

I solved this issue for following. Remove "resolved": "git+ssh://[email protected]/ethereumjs/ethereumjs-abi.git#ee3994657fa7a427238e6ba92a84d0b529bbcde0" from my yarn.lock and re-run yean install, then yarn.lock was updated to git+https url.

It's works for me, but I don't know if this is right way.

thanks, it works for me

@terryjiang2020
Copy link

I have this same problem when I was trying to build my project via AWS Ampify. It is serverless so I guess there's no way for me to add my ssh key there. (The repo I used is a private repo of mine, though.) Does anyone have the solution for a serverless service like that?

@blazejkrzak
Copy link

I had this problem when I logged to the server via SSH.
I forgot to forward my agent via -A flag.

ssh -A $user:$host
I leave it here, probably for myself in the future and maybe for the others that encounter this issue

grishick added a commit to HEO-Platform/heo-web that referenced this issue Jan 31, 2024
Remove package-lock.json because it's presence breaks the build due to this bug: ethereumjs/ethereumjs-abi#67 (comment)
grishick added a commit to HEO-Platform/heo-web that referenced this issue Jan 31, 2024
Add package-lock.json to .gitignore as a workaround for this bug ethereumjs/ethereumjs-abi#67 (comment)
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

No branches or pull requests