196 scanning cannot be completed correctly

[BenediktMKuehne]

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

work-around for db timeouts

What is the current behavior? (You can also link to an open issue here)

problems with long scans

What is the new behavior (if this is a feature change)? If possible add a screenshot.

fixed?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

no

[torabi12]

Something not ok on my side. I downloaded this:

$ git clone --branch 196-scanning-cannot-be-completed-correctly https://github.com/BenediktMKuehne/embark.git

Uploaded the iso from the bug:
android-x86_64-9.0-r2.iso

when I hit Analyze I get 500:

[torabi12]

Only the android-x86_64-9.0-r2.iso dropped 500, I tried another binary and EMBArk is started the scan:

[torabi12]

I started a new test with a binary that was never available under EMBArk.
I hope this will show that the web site can handle long runs.

[torabi12]

The scan in EMBArk has been running since 2 and half days and I think it will never finish:

I try to execute the same in emba to see the running time.

[BenediktMKuehne]

fixed problems with APK extractor log output