Build Failure: Running gx install hangs fetching ipfs objects

[vyzo]

I am trying to build go-libp2p in a fresh workspace.
After running make, the obvious next step in building seems to be gx install.
Alas, it hangs while fetching dependencies from ipfs; running with --verbose hangs here:

  - fetching QmZ4Qi3GaRbjcx28Sme5eMH7RQjGkt8wHxt2a65oLaeFEV via ipfs api

[vyzo]

If I C-c the process and restart, it seems go through the previous reference -- only to hang in a different fetch:

  - fetching QmeLQ13LftT9XhNn22piZc3GP56fGqhijuL5Y8KdUaRn1g via ipfs api

[vyzo]

Also, there don't appear to be any artefacts from these fetches in my go workspace.

[vyzo]

Upon further experimentation, it seems that it starts a number of fetches in the background with a non-deterministic process (goroutines problably), resulting in varying fetch print order.
The end result is the same however, it just hangs for a long time

Note: I am not running a local ipfs node.

[vyzo]

Running with a local ipfs node seems to be making progress.

Perhaps running ipfs should be a hard dependency listed in the README?

[vyzo]

An update: it made solid albeit slow progress, until it got stuck installing go-libp2p-loggables.
It's been stuck there for over an hour now:

installing package: go-libp2p-loggables-1.0.7
  - QmRBqJF7hb8ZSpRcMwUt8hNhydWcxGEhtk81HKq6oUwKvs not found locally, fetching into /home/vyzo/src/golang/src/gx/ipfs/QmRBqJF7hb8ZSpRcMwUt8hNhydWcxGEhtk81HKq6oUwKvs
  - fetching QmRBqJF7hb8ZSpRcMwUt8hNhydWcxGEhtk81HKq6oUwKvs via ipfs api

[jbenet]

@whyrusleeping what's going on there? Missing packages?
On Mon, Aug 8, 2016 at 11:18 vyzo notifications@github.com wrote:

An update: it made solid albeit slow progress, until it got stuck
installing go-libp2p-loggables.
It's been stuck there for over an hour now:

installing package: go-libp2p-loggables-1.0.7

• QmRBqJF7hb8ZSpRcMwUt8hNhydWcxGEhtk81HKq6oUwKvs not found locally, fetching into /home/vyzo/src/golang/src/gx/ipfs/QmRBqJF7hb8ZSpRcMwUt8hNhydWcxGEhtk81HKq6oUwKvs
• fetching QmRBqJF7hb8ZSpRcMwUt8hNhydWcxGEhtk81HKq6oUwKvs via ipfs api

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#81 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIcoT5B59__QmqmMfX3oMJqvvhYpqJnks5qdz00gaJpZM4Je_Yu
.

[vyzo]

There seems to be some IPFS routing issue -- the object seems to be resolvable from other locations.

[vyzo]

Restarting the ipfs daemon magically fixed the problem and installation completed!

Closing the issue as there isn't any action that needs to be taken.

[whyrusleeping]

@vyzo what version of ipfs are you using? This is likely the major bug in 0.4.2 that we've fixed in 0.4.3. If you see this sort of thing somewhat frequently, i would recommend trying out the release candidate for 0.4.3

[vyzo]

Aha! I am using ipfs-0.4.2 (it has an ebuild in gentoo, so it was convenient).