Skip to content

Import Meta AI Parser cloud plugins. - #429

Open
Jadoo4QFan wants to merge 1 commit into
abrignoni:mainfrom
Jadoo4QFan:patch-2
Open

Import Meta AI Parser cloud plugins.#429
Jadoo4QFan wants to merge 1 commit into
abrignoni:mainfrom
Jadoo4QFan:patch-2

Conversation

@Jadoo4QFan

Copy link
Copy Markdown
Contributor

Imported from the Meta AI parser on your repo, but stripped of artifacts fit for ALEAPP. No reason for it to be a standalone parser that most investigators will never hear about that actually needed, with a complicated setup process on top of it.

Imported from the Meta AI parser on your repo, but stripped of artifacts fit for ALEAPP.
@abrignoni

Copy link
Copy Markdown
Owner

Thanks for the contribution!

This PR changes artifact modules without test data for them. A small fixture with each artifact change lets reviewers run the module against real data, and the committed case keeps guarding the module after merge.

  • meta_ai.py: please include a fixture with this PR.

Adding a fixture

Generate it from your extraction with the helper (details in create_module_test_cases.md):

python admin/test/scripts/make_test_data.py <module> --case <case_number> --input <extraction.zip>

It writes admin/test/cases/testdata.<module>.json and one zip per artifact under admin/test/cases/data/<module>/.

Size rules:

  • Under 10 MB per zip: commit the files in this PR.
  • 10 to 25 MB: commit the case JSON in the PR and attach the zip to a comment here.
  • Over 25 MB: say so here and a maintainer will arrange a handoff.

If your extraction cannot be shared:

  • If the app appears on a public research image, generate the fixture from that instead. public_corpus_images.md lists the images and where to download them.
  • Or sanitize the real file in place: keep the file the app wrote and overwrite only the personal values, which keeps the format honest.
  • Or script a known session: install the app on a test device with a throwaway account, perform documented actions, and extract that.

If none of those fit, say so here and we will work it out. The PR can still be reviewed and merged with the gap recorded in the artifact's notes.

This is a request, not a gate. Nothing here blocks review.

@abrignoni abrignoni added the needs-test-data Artifact PR without test data for the changed modules label Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-test-data Artifact PR without test data for the changed modules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants