fix: Harden benchmark infrastructure and resolve OSS data integrity#5
Open
ixchio wants to merge 1 commit into
Open
fix: Harden benchmark infrastructure and resolve OSS data integrity#5ixchio wants to merge 1 commit into
ixchio wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This PR addresses structural reliability and temporal data integrity issues within the benchmark infrastructure.
Changes
timestampsupport to theAddRequestmodel and injected it intometadata["created_at"]. This prevents the silent dropping of observation dates during ingestion and ensures temporal reasoning benchmarks function correctly.get_user_profilefunctionality withinMem0Clientso it supports bothoss(via memory aggregation) andcloudmodes to prevent runtime missing attribute errors.locomo,beam, andlongmemevalrunners. Debug file descriptors are now safely wrapped in robusttry...finallystructures to guarantee release upon exit or exception, mitigatingOSError: [Errno 24]during high-volume batch executions.