Nick Ripley

Hi @marcosg-peya. Unfortunately I did not find it yet. I found some race issues in our unit tests that I think are different than this issue (fixed in https://github.com/DataDog/dd-trace-go/pull/1255). Thank...

Thanks, that's helpful. I assume that the goroutines in that stack trace would also include the stack trace you shared in [this comment](https://github.com/DataDog/dd-trace-go/issues/1250#issuecomment-1106592496)? I see the `(*profiler).send` and `(*profiler).collect` goroutines,...

Thank you for the report! Does your vulnerability scanner report a minimum version required to mitigate the issue? I can't find anything like that in any of the provided links,...

Breadcrumb: The issue tracker for github.com/jinzhu/gorm was moved to github.com/go-gorm/gorm. Here's the issue where the vulnerability was reported: https://github.com/go-gorm/gorm/issues/2517, and here's a PR that supposedly fixes it https://github.com/go-gorm/gorm/pull/2519.

So, the commit that fixes the issue referenced above is this one in `go-gorm/gorm`: https://github.com/go-gorm/gorm/commit/836fb2c19d84dac7b0272958dfb9af7cf0d0ade4 Looking at the tags containing that commit, the oldest one is `v1.9.19`. However, that tag...

Awesome! It's great that we'll get macOS and Windows testing. From what I can tell this should also be a good cost savings for us since GitHub actions are free...

I'm not sure if I'd call it flaky? This failure message suggests that the test was influenced by tests from a completely different package. Maybe there's some way we can...

Is there any kind of tool that can check in CI to be sure that every file that would be built by `go build` will also get built by `bazel...

RE: gorm flavors, `github.com/jinzhu/gorm` was moved to `gorm.io/gorm.v1`, and the former is no longer updated. See also #1219

RE: `nil` pointer dereference, the failure is because of calling `Rows.Close` on a `nil` pointer, because the rows are nil due to the error that shows up earlier in [the...