fix(codex): include entry count in globalHash to prevent duplicates #72
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
Messages with identical timestamps (within the same millisecond) were getting the same globalHash, causing skipDuplicates to silently drop them on upload. This resulted in ~10% data loss ($7.29 of $73.74 in one user's case). Fix: Include entries.len() in the hash to ensure uniqueness even when timestamps collide.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
skipDuplicateson the cloud to silently drop them during uploadFix
Include
entries.len()in the hash to ensure uniqueness even when timestamps collide:{file}_{timestamp}_user_{count}{file}_{timestamp}_assistant_{count}{file}_{timestamp}_token_{count}Test plan