Skip to content

Segmentation fault when a segment is missing from minio #2693

@himsheda

Description

@himsheda

Describe the bug

When a segment is corrupted or deleted from minio, if you try to read data in that date range, then the code will throw an segmentation error inside the C++ instead of raising a DataError.

I was using 4.4.3 earlier, it works correctly. But the recent version does not work. I tried upto 6.2.1. Not sure the exact version which had this bug for the first time.

Steps/Code to Reproduce

Create a data frame with a date range and write the data into minio backend.
Then delete a segment from tdata.

Then when you try to read the data it will now return a data error instead it will throw you a segmentation fault, hence crashing your application completely

Expected Results

DataError

OS, Python Version and ArcticDB Version

Python: 3.8.20 | packaged by conda-forge | (default, Sep 30 2024, 17:52:49)
[GCC 13.3.0]
OS: Linux-5.15.0-140-generic-x86_64-with-glibc2.17
ArcticDB: 6.2.3

Tried this with python 3.11 also. Same issue

Backend storage used

Minio S3

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions