-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix: time on filter #5238
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
fix: time on filter #5238
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
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.
Pull Request Overview
This PR fixes a time filtering bug in the search engine by changing the field used for time-based filtering from lastReceived to timestamp. The issue was that time_delta filtering in Keep Provider version 2 was using the wrong field, causing incorrect results when filtering alerts by time.
- Updated the search engine to use
timestampfield instead oflastReceivedfor time-based filtering - Added comprehensive test cases to verify the fix and prevent regression
- Version bump to reflect the bug fix
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| keep/searchengine/searchengine.py | Fixed the time filtering logic to use timestamp field instead of lastReceived |
| tests/test_search_alerts.py | Updated existing test expectations to reflect the corrected field usage |
| tests/test_keep_provider_time_delta.py | Added new comprehensive test cases to reproduce and verify the fix for the time filtering bug |
| pyproject.toml | Version bump from 0.46.4 to 0.46.5 |
Bugbot found 1 bugTo see it, have a team admin activate your membership in the Cursor dashboard. |
close #5180