William Ayd

Its been a while since I have looked at this, but it may also be the result of Python 3.13 removing the lib2to3 module: https://docs.python.org/3.13/whatsnew/3.13.html#to3

I am not sure if the ArrowDtype has ever fully been scoped out, but as far as I am aware we should allow any Arrow data type to be stored...

> Or maybe we should actually also consider still by default convert `string_view` to `string` I'd be hesitant to do this without clarifying how we expect logical types to behave....

Thanks @henry2cox for all of the info on this thread. Is there already a bug report upstream in gcc for this that can be tracked? If not I'd be happy...

When you refer to the gcc/llvm report are you asking about the `.info` file? I see an error like: ```sh geninfo: ERROR: mismatched end line for _ZN32HppBuffer_BufferInitWrapped_Test8TestBodyEv at /home/willayd/clones/arrow-nanoarrow/src/nanoarrow/hpp/buffer_test.cc:41: 41...

Thanks for the steps. I am inspecting the gcov output but I don't think I am seeing exactly what you described. There is only one entry with that function name...

Just a few other assorted things I've noticed so far. > or just the function(s) (see the `--erase-functions` section) FWIW the version of lcov I get with ubuntu 24.04 is...

Also unsure if this matters to the lcov project at all but it appears that gcovr is able to produce coverage reports against the same code base

...and one potentially last useful bit of information is that lcov-2.2 doesn't have the issue from the OP but does end up with an error similar to https://github.com/linux-test-project/lcov/issues/296#issuecomment-2562917191 ```sh /usr/bin/meson...

Yes I agree - let's keep it as an upstream fix. Thanks for the thorough investigation and solution @iabhi4