mvt-project / mvt-project/androidqf
Inconsistent data extracted depending on platform run on.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 281
- Forks
- 48
- Avg merge
- 1h 28m
- Merged PRs (30d)
- 2
Description
I still have to dig into this a bit more but when testing the #36 patch, I've noticed that running androidqf against the same phone on each of the supported host platforms you get different levels of extracted data.
$ du -sh ./*
650M ./linux-be2e5867-59b8-421a-adc3-77cb88fe879d
452M ./macos-8545199d-57a7-448c-b4e5-457a409fbaaa
257M ./windows-8d7baa53-8b2b-4e8e-977e-84fd9967ca60
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Reproduce androidqf against the same phone on Linux, macOS, and Windows, then compare the extracted data and the output sizes shown in the report. Done means the platform-dependent extraction difference is fixed or its cause and expected behavior are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, go
- Domain
- mobile-dev, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100