Skip to content
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 workaround for pinfo non-json warning output #1418

Merged
merged 1 commit into from Jan 16, 2024

Conversation

hacktobeer
Copy link
Collaborator

Description of the change

Make sure we only use the relevant json output of pinfo.py

Applicable issues

Additional information

Checklist

  • All tests were successful.

Copy link
Member

@aarontp aarontp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@aarontp aarontp merged commit 0a1e1b4 into google:master Jan 16, 2024
5 checks passed
@hacktobeer
Copy link
Collaborator Author

We need to cherry pick this on top of the last release!

Copy link

@113ll3 113ll3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me know

@@ -1070,6 +1070,8 @@ def _validate(self):
log.info(f'Running pinfo.py to validate PlasoFile {self.local_path}')
command = subprocess.run(cmd, capture_output=True, check=True)
storage_counters_json = command.stdout.decode('utf-8').strip()
# pinfo.py might print warnings (non-json) so we only need to last line of output
storage_counters_json = storage_counters_json.splitlines()[-1]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

turbinia/evidence.py

wajihyassine pushed a commit that referenced this pull request Feb 14, 2024
* add workaround for pinfo warning output (#1418)

* Update version to 20231116.1

* Fix plaso dependencies (#1420)

* fix deps

* fix test

* Update version to 20231116.2

* Fix plaso dependencies (#1420)

* fix deps

* fix test

* update docs link

---------

Co-authored-by: hacktobeer <ramsesdebeer@gmail.com>
Co-authored-by: Aaron Peterson <aaronp@gmail.com>
jleaniz pushed a commit to jleaniz/turbinia that referenced this pull request Feb 28, 2024
jleaniz added a commit to jleaniz/turbinia that referenced this pull request Feb 28, 2024
* add workaround for pinfo warning output (google#1418)

* Update version to 20231116.1

* Fix plaso dependencies (google#1420)

* fix deps

* fix test

* Update version to 20231116.2

* Fix plaso dependencies (google#1420)

* fix deps

* fix test

* update docs link

---------

Co-authored-by: hacktobeer <ramsesdebeer@gmail.com>
Co-authored-by: Aaron Peterson <aaronp@gmail.com>
jleaniz pushed a commit to jleaniz/turbinia that referenced this pull request Mar 18, 2024
jleaniz added a commit to jleaniz/turbinia that referenced this pull request Mar 18, 2024
* add workaround for pinfo warning output (google#1418)

* Update version to 20231116.1

* Fix plaso dependencies (google#1420)

* fix deps

* fix test

* Update version to 20231116.2

* Fix plaso dependencies (google#1420)

* fix deps

* fix test

* update docs link

---------

Co-authored-by: hacktobeer <ramsesdebeer@gmail.com>
Co-authored-by: Aaron Peterson <aaronp@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: plaso jobs fail when plaso >6 months old
3 participants