Ryan Currah

One way to reproduce this with golangci itself is to: 1) Set `modules-download-mode: readonly` in `golangci.yml` 2) Remove a line from `go.sum` that does NOT have `/go.mod` in the line...

Seems to be `packages.Load(conf, args...)` does not return an error even though the debug output with `export GL_DEBUG=loader` set shows a debug line from `packages` of: ```bash DEBU [loader] 191.382563ms...

Ok after a bunch of time spent debugging the `tools` package from golang I found the issue and created a Pull Request here: https://github.com/golang/tools/pull/231. If this fix is accepted `packages.Load`...

Just another thought. Whenever someone is having this issue they should run: ``` go list -mod=readonly -e -json -compiled=true -test=true -export=true -deps=true -find=false -- ./... ``` In their project to...

Looks like 6 days ago Lima documented using virtiofs https://github.com/lima-vm/lima/commit/c18ae239b69a47db77436765b9b4861aaa0d595d

The way this linter works is by determining which modules are blocked in your `go.mod` file and finding any blocked modules in your import statements. This is because lint results...

Since this linter is for modules, not internal packages I am going to close this.

We are also interested in this for our own initiative. We hope we could use Artifactory as a source for Ollama models.

I think you should remove `depguard` from the enabled linters. We do not seem be using it, how I can tell is there is no list of allowed linters. Then...

Testing these changes in our environment. When they have baked for a little bit I will change this PR to `Ready for Review`.