Jörg Stucke

I agree that this doesn't make sense. It could break some existing scripts, though. Better we discuss this in the next "quarterly"

This is not a bug: The length of the entries in the "virtual path" section is capped.

> Please add some tests to make sure this api does not regress. Also this lacks documentation. I'd suggest to add this alongside the examples already displayed on the advanced...

The screenshots you posted don't really seem unusual: The cwe_checker plugin can be very slow depending on the size and number of binaries contained in the firmware (each individual analysis...

The message "Throttling down unpacking to reduce memory consumption" is not an error. It is a built-in function that temporarily halts unpacking to reduce resource consumption. It should not interfere...

There is actually a standardized way of doing this: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files I'm not really sure what we would fill it with, though, Feel free to open a PR

In general, it is possible to start the app directly with your WSGI framework of choice but the app expects an argument containing the path to the parsed CLI args....

this minimal patch seems to be enough for just being able to start the app with default config: ```diff diff --git a/src/flask_app_wrapper.py b/src/flask_app_wrapper.py index 434c801e..a710e7a7 100644 --- a/src/flask_app_wrapper.py +++ b/src/flask_app_wrapper.py...

It seems I'm unable to reproduce this bug in the latest master version, so I guess it is fixed already

I tried running it and there seem to be problems with the "architecture_detection" plugin (which depends on the device_tree plugin) not expecting `None` as result: ```python Traceback (most recent call...