You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it was discussed in #1203 (and related issues), the failure ZIP creating routine is not armed to handle generation of ZIPs when any debug. checker is enabled. These checkers are only enabled on the most explicit user consent of all times, typing in at least-e debug.
Because at analysis we know which checkers are enabled (either via the direct invocation command or the metadata.json output), we could skip the generation of the failure ZIP in case such a checker was enabled, in which almost all cases, it could have tainted the analyzer's output.
Alternatively, looking at the Namespace value for enabled checkers, if it contains any "debug" thing, the flag which prevents failure ZIP creation (I vaguely recall the existence of such) could be turned on.
The text was updated successfully, but these errors were encountered:
As it was discussed in #1203 (and related issues), the failure ZIP creating routine is not armed to handle generation of ZIPs when any
debug.
checker is enabled. These checkers are only enabled on the most explicit user consent of all times, typing in at least-e debug
.Because at analysis we know which checkers are enabled (either via the direct invocation command or the
metadata.json
output), we could skip the generation of the failure ZIP in case such a checker was enabled, in which almost all cases, it could have tainted the analyzer's output.Alternatively, looking at the
Namespace
value for enabled checkers, if it contains any "debug" thing, the flag which prevents failure ZIP creation (I vaguely recall the existence of such) could be turned on.The text was updated successfully, but these errors were encountered: