I'm not able to verify with Go 1.25 unless I disable the new leak sanitizer. The tests do pass when ASAN_OPTIONS is set. I don't consider this a blocker but we should look at it for the next release.
I poked around and it seems C Data test helpers like testStruct invoke C.CString but there is no code that ever frees the result. It would require some refactoring to get around this (e.g. returning both the C Data pointer and a Go release callback for the test to invoke from testStruct?) -David On Fri, Aug 29, 2025, at 07:11, Matt Topol wrote: > Hi, > > I would like to propose the following release candidate (RC0) of > Apache Arrow Go version v18.4.1. > > This release candidate is based on commit: > c6ce2ef4e55009a786cf04b3845eba5170c98066 [1] > > The source release rc0 is hosted at [2]. > > Please download, verify checksums and signatures, run the unit tests, > and vote on the release. See [3] for how to validate a release candidate. > > The vote will be open for at least 72 hours. > > [ ] +1 Release this as Apache Arrow Go v18.4.1 > [ ] +0 > [ ] -1 Do not release this as Apache Arrow Go v18.4.1 because... > > [1]: > https://github.com/apache/arrow-go/tree/c6ce2ef4e55009a786cf04b3845eba5170c98066 > [2]: https://github.com/apache/arrow-go/releases/v18.4.1 > [3]: > https://github.com/apache/arrow-go/blob/main/dev/release/README.md#verify
