fix(sensor): support the current Warp database schema - #89
Draft
barisozbas wants to merge 1 commit into
Draft
Conversation
Summary: Intent: - Continue collecting Warp conversations after its local database schema changed. Changes: - Detect supported schema variants and query their current columns. - Cache schema detection for the duration of parsing.
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.
What changed
Warp conversation parsing now supports both the legacy and current local database schemas.
Why
Warp renamed conversation fields in its local database. The fixed legacy query fails against current installations and prevents conversation collection entirely.
Validation
pytest -q Sensor/testsruff check Sensor/adr_sensor/parsers/warp_parser.py Sensor/tests/test_parsers.py