search package only in base gopath
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.5k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
e.g. I have a source dir like this
+src
**_\+ login_server
_____main.go (package main)
____**\+ login
________login.go (package login)
main.go and dir login are children of dir src, login.go in dir login
when I try --instrument=login
complains
cannot find package "login" in any of:
C:\Go\src\login (from $GOROOT)
C:\Go\gopath\src\login (from $GOPATH)
G:\go\zhongshen\server\src\login
even if I add login_server to gopath, it can't work
cannot find package "login" in any of:
C:\Go\src\login (from $GOROOT)
C:\Go\gopath\src\login (from $GOPATH)
G:\go\zhongshen\server\src\login
G:\go\zhongshen\server\src\login_server\src\login
No idea how to make it work
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Windows setup from the report with --instrument=login, using the shown src/login and login_server paths. Start by tracing package resolution from the --instrument entry point and compare the searched GOPATH locations. Done means the login package can be located in this layout, with accurate search-path diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100