Open WillAyd opened 2 months ago
Thank you for the report and excellent example! I'll will take a look at this today or tomorrow.
Thanks @paleolimbot . To my surprise, I think this issue goes away when I use meson as the build system?
https://github.com/WillAyd/capsule_testing/pull/1/files
So may be something in the flags between CMake / Meson that causes this
If it helps, here is the verbose log for a CMake build:
https://github.com/WillAyd/capsule_testing/actions/runs/10494816933/job/29071897812?pr=3#step:4:286 https://github.com/WillAyd/capsule_testing/pull/3
Versus the same thing in Meson:
https://github.com/WillAyd/capsule_testing/actions/runs/10494621884/job/29071248445?pr=1#step:4:382 https://github.com/WillAyd/capsule_testing/pull/1
Not sure if this is a nanoarrow issue or with the PyArrow export, but figured I'd start here.
When consuming an array like this:
and using
ArrowDecimalAppendDigitsToBuffer
in nanoarrow, it seems like negative values on windows only are not properly represented.I created an "MRE" for this in this library:
https://github.com/WillAyd/capsule_testing/tree/739bc608b96101ada424ef6d9736e2dfffcc2f11
You can see the issue for Windows in CI logs:
https://github.com/WillAyd/capsule_testing/actions/runs/10482665140/job/29034136906#step:4:358