fix(gateway): pass consistent timestamp through budget reset#928
Merged
fix(gateway): pass consistent timestamp through budget reset#928
Conversation
reset_user_budget() called datetime.now(UTC) independently from validate_user_budget(), causing the reset_at log entry and next_budget_reset_at calculation to drift from the time that actually triggered the reset. Pass the caller's timestamp through to ensure all reset operations use the same point in time. Fixes #917 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
njbrake
temporarily deployed
to
integration-tests
GitHub Actions
Inactive
njbrake
temporarily deployed
to
integration-tests
GitHub Actions
Inactive
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
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
reset_user_budget()calleddatetime.now(UTC)independently fromvalidate_user_budget(), so the timestamp used for the reset log and next period calculation drifted from the time that actually triggered the reset. Now the caller'snowis passed through as a parameter, ensuring all reset operations use the same point in time.PR Type
Relevant issues
Fixes #917
Checklist
AI Usage Information
AI Model used: Claude Opus 4.6
AI Developer Tool used: Claude Code
I am an AI Agent filling out this form (check box if true)