-
-
Notifications
You must be signed in to change notification settings - Fork 48
fix: parse reset timestamps for Claude CLI & Gemini API absolute times #104
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
Merged
hanrw
merged 7 commits into
tddworks:main
from
zenibako:fix-absolute-reset-date-parsing
Feb 11, 2026
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
a3c253a
fix: parse absolute timestamps in Claude CLI reset times
zenibako d08ed7e
fix(test): add time buffer to reset timestamp tests to prevent flakiness
zenibako e2d9874
fix: deduplicate reset text from terminal redraw artifacts
zenibako 8185e24
fix: handle mid-line "Resets" token in parseAbsoluteDate
zenibako 99c2fca
fix: parse Gemini reset timestamps from ISO 8601 into human-readable …
zenibako e51fcbd
fix: use case-insensitive search on cleaned string directly to avoid …
zenibako 9117400
Update Sources/Infrastructure/Claude/ClaudeUsageProbe.swift
zenibako 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
Some comments aren't visible on the classic Files Changed page.
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
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
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.
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.
Future-date resolution logic is well-structured and covers all format branches correctly.
Each format maps to the right resolution strategy. One very minor edge case: if
calendar.date(byAdding: .day, value: 1, to: now)were to returnnil(Line 796), the fallback on Line 805 would return the rawparsedDate(a year-2000 reference date). This is practically impossible but could produce a silently wrongresetsAtrather thannil.Possible defensive tweak
This ensures a clearly-past date is never returned, though the scenario is essentially theoretical.
📝 Committable suggestion
🤖 Prompt for AI Agents