Zeppelin installation error

[wallyxie]

Hi all,
I am getting the following error:

>truffle install zeppelin
Error: Could not find object at hash 'QmYt6ZfD1VNmKp85TeteEcsgaxHzP2gTSKupHxHMVgcHYb' in 5000ms
    at Timeout._onTimeout (/usr/local/lib/node_modules/truffle/node_modules/ethpm/lib/hosts/ipfshost.js:47:14)
    at ontimeout (timers.js:386:14)
    at tryOnTimeout (timers.js:250:5)
    at Timer.listOnTimeout (timers.js:214:5)

Has anyone had experience with this?

[frangio]

It's an issue with IPFS, the storage used for the Ethereum Package Registry.

I recommend installing via npm for now: npm install zeppelin-solidity.

[wallyxie]

Hmm, after I execute npm install zeppelin-solidity I get the following error: dhcp-v229-197:eqc-token huax$ npm install zeppelin-solidity npm ERR! Darwin 15.6.0 npm ERR! argv "/usr/local/Cellar/node/7.10.0/bin/node" "/usr/local/bin/npm" "install" "zeppelin-solidity" npm ERR! node v7.10.0 npm ERR! npm v4.2.0 npm ERR! code ENOSELF npm ERR! Refusing to install package with name "zeppelin-solidity" under a package npm ERR! also called "zeppelin-solidity". Did you name your project the same npm ERR! as the dependency you're installing?

…

On Fri, May 5, 2017 at 11:02 AM, Francisco Giordano < ***@***.***> wrote: It's an issue with IPFS, the storage used for the Ethereum Package Registry. I recommend installing via npm for now: npm install zeppelin-solidity. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZyd_DYIT2VOBtD1SJUBY_FoQEGirhviks5r22QkgaJpZM4NRacj> .

[maraoz]

Just reported this on truffle, FYI: trufflesuite/truffle#378

[maraoz]

Another occurrence here: #96 (comment)

[madmartian5]

Having same issue on Mac OSX

[maraoz]

@notsodirewolf @amexperts @ProphetDaniel @frangio just published a new release of the framework. Can you attempt to install it again and report if you have any problems?
Just run truffle install zeppelin in your project. Thanks!

[madmartian5]

@maraoz - same problem for me I am afraid.

[dukei]

It does not help, still the same error.

Error: Could not find object at hash 'QmPhHVUuwMkkGMg7TWQw7eFANvTrWugpeXqQ7SgkawPN2b' in 5000ms

Still https://ipfs.io/ipfs/QmPhHVUuwMkkGMg7TWQw7eFANvTrWugpeXqQ7SgkawPN2b is available but could not be retrieved by truffle

[wallyxie]

Me too, still same error.

…

On Wed, May 10, 2017 at 8:53 AM, Dmitry Kochin ***@***.***> wrote: It does not help, still the same error. Error: Could not find object at hash 'QmPhHVUuwMkkGMg7TWQw7eFANvTrWugpeXqQ7SgkawPN2b' in 5000ms Still https://ipfs.io/ipfs/QmPhHVUuwMkkGMg7TWQw7eFANvTrWugpeXqQ7SgkawPN2b is available but could not be retrieved by truffle — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZyd_FbrOlaUNP1wNSq3p0iKrrKz4ZuLks5r4d1qgaJpZM4NRacj> .

[maraoz]

Damn. We'll have to revert to npm for the time being then :(

[maraoz]

@notsodirewolf @amexperts @ProphetDaniel @frangio Thanks a bunch for your patience. We've reverted to npm for now. Can you check the new installation instructions below work for you?

https://github.com/OpenZeppelin/zeppelin-solidity#getting-started

@tcoulter I'm sad to do this but I think you understand. We loved being early adopters of ethpm and we'll be eager to jump back to using it once it's reliable. :)

[tcoulter]

Absolutely understand. Once the issues are figured out I'd recommend deploying on both EthPM and NPM to reach the widest audience. Additionally, I envision the internals of EthPM will change once SWARM is complete and file persistence is economically guaranteed. I'm continuing to look at this issue and will let you know what I find.

…

On Fri, May 12, 2017, 8:16 AM Manuel Aráoz ***@***.***> wrote: @notsodirewolf <https://github.com/notsodirewolf> @amexperts <https://github.com/amexperts> @ProphetDaniel <https://github.com/prophetdaniel> @frangio <https://github.com/frangio> Thanks a bunch for your patience. We've reverted to npm for now. Can you check the new installation instructions below work for you? https://github.com/OpenZeppelin/zeppelin-solidity#getting-started @tcoulter <https://github.com/tcoulter> I'm sad to do this but I think you understand. We loved being early adopters of ethpm and we'll be eager to jump back to using it once it's reliable. :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFp1W4lG_a3u_biGfbkZVf9cy_xMkdKks5r5HfngaJpZM4NRacj> .

[maraoz]

Any luck guys?

[tcoulter]

Yep. I've isolated the issue, but to fix it will require some coding (which I'm working on now).

Background: I was wrong. The issue we're having with Zeppelin wasn't the issue where data was lost. The results of the issue looked the same at first glance, but instead it was a combination of smaller issues.

• The first issue is that ethpm-js has a download timeout of 5 seconds per file, and if the file takes longer than five seconds to download, it bails, resulting in the error you guys are seeing.
• The second issue is that, for some reason (I'm still trying to figure it out) the ipfs-api-js module ethpm-js uses to download IPFS files is suuuuuper slow, taking more than five seconds to resolve a file. That same file, when downloaded over http, is nearly instant.

Now some technical details: Because IPFS URIs can denote files OR directories of files (:grumble grumble:), in order to be up to spec I need to now walk the IPFS directory and download all the individual files over http. ipfs-api-js was doing this for me, but I'm ditching it in favor of downloading files the speedy way.

So TL;DR: Problem isolated, but still working on code to get around it. Oh and no Zeppelin data was lost.

[madmartian5]

That seems to work. But just a note it is installing into contracts folder now. :)

[tcoulter]

So you guys know: The issue has been fixed on Truffle v3.2.3. You can get the latest version by uninstalling and then reinstalling Truffle. Cheers! Thanks for the reports, and appreciate your patience.

[wallyxie]

Thank you!

…

On May 16, 2017 1:14 PM, "Tim Coulter" ***@***.***> wrote: So you guys know: The issue has been fixed on Truffle v3.2.3. You can get the latest version by uninstalling and then reinstalling Truffle. Cheers! Thanks for the reports, and appreciate your patience. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZyd_KT_OCg1VriHdL0mAh740ZU7jC2Eks5r6gOTgaJpZM4NRacj> .