To workaround https://pagure.io/golist/issue/7, the shell wrapper should switch to another directory (for example /usr/bin) before running golist, and switch back to the correct dir afterwards (so add strategic pushds popds to keep track of where the user, golist and the tests want to be)
golist
Metadata Update from @nim: - Issue assigned to nim
Based on further debugging, this appears related to Go modules. As such, an alternate workaround is to set GO111MODULE=off before calling golist. Of course, you need to be sure your package doesn't actually use Go modules to specify an alternate path or whatever.
GO111MODULE=off
Modules are now disabled by default, module mode will require a new tooling stack refresh anyway. Closing
Metadata Update from @nim: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.