Matteo Lodi

nvm the error is for `AssertionError: Analyzer DroidLysis with config Droidlysis and mimetype application/vnd.android.package-archive failed Report is empty. Reason: None` itself. There's some lower level debugging to do here and...

oh nou, dependency conflicts... I think it makes sense to add this tool in the "malware_tools_analyzers" too with its own python environment. That's the only way to avoid becoming mad

about the doc file, now you need to change it here: https://github.com/intelowlproject/docs/blob/main/docs/IntelOwl/usage.md I'll update the PR template

> the test fails here is due to [this](https://github.com/intelowlproject/IntelOwl/commit/34c3c674337a4142cee42eb5a9ea68f5ffaee239#diff-08232e15f369f213f74eca8cbc14f0c12f515e35aeecf9e50b0701712b4842ba) last commit made in the develop branch. That was a mistake of mine. You can readd that package

once fixed those, the PR is gtg

yes, you can create a PR request in that `docs` repository, just once

I think tests are failing cause in the "normal" CI (see [here](https://github.com/intelowlproject/IntelOwl/blob/master/.github/workflows/pull_request_automation.yml#L80) ) we don't execute the malware tools container because it's too heavy. It would be cool to find...

> So we need docker analyser tests to run only when the particular container is up? no you are right, I checked again and this is not necessary > If...

looking at the other goresym analyzer, the only things that changes is that you created 2 different migrations instead of a single one. You can try by adding first a...

one thing missing: you commented some code while testing, can you remove it? plus, migrations order, let's do that in this order: * mobsf * droidlys * apk artifacts and...