paleolimbot opened a new issue, #306:
URL: https://github.com/apache/arrow-nanoarrow/issues/306

   From release verification on condaforge/mambaforge:
   
   ```
   In file included from 
/arrow-nanoarrow/extensions/nanoarrow_ipc/../../src/nanoarrow/array_inline.h:27,
                    from 
/arrow-nanoarrow/extensions/nanoarrow_ipc/../../src/nanoarrow/nanoarrow.h:1100,
                    from 
/arrow-nanoarrow/extensions/nanoarrow_ipc/src/nanoarrow/nanoarrow_ipc.h:21,
                    from 
/arrow-nanoarrow/extensions/nanoarrow_ipc/src/nanoarrow/nanoarrow_ipc_reader_test.cc:22:
   In function 'void ArrowBufferAppendUnsafe(ArrowBuffer*, const void*, 
int64_t)',
       inlined from 'ArrowErrorCode ArrowBufferAppend(ArrowBuffer*, const 
void*, int64_t)' at 
/arrow-nanoarrow/extensions/nanoarrow_ipc/../../src/nanoarrow/buffer_inline.h:124:26,
       inlined from 'virtual void 
NanoarrowIpcReader_StreamReaderExpectedSchema_Test::TestBody()' at 
/arrow-nanoarrow/extensions/nanoarrow_ipc/src/nanoarrow/nanoarrow_ipc_reader_test.cc:321:3:
   
/arrow-nanoarrow/extensions/nanoarrow_ipc/../../src/nanoarrow/buffer_inline.h:115:11:
 warning: 'void* memcpy(void*, const void*, size_t)' reading 280 bytes from a 
region of size 160 [-Wstringop-overread]
     115 |     memcpy(buffer->data + buffer->size_bytes, data, size_bytes);
         |     ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
/arrow-nanoarrow/extensions/nanoarrow_ipc/src/nanoarrow/nanoarrow_ipc_reader_test.cc:
 In member function 'virtual void 
NanoarrowIpcReader_StreamReaderExpectedSchema_Test::TestBody()':
   
/arrow-nanoarrow/extensions/nanoarrow_ipc/src/nanoarrow/nanoarrow_ipc_reader_test.cc:46:16:
 note: source object 'kSimpleRecordBatch' of size 160
      46 | static uint8_t kSimpleRecordBatch[] = {
         |                ^~~~~~~~~~~~~~~~~~
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to