-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Stabilize token provenance fixture clock #2464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
kiranmagic7
wants to merge
1
commit into
steipete:main
from
kiranmagic7:kiran/stabilize-token-provenance-clock-20260727
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On hosts using Mountain, Pacific, Alaska, or Hawaii time,
1_784_179_200is still July 15 locally (it is 2026-07-16 05:20 UTC). The Bedrock snapshot labels its bucket2026-07-16using the local dashboard calendar, so the newly fixed request clock ends the reporting window on July 15 and filters out the fixture's only entry; consequentlyforced successful empty publication removes prior spend without warningfails its initialtotalCost == 4assertion. Use an instant safely inside July 16 across supported time zones, such as the fixture snapshot's existing noon-UTC timestamp.Useful? React with 👍 / 👎.