[BUG]: Retrieving the Python DataFrame from a SlicedMessageMeta ignores the start/stop

[dagardner-nv]

Version

24.10

Which installation method(s) does this occur on?

Conda

Describe the bug.

This was found while investigating #2002
The issue is that while the TableInfo held by SlicedMessageMeta correctly reflects the start and stop values, attempting to call:

auto mutable_info = sliced_meta.get_mutable_info();
auto pdf = mutable_info.checkout_obj(); // pdf contains the entire original DF

Will return the entire DataFrame. Fix would likely require SlicedMessageMeta to apply a sliced to the python object. Once this is fixed, we should avoid the work-around introduced in PR #2015 in the DeserializeStage

Minimum reproducible example

auto mutable_info = sliced_meta.get_mutable_info();
auto pdf = mutable_info.checkout_obj(); // pdf contains the entire original DF

Relevant log output

Click here to see error details

[Paste the error here, it will be hidden by default]

Full env printout

Click here to see environment details

[Paste the results of print_env.sh here, it will be hidden by default]

Other/Misc.

No response

Code of Conduct

• I agree to follow Morpheus' Code of Conduct
• I have searched the open bugs and have found no duplicates for this bug report