{{ message }}
Repository navigation
Convert chromeAutofill to LAVA @artifact_processor (multi-browser) - #768
Merged
Merged
Conversation
…lit entries/profiles)
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.
Converts the Chromium autofill parser to the LAVA
@artifact_processorpattern, following the multi-browser approach (per-browser HTML + per-browser LAVA table + combined return with aBrowser Namecolumn).date_created/date_last_used) to a consistent 5-column shape — older schema getsDate Last Used = ''.Date Created/Date Last Usedraw → aware UTCdatetime(replacing SQLdatetime(...,'unixepoch')).Date Modified/Date Last Usedraw → aware UTCdatetime;Phone Numbermarkedphonenumber.open_sqlite_db_readonly; shared report/LAVA emission via a small helper.Verified: byte-compile, both functions decorated with 4-arg signature, return 3-tuples, output_types valid, loader resolves both, uses the same lava_process_artifact/lava_insert_sqlite_data per-browser pattern as chromeBookmarks, pylint clean.