Steven Hartland

Looks like [Rows.Close](https://pkg.go.dev/database/sql#Rows.Close) is more complex as if `Next` is called and returns false then `Rows` is closed implicitly, so will need some more thought to ensure it doesn't give...

Looking at it https://github.com/ryanrolds/sqlclosecheck suffers from the false positive when you have checked `rows.Next()` and `rows.Err()` for example: ```go func Called(db *sql.DB) { rows, _ := db.Query("select id from tb")...

Seeing this in combination with `ireturn` too, as mentioned the error goes away for a time if you clean the cache with `golangci-lint cache clean`. ```shell pkg/mything.go:9:78: directive `//nolint:ireturn //...

Your repo tar is no longer present, but #2346 might fix this issue as it refactors how logging start / stop is handled eliminating a race and subsequent deadlock. If...

I tried to repo locally but can't, here my archive: [log_repo.tgz](https://github.com/testcontainers/testcontainers-go/files/14592050/log_repo.tgz) ```shell # build (cd container; docker build -t localhost/log_repro:latest .) # run test go test -v -race ``` Output:...

I tried adding `ProviderType: tc.ProviderPodman,` to the request but still seems to want to use docker under WSL.

Tried getting a podman working but its just way to flaky, vm totally hangs and then just wont work for me on WSL: ``` API forwarding for Docker API clients...

Finally got podman working after a kernel upgrade but still can't reproduce: ```shell === RUN TestLogIssue 2024/03/13 20:22:37 github.com/testcontainers/testcontainers-go - Connected to docker: Server Version: 4.9.3 API Version: 1.41 Operating...

Can you post the build for the container so we don't have to rely on images?

Thanks @nmoroze looks like a bug in podman to me, if the container doesn't generate any log entries the request for log entries just hangs with podman where as docker...