You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gopls/go.mod and gopls/go.sum are updated to reflect dependency changes (maybe?)
OTOH, I don't know what's the intended behavior.
The development was done using an uncommitted golang.org/x/tools module version.
If the code in golang.org/x/tools/gopls module depends on uncommitted changes in
golang.org/x/tools module, it's not possible to create a working go.mod /go.sum until
the change for golang.org/x/tools module is first committed & released.
It's likely I misunderstood the purpose of gotip work sync.
go work sync resets the state in the modload package before each
iteration where it updates the workspace modules' go.mod files. But
before this change it wasn't resetting the global state in the modfetch
package. This is necessary because the modfetch package keeps track of
the sums that will be written to go.sum. Further, the fetch caches
will update information about which modules are used when fetching
packages, and so those caches need to be cleared between each workspace
Thanks bcmills for helping me debug!
Trust: Michael Matloob <firstname.lastname@example.org>
Run-TryBot: Michael Matloob <email@example.com>
Reviewed-by: Bryan Mills <firstname.lastname@example.org>
TryBot-Result: Gopher Robot <email@example.com>