You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug, including details regarding any error messages, version, and platform.
get_next should set ArrowArray.release to NULL when there are no more records. However, the current implementation instead tries to release the out-parameter. This is harmless when the out-parameter is 0-initialized (the implementation will skip the call) but otherwise it'll crash (after jumping to a random garbage address).
Component(s)
Go
The text was updated successfully, but these errors were encountered:
@pitrou I noticed this while using PyArrow to import an ArrowArrayStream exported from Go. PyArrow apparently passes in an uninitialized ArrowArray to Go, and Go was assuming it would be initialized. Should we say that producers should not assume inputs are initialized, or that consumers should (zero-)initialize parameters?
Describe the bug, including details regarding any error messages, version, and platform.
get_next
should setArrowArray.release
toNULL
when there are no more records. However, the current implementation instead tries to release the out-parameter. This is harmless when the out-parameter is 0-initialized (the implementation will skip the call) but otherwise it'll crash (after jumping to a random garbage address).Component(s)
Go
The text was updated successfully, but these errors were encountered: