Thanks for the advice Bryan.
Sadly I tried using go mod download but I'm still seeing the same problem.
I'm concerned that it might be something environmental.
The module that's been causing me the issue is github.com/jung-kurt/gofpdf
v1.16.2
I tried again but this time with a different module:
go mod download go.elastic.co/[email protected]
This populated the cache with a couple of dozen modules but the only info
file that gets downloaded is
go/pkg/mod/cache/download/go.elastic.co/apm/@v/v1.16.2.info
Then on a whim I cleaned the cache again and ran "go get" on this new
module:
go get go.elastic.co/[email protected]
go: downloading go.elastic.co/apm v1.8.0
go: downloading go.elastic.co/fastjson v1.0.0
go: downloading github.com/santhosh-tekuri/jsonschema v1.2.4
go: downloading github.com/pkg/errors v0.8.1
go: downloading golang.org/x/sys v0.0.0-20191204072324-ce4227a45e2e
go: downloading github.com/elastic/go-sysinfo v1.1.1
go: downloading github.com/armon/go-radix v1.0.0
go: downloading github.com/elastic/go-windows v1.0.0
go: downloading github.com/prometheus/procfs v0.0.3
go: downloading github.com/joeshaw/multierror
v0.0.0-20140124173710-69b34d4ec901
go: downloading howett.net/plist v0.0.0-20181124034731-591f970eefbb
This time all but two of the downloaded modules contained .info files.
I don't get it.
One thing that I did note was that when I go back to using "go get" on the
original module, it caches a number of modules into the but it only
*reports* one:
go get github.com/jung-kurt/[email protected]
go: downloading github.com/jung-kurt/gofpdf v1.16.2
The only .info file that's downloaded is
go\pkg\mod\cache\download\github.com\jung-kurt\gofpdf\@v\v1.16.2.info
I'm wondering if that's hinting at something?
I'm not interested in the info files per se. It's just that we're using our
own module proxy and some of our developers are using GoLand. When GoLand
opens a project it seems to run "go list" on all dependencies and reports
an http 404 on any .info files that it can't download. Because some of our
dependencies don't have .info files, we get the http 404s.
Aside from that the lack of info files doesn't seem to stop us from using
GoLand but all the same I'd rather we fixed the errors.
On Wednesday, 6 January 2021 at 16:21:25 UTC Bryan C. Mills wrote:
> `go mod download` should include `.info` files for the requested
> module(s), or for all dependencies of your module (if you don't give any
> specific modules as arguments).
>
> That said, .info files are not particularly useful in general, and the
> `go` command should probably read them less than in does today; see
> https://golang.org/issue/42723 for details;
>
> On Tuesday, January 5, 2021 at 2:10:05 PM UTC-5 Orson Cart wrote:
>
>> Apologies if this is a dumb question as I don't have a great deal of
>> experience with modules.
>>
>> So, if I use the "go get" command to download a module, when I look in
>> the module cache the @v directory of the requested module contains at least
>> one .info file.
>> This isn't the case for any indirect dependencies which seem to contain
>> only list, list.lock and .mod files.
>>
>> There must be a way to have all of the .info files downloaded to the
>> cache because the goland ide does this when it opens a module directlry and
>> the cache is empty. I just don't know what command it's using to achieve it.
>>
>> So, does anyone know a command which will download all dependencies
>> complete with their .info files?
>>
>> Thanks
>>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/edb36cbc-e814-4712-9582-c0e9633597b9n%40googlegroups.com.
