-
Notifications
You must be signed in to change notification settings - Fork 367
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
Add SQLite parser for Files by Google (files_master_database) file #4938
base: main
Are you sure you want to change the base?
Conversation
Is the cause of |
@jundi77 looks like the run took more than 1h, that can be due to external factors. |
@gustino7 what is the origin of the test data file? |
TODO: both timeliner and formatters MUST be reviewed for a better output on sentencing and description
* Create files_by_google.py * Add files_master_database for files_by_google unit test * Update db filename used in files_by_google unit test * Fix unit test files_by_google Fix unit test files_by_google: - Renamed class to conform with other test class - Wrong class used in plugin variable used for testing - Event data is mistakenly written in AM/PM mode, now is written in 24H format - Fix some value `expected_event_values` is in number type - Mistakenly assumed in GetAttributeContainerByIndex that 1 is the first event_data, now changed to 0
Rebased PR |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4938 +/- ##
==========================================
+ Coverage 85.09% 85.10% +0.01%
==========================================
Files 432 433 +1
Lines 38792 38840 +48
==========================================
+ Hits 33009 33056 +47
- Misses 5783 5784 +1 ☔ View full report in Codecov by Sentry. |
We are using forensic image from https://corp.digitalcorpora.org/corpora/mobile/android_13/ at |
One line description of pull request
Add SQLite parser for Files by Google (files_master_database) file
Description:
I add/edit several files:
Notes:
All contributions to Plaso undergo code review.
This makes sure that the code has appropriate test coverage and conforms to the
Plaso style guide.
One of the maintainers will examine your code, and may request changes. Check off the items below in
order, and then a maintainer will review your code.
Checklist: