fix(lifecycle): Fix ObjectInfo fields and mod_time error handling #1088
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #1055
Fixes #932
This PR fixes two issues with lifecycle processing that were causing objects to not be deleted according to lifecycle rules.
Root Causes
Missing is_latest field in ObjectInfo: The scanner convert_record_to_object_info was not setting is_latest field.
Panic on missing mod_time: The lifecycle evaluation code used obj.mod_time.expect() which would panic.
Changes
crates/ahm/src/scanner/data_scanner.rs
crates/ecstore/src/bucket/lifecycle/lifecycle.rs
Testing
Related