Gopls supports =>, and in fact has a replace in its own modfile. Also, per my reading of the error the unexpected token is "v0.13.0".

That error is present in the go command, related to retraction, though not at 1.15.11. It's also present in x/mod (again for the retract verb), but I don't think an error from x/mod would present as the critical error you see.

Is it possible you typed 'retract' instead of 'replace'? Is it possible you have multiple versions of Go installed on your computer? Thanks.

I pasted it here exactly as it appears in go.mod, namely

replace github.com/apache/thrift v0.13.0 => github.com/apache/thrift/lib/go/thrift v0.0.0-20210120171102-e27e82c46ba4

So it's definitely replace. To be fair, I left a comment on that repo's commit and got the response that the particular commit is actually in an invalid state and he instructed me to use the next commit, which negated the need to even use replace. So my issue is technically solved, but this issue for gopls still results in the reported error state.

If it is supported as you claim, then I suppose it might somehow be related to the invalid go.mod state of the repo in question, but the errors thrown by gopls itself are still questionable. The replace resolved the errors issued by the regular go commands, but resulted in these errors here.

I suppose it might somehow be related to the invalid go.mod state of the repo in question

The error indicates the local go.mod, and the go.mod in github.com/apache/thrift/lib/go/thrift at that version is empty.

Gopls uses the same modfile parser as the go command: golang.org/x/mod. The error you see is either originating from executions of the go command, or from calls to x/mod from gopls. When I looked for it, it appears that its only occurrence is related to module retraction (linked above). Something strange is going on.

Just as a sanity check, I did create a minimal module that uses that exact replace directive. Everything works fine.

> cat go.mod
module mod.test

go 1.12

require github.com/apache/thrift v0.13.0

replace github.com/apache/thrift v0.13.0 => github.com/apache/thrift/lib/go/thrift v0.0.0-20210120171102-e27e82c46ba4
> cat main.go
package main

import "github.com/apache/thrift"

func main() {
        println(thrift.UNKNOWN_APPLICATION_EXCEPTION)
}

So I suspect there is something else in your go.mod file that is contributing to the error you see. Would you be able to provide a redacted version of your go.mod file, or try trimming down your modfile to a minimal repro? Could you also search the start of your logs for "go version", and make sure it agrees with the version you see on the command-line (go1.15.11)? I'd like to understand what's going on -- at the very least this is a confusing error message.

at the very least this is a confusing error message.

This was my argument for not dismissing this off-hand. I'll provide the full go.mod when I get back to work tomorrow.

The ultimate cause is possibly due to this being a massive monorepo using please.build for a build system, which ultimately does all it's individual builds in GOPATH mode. Despite that, as far as I'm aware, gopls should be pulling in the go.mod and initializing based off that. Perhaps that assumption is my failing...

I tried to be sure there weren't any queries being sent to the gopls server yet though, so the error occurs during initialization. If my assumptions there are false, then our repo itself could be at fault.

Hi, I'm closing this as unactionable for now. Please re-open if you are able to gather more details. Thanks.