Update dependencies of test/dependencies/go.mod

[schomatis]

Checklist

• This is a bug report, not a question. Ask questions on discuss.ipfs.io.
• I have searched on the issue tracker for my bug.
• I am running the latest go-ipfs version or have an issue updating.

Installation method

built from source

Version

..

Config

..

Description

I'm not sure the rationale for this separate go.mod file but we should update its dependencies to match as close as possible the main one (at least its go version).

[BigLep]

@schomatis : feel free to take this one on.

[schomatis]

@BigLep I'm temporarily un-assigning myself as I'm sinking too much time without any concrete progress. Will need input on the proper way to approach this. My last fail attempt is in #8478.

More background: I'm failing to do a simple go get -u ./... for this handful of packages as there is an inconsistency in the libp2p and libp2p-core latest minor versions that make this command fail (see libp2p/go-libp2p#1196 for more details on that). Updating each module manually (as I was attempting in the above PR) starts to hit a lot dependency entanglements where I can never reach a checkpoint where I can successfully build all dependencies and hence I'm left at a state where I'm not sure if I'm making progress at all by the updates I'm doing.

[aschmahmann]

Doing go get -u is unlikely to ever be very useful.

If you update the dependencies to match what they are in go-ipfs you should be fine though. You can then do go get {repo}@latest on the non go-ipfs related dependencies to see if you're able to upgrade to them or not (they might be breaking changes not worth upgrading to).

An easy way to do the go-ipfs dependency matching is:

go get github.com/ipfs/go-ipfs@latest
go mod edit -droprequire github.com/ipfs/go-ipfs
go mod tidy

[schomatis]

Re-assigned myself to give Adin's comment a try.

[schomatis]

Working on this again.

[schomatis]

I'm still having many errors updating these dependencies (probably due to my own inexperience with Go modules) so I'm un-assigning myself permanently from this issue as I'm not even sure if I'm making any progress and the ROI is very low.

After running Adin's commands I still have issues with the libp2p core versions, see https://discuss.ipfs.io/t/good-tutorials-for-go-ipfs-library/11924/4.
After that I then have issues with graphsync, but I never have too much information to understand what is happening or what should I do (this is definitively my fault given my inexperience), for example:

$ make test_sharness_deps

graphsync-get/graphsync-get.go:27:2: missing go.sum entry for module providing package github.com/libp2p/go-libp2p (imported by github.com/ipfs/go-ipfs/test/dependencies/graphsync-get); to add:
	go get github.com/ipfs/go-ipfs/test/dependencies/graphsync-get

$ go get github.com/ipfs/go-ipfs/test/dependencies/graphsync-get

# github.com/ipfs/go-ipfs/test/dependencies/graphsync-get
graphsync-get/graphsync-get.go:37:3: undefined: storeutil.LoaderForBlockstore
graphsync-get/graphsync-get.go:38:3: undefined: storeutil.StorerForBlockstore
graphsync-get/graphsync-get.go:43:40: undefined: "github.com/ipld/go-ipld-prime/node/basic".Style

In general the restriction of having a single dependency tree for many independent tools seems to put a lot of pressure on how to make all the pieces fit without (AFAICT) a clear benefit other than maintaining a single go.mod file.