Edge case of partial written record #2282
Description
After hours of debugging this is the real cause: it happens ONLY when the 1st record in the bucket is reused as part of a multi-page records and it's not the 1st chunk.
This is because historically when a multi-page record is written as a linked list in multiple pages, the next pointer = 0 means it's the last chunk. But after ArcadeDB supported the reusing of deleted records, the 1st record in a bucket can be deleted and reused to store a chunk. Well, in this case its pointer is 0, but 0 means last chunk.
I've fixed the algorithm to skip record 0 to be reused in a multi-chunk record.