fix(audit): clamp timestamps forward on clock step-back (AUDIT-001) - #219
Merged
Conversation
…AUDIT-001) Closes #166. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
AuditChain.append()useddatetime.now(UTC)with no guard, so a backward NTP step or clock adjustment could produce entries with timestamps earlier than the previous entrynowtomax(now, prev_entry.timestamp_utc)before assigning — the sequence number already provides strict ordering; this prevents confusing human-readable audit trailsFixes #166.
Test plan
pytest tests/unit/test_audit.py— all 18 pass including 2 new AUDIT-001 testspytestfull suite — no regressions