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
total 24
drwxr-xr-x 6 user staff 192 Apr 6 17:36 .
drwxr-xr-x@ 40 user staff 1280 Apr 6 17:25 ..
drwxr-xr-x 12 user staff 384 Apr 6 17:36 .git
-rw-r--r-- 1 user staff 165 Apr 6 17:36 go.mod
-rw-r--r-- 1 user staff 5352 Apr 6 17:36 go.sum
drwxr-xr-x 3 user staff 96 Apr 6 16:51 log
$ go get -u
go: no package to get in current directory
$ git checkout work
$ go get -u
go: upgraded go.uber.org/atomic v1.7.0 => v1.9.0
go: upgraded go.uber.org/multierr v1.6.0 => v1.8.0
go: upgraded go.uber.org/zap v1.20.0 => v1.21.0
(dependencies should be upgraded because the current version is outdated)
What did you expect to see?
Run go get -u on branch failed should upgrade dependencies.
In the past, it worked. I'm don't know the go version exactly, maybe 1.16 or 1.17.
What did you see instead?
go: no package to get in current directory
The text was updated successfully, but these errors were encountered:
@seankhliao I got it. This is my mistake. But I believe that adding a meaningful message is a better choice and it will help developers save time to debug this issue. For example:
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
)?go env
OutputWhat did you do?
Run the following commands:
$ git clone https://github.com/ansidev/go-get-issue
$ git checkout failed
$ ls -la
$ go get -u
go: no package to get in current directory
$ git checkout work
$ go get -u
go: upgraded go.uber.org/atomic v1.7.0 => v1.9.0
go: upgraded go.uber.org/multierr v1.6.0 => v1.8.0
go: upgraded go.uber.org/zap v1.20.0 => v1.21.0
(dependencies should be upgraded because the current version is outdated)
What did you expect to see?
Run
go get -u
on branchfailed
should upgrade dependencies.In the past, it worked. I'm don't know the go version exactly, maybe
1.16
or1.17
.What did you see instead?
go: no package to get in current directory
The text was updated successfully, but these errors were encountered: