-
Notifications
You must be signed in to change notification settings - Fork 0
filter log entries from parsed levels and timezone-normalise CLI filters #17
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
Open
HrachShah
wants to merge
1
commit into
main
Choose a base branch
from
fix/cli-filter-on-parsed-level-and-tz-aware-time
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
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.
🧩 Analysis chain
🏁 Script executed:
Repository: HrachShah/log-analyzer-cli
Length of output: 22486
🏁 Script executed:
Repository: HrachShah/log-analyzer-cli
Length of output: 1535
🏁 Script executed:
Repository: HrachShah/log-analyzer-cli
Length of output: 525
Datetime comparison will fail when parsers return naive timestamps.
Lines 232–234 compare
parsed.timestampagainst UTC-aware datetimes (start_timeandend_timepassed from lines 108 and 117). Python raisesTypeErrorwhen comparing aware and naive datetime objects. Multiple parsers emit naive datetimes:strptime()strptime()When a log entry has a naive timestamp, the comparison at lines 232–234 will crash with
TypeError: '<' not supported between instances of 'datetime.datetime' and 'datetime.datetime'instead of being caught by the outer exception handler (lines 96–99, which does not listTypeError).Normalize naive timestamps before comparison, or convert all timestamps to a consistent timezone state.
🤖 Prompt for AI Agents