go-ipfs | IPFS implementation in Go | Storage library

Bash variables expand inside quoted " strings.

Solution is

This is a Go 1.16 issue which is currently investigated in golang/go issue 44529

It includes Jay Conrod's comment:

go mod tidy and go get may both hit the network to look up imported packages that aren't provided by any required module.
If a module is replace locally, the go command will look there first, but I think it may still go out to the network for other prefixes of the module path.

Instead, you can add a requirement on a non-existent version while replacing that version:

The context is a Golang context which helps track things like deadlines or cancellations of operations. In this case because you're making an HTTP call to your local IPFS daemon it's possible you might want to cancel the function because it's taking too long or your application no longer cares and the context lets you handle that use case.

You can get a background context (i.e. lives forever and is never cancelled) via context.Background(). If you want to set a timeout on it you can pass that background context to context.WithTimeout. Checkout the Golang docs on context for more information.

Yes, you can use go-ipfs as a library. There are some examples here https://github.com/ipfs/go-ipfs/tree/90a573354af23e361da87a29f7bafc459967c070/docs/examples. Basically you need to import go-ipfs (and some of its subpackages) instead of go-ipfs-api.

As Stebalien said in this Github issue, it's a go's expected behavior of Reader.

Refer to the third paragraph of this documentation

When Read encounters an error or end-of-file condition after successfully reading n > 0 bytes, it returns the number of bytes read. It may return the (non-nil) error from the same call or return the error (and n == 0) from a subsequent call. An instance of this general case is that a Reader returning a non-zero number of bytes at the end of the input stream may return either err == EOF or err == nil. The next Read should return 0, EOF.