cmd/go: `expected 'package', found 'EOF'` errors with module indexing enabled on WSL2 #54651

jhaumont · 2022-08-24T15:50:31Z

What version of Go are you using (`go version`)?

$ go version
go version go1.19 linux/amd64

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (`go env`)?

go env Output

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/jhaumont/.cache/go-build"
GOENV="/home/jhaumont/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/jhaumont/go/pkg/mod"
GONOPROXY="github.com/blablacar"
GONOSUMDB="github.com/blablacar"
GOOS="linux"
GOPATH="/home/jhaumont/go"
GOPRIVATE="github.com/blablacar"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/jhaumont/bin/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/jhaumont/bin/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1850192189=/tmp/go-build -gno-record-gcc-switches"

What did you do?

When installing 1.19 go version & reinstall/update the additional go tools like gopls & dlv, I have an issue with delve and the package https://github.com/hashicorp/golang-lru/tree/master/simplelru.
So, I can't install delve. But if I use the 1.18.5 version of go, I have no issue and I can install the last delve version (1.9.0)

But if I use GODEBUG=goindex=0, it works :)

Reproduce:
I try to do a fresh install of go (with 1.19.0) and then, install delve.

Install go:

rm -rf ${HOME}/bin/go
cd "$(mktemp -d)"
wget https://go.dev/dl/go1.19.linux-amd64.tar.gz
tar -C ${HOME}/bin -xzf go1.19.linux-amd64.tar.gz

Install devel:

go install -v github.com/go-delve/delve/cmd/dlv@latest

What did you expect to see?

No error, devel is correctly installed

What did you see instead?

pkg/mod/github.com/hashicorp/golang-lru@v0.5.4/simplelru/lru.go:1:1: expected 'package', found 'EOF'

The text was updated successfully, but these errors were encountered:

jhaumont · 2022-08-24T15:51:10Z

This one close go-delve/delve#3118
and the requested files: https://drive.google.com/drive/folders/1va6Xvnyhl00gjWvHh-0sLCCdoQyYxlD-?usp=sharing

cc @bcmills

dr2chase · 2022-08-24T20:10:37Z

Assigned @bcmills for now, anyone looking at this should know that this is not reproducible in general (I tried with 1.19 and tip on macOS and Linux), but there was nonetheless a problem, which is linked to the delve bug and referenced files above. So it remains open.

jhaumont · 2022-08-25T08:27:06Z

By the way @dr2chase, I work with Debian on WSL.

jhaumont · 2022-09-08T12:23:48Z

Hello
I face the same issue with 2 new packages (not link to delve) on an internal go projet:
../../go/pkg/mod/github.com/armon/go-radix@v1.0.0/radix.go:1:1: expected 'package', found 'EOF' ../../go/pkg/mod/github.com/mitchellh/mapstructure@v1.5.0/decode_hooks.go:1:1: expected 'package', found 'EOF'
Using GODEBUG=goindex=0 fix the issue

bcmills · 2022-09-08T18:53:49Z

@jhaumont, just to rule out filesystem weirdness, what filesystem are you using for /home/jhaumont/go/pkg/mod?

bcmills · 2022-09-08T18:59:38Z

And does running go clean -cache also fix the issue (without GODEBUG=goindex=0) when it happens?

jhaumont · 2022-09-09T12:25:16Z

@bcmills I'm on WSL. This is the result of mount | column -t command:
/dev/sdc on / type ext4 (rw,relatime,discard,errors=remount-ro,data=ordered)
And for the second question, the answer is no (I already test it before opening the issue)

aarzilli · 2022-09-09T13:04:21Z

Is this WSL1 or WSL2?

jhaumont · 2022-09-09T14:35:16Z

@aarzilli WSL2 with debian

bcmills · 2022-09-19T15:31:01Z

This is currently the only report we have of this kind of corruption. It's not clear to me whether this is a bug in Go, a bug in WSL2, or both. Moving to the Backlog pending more user reports and/or test failures that might shed some light for debugging.

Obasoro · 2023-01-02T17:46:25Z

I have go on both my system and I am having the same issue after installing go and trying to run a go file "go:1:1: expected 'package', found 'EOF'"

package main
import
"fmt"
"os"

func main() {
var s, sep string
for i := 1; i < len(os.Args); i++ {
s += sep + os.Args[i]
sep = ""
}
fmt.Println(s)

}

jhaumont · 2023-01-10T18:54:55Z

@bcmills @Obasoro on my side, I have wiped out my WSL and it works normally. I ve no idea why 😕

ghost · 2023-02-11T18:08:59Z

I've faced the same issue today.

If I run go build with GOPATH="$(realpath ../gopath)", the command fails. However, I was able to resolve the error by several workarounds:

Setting GOPATH to somewhere else, such as ../../gopath. I have no idea what makes the difference.
By using GODEBUG=goindex=0.
Locating the building directory somewhere else (see below on this).

Something about the location of building directory appears to cause the error. First of all, the problem is only caused when the building directory is either ~/aur/yay/src/yay-11.3.2, ~/aur/yay/src/yay, ~/aur/yay/src/foobarbaz, or anything else of that kind. Otherwise, I wasn't able to reproduce the error, e.g. the building works perfectly in ~/aur/yay/yay. It seems like there's something special about ~/aur/yay/src.

Permissions don't seem to cause the error. I've removed and created ~/aur several times.

go version

go version go1.20 linux/amd64

go env

output

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/azat/.cache/go-build"
GOENV="/home/azat/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/azat/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/azat/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.20"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/azat/aur/yay/src/foo/barbaz/go.mod"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1292885877=/tmp/go-build -gno-record-gcc-switches"

what I did

mkdir -p aur/yay/src
cd aur/yay/src
git clone https://github.com/Jguer/yay
cd yay
GOPATH="$(realpath ../gopath)" go build

what I expected to see

output

go: downloading github.com/Jguer/aur v1.1.3
go: downloading github.com/Jguer/go-alpm/v2 v2.1.2
go: downloading github.com/Jguer/votar v1.0.0
go: downloading github.com/Morganamilo/go-srcinfo v1.0.0
go: downloading github.com/deckarep/golang-set/v2 v2.1.0
go: downloading github.com/pkg/errors v0.9.1
go: downloading github.com/leonelquinteros/gotext v1.5.1
go: downloading github.com/Morganamilo/go-pacmanconf v0.0.0-20210502114700-cff030e927a5
go: downloading github.com/adrg/strutil v0.3.0
go: downloading golang.org/x/term v0.3.0
go: downloading golang.org/x/sys v0.3.0
go: downloading github.com/itchyny/gojq v0.12.11
go: downloading github.com/ohler55/ojg v1.15.0
go: downloading golang.org/x/text v0.5.0
go: downloading github.com/itchyny/timefmt-go v0.1.5

what I saw

output

go: downloading github.com/Jguer/aur v1.1.3
go: downloading github.com/Jguer/go-alpm/v2 v2.1.2
go: downloading github.com/Jguer/votar v1.0.0
go: downloading github.com/Morganamilo/go-srcinfo v1.0.0
go: downloading github.com/deckarep/golang-set/v2 v2.1.0
go: downloading github.com/leonelquinteros/gotext v1.5.1
go: downloading github.com/pkg/errors v0.9.1
go: downloading github.com/Morganamilo/go-pacmanconf v0.0.0-20210502114700-cff030e927a5
go: downloading github.com/adrg/strutil v0.3.0
go: downloading golang.org/x/term v0.3.0
go: downloading golang.org/x/sys v0.3.0
go: downloading github.com/itchyny/gojq v0.12.11
go: downloading github.com/ohler55/ojg v1.15.0
go: downloading golang.org/x/text v0.5.0
go: downloading github.com/itchyny/timefmt-go v0.1.5
../gopath/pkg/mod/github.com/!jguer/votar@v1.0.0/pkg/vote/aur.go:1:1: expected 'package', found 'EOF'
../gopath/pkg/mod/github.com/!morganamilo/go-pacmanconf@v0.0.0-20210502114700-cff030e927a5/cmd.go:1:1: expected 'package', found 'EOF'
../gopath/pkg/mod/github.com/!morganamilo/go-srcinfo@v1.0.0/examples_test.go:1:1: expected 'package', found 'EOF'
../gopath/pkg/mod/github.com/adrg/strutil@v0.3.0/example_test.go:1:1: expected 'package', found 'EOF'
../gopath/pkg/mod/github.com/adrg/strutil@v0.3.0/metrics/examples_test.go:1:1: expected 'package', found 'EOF'

ghost · 2023-02-11T20:40:17Z

The problem has been resolved after I deleted go-build cache in ~/.cache/go-build

Windeal · 2023-02-15T01:32:11Z

The problem has been resolved after I deleted go-build cache in ~/.cache/go-build

I've faced the same issue today.
And solved with your method， thanks

aarzilli · 2023-02-15T06:18:57Z

@azat-reason @Windeal are you using WSL2?

timohn · 2023-02-24T07:40:17Z

The problem has been resolved after I deleted go-build cache in ~/.cache/go-build

Had the issue on centOS 7.
Fixed it for me either - thank you!

GMsure · 2023-04-06T08:40:51Z

Well I was having a lot of xxx.go:1:1: expected 'package', found 'EOF' problems when I went to build the kubectl-debug tool in WSL2
After deleting the cache directory under gowork/pkg/mod and all the packages that prompted for EOF in the file header, I re-make and solved the problem
In the situation I was in, this command was executed in the ~/gowork/pkg/mod directory: sudo rm -rf cache sigs.k8s.io github.com golang.org k8s.io

jhaumont · 2023-05-04T14:35:24Z

Hello
I just update to go 1.20 and no issue on my side. So I only have the issue with the update from 1.18 to 1.19

ghoulsec · 2023-05-06T02:54:29Z

Hi, I just updated to 1.20, no problem on my side. So I only have problems with updates from 1.18 to 1.19
I am also version 20, but I am in the Windows version of vscode environment

youguanxinqing · 2023-09-04T05:10:12Z

The problem has been resolved after I deleted go-build cache in ~/.cache/go-build

It's helpful! Works for me after go clean -cache on WSL1.

Jack-Can · 2023-10-23T16:28:39Z

Using VS Code for GO, and faced the same issue. Saving the file 'Ctrl+S' on Windows fixed the issue.

ChennSun · 2023-11-23T04:16:07Z

我删除了go-build缓存后问题已经解决~/.cache/go-build

nice, solved my problem

newnetmp3 · 2023-12-07T23:13:17Z

currently having this issue on Linux Mint 21.2 when run as a normal user:
../go/pkg/mod/github.com/h2non/bimg@v1.1.5/type.go:1:1: expected 'package', found 'EOF'

runs fine when run as root, fails in sudo

Moonyongjung · 2024-01-02T04:40:48Z

The problem has been resolved after I deleted go-build cache in ~/.cache/go-build

Thanks, it is helpful.

dimisjim · 2024-02-05T10:30:50Z

This can also be due to go files in the module, not having the package declaration: https://stackoverflow.com/a/38812470/3263374

zhengsc01 · 2024-04-12T07:18:15Z

go clean -cache works for me on WSL 2. Thanks for sharing!

jhaumont changed the title ~~affected/package: cmd/go - modindex - Can't install delve with go 1.19~~ cmd/go - modindex - Can't install delve with go 1.19 Aug 24, 2022

jhaumont changed the title ~~cmd/go - modindex - Can't install delve with go 1.19~~ cmd/go - modindex: Can't install delve with go 1.19 Aug 24, 2022

bcmills added GoCommand cmd/go modules labels Aug 24, 2022

bcmills added this to the Go1.20 milestone Aug 24, 2022

dr2chase assigned bcmills Aug 24, 2022

dr2chase added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Aug 24, 2022

bcmills changed the title ~~cmd/go - modindex: Can't install delve with go 1.19~~ cmd/go: error installing delve with go 1.19 with module indexing enabled Aug 25, 2022

bcmills added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Sep 8, 2022

bcmills removed the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Sep 19, 2022

bcmills modified the milestones: Go1.20, Backlog Sep 19, 2022

bcmills removed their assignment Sep 19, 2022

bcmills changed the title ~~cmd/go: error installing delve with go 1.19 with module indexing enabled~~ cmd/go: expected 'package', found 'EOF' errors with module indexing enabled on WSL2 Sep 29, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cmd/go: `expected 'package', found 'EOF'` errors with module indexing enabled on WSL2 #54651

cmd/go: `expected 'package', found 'EOF'` errors with module indexing enabled on WSL2 #54651

jhaumont commented Aug 24, 2022 •

edited

jhaumont commented Aug 24, 2022 •

edited

dr2chase commented Aug 24, 2022

jhaumont commented Aug 25, 2022

jhaumont commented Sep 8, 2022

bcmills commented Sep 8, 2022

bcmills commented Sep 8, 2022

jhaumont commented Sep 9, 2022

aarzilli commented Sep 9, 2022

jhaumont commented Sep 9, 2022

bcmills commented Sep 19, 2022

Obasoro commented Jan 2, 2023 •

edited

jhaumont commented Jan 10, 2023

ghost commented Feb 11, 2023 •

edited by ghost

ghost commented Feb 11, 2023

Windeal commented Feb 15, 2023

aarzilli commented Feb 15, 2023

timohn commented Feb 24, 2023

GMsure commented Apr 6, 2023

jhaumont commented May 4, 2023

ghoulsec commented May 6, 2023 •

edited

youguanxinqing commented Sep 4, 2023

Jack-Can commented Oct 23, 2023

ChennSun commented Nov 23, 2023

newnetmp3 commented Dec 7, 2023

Moonyongjung commented Jan 2, 2024

dimisjim commented Feb 5, 2024

zhengsc01 commented Apr 12, 2024

cmd/go: expected 'package', found 'EOF' errors with module indexing enabled on WSL2 #54651

cmd/go: expected 'package', found 'EOF' errors with module indexing enabled on WSL2 #54651

Comments

jhaumont commented Aug 24, 2022 • edited

What version of Go are you using (go version)?

Does this issue reproduce with the latest release?

What operating system and processor architecture are you using (go env)?

What did you do?

What did you expect to see?

What did you see instead?

jhaumont commented Aug 24, 2022 • edited

dr2chase commented Aug 24, 2022

jhaumont commented Aug 25, 2022

jhaumont commented Sep 8, 2022

bcmills commented Sep 8, 2022

bcmills commented Sep 8, 2022

jhaumont commented Sep 9, 2022

aarzilli commented Sep 9, 2022

jhaumont commented Sep 9, 2022

bcmills commented Sep 19, 2022

Obasoro commented Jan 2, 2023 • edited

jhaumont commented Jan 10, 2023

ghost commented Feb 11, 2023 • edited by ghost

go version

go env

what I did

what I expected to see

what I saw

ghost commented Feb 11, 2023

Windeal commented Feb 15, 2023

aarzilli commented Feb 15, 2023

timohn commented Feb 24, 2023

GMsure commented Apr 6, 2023

jhaumont commented May 4, 2023

ghoulsec commented May 6, 2023 • edited

youguanxinqing commented Sep 4, 2023

Jack-Can commented Oct 23, 2023

ChennSun commented Nov 23, 2023

newnetmp3 commented Dec 7, 2023

Moonyongjung commented Jan 2, 2024

dimisjim commented Feb 5, 2024

zhengsc01 commented Apr 12, 2024

cmd/go: `expected 'package', found 'EOF'` errors with module indexing enabled on WSL2 #54651

cmd/go: `expected 'package', found 'EOF'` errors with module indexing enabled on WSL2 #54651

jhaumont commented Aug 24, 2022 •

edited

What version of Go are you using (`go version`)?

What operating system and processor architecture are you using (`go env`)?

jhaumont commented Aug 24, 2022 •

edited

Obasoro commented Jan 2, 2023 •

edited

ghost commented Feb 11, 2023 •

edited by ghost

ghoulsec commented May 6, 2023 •

edited