Klever

Suggestion: Since the majority of reports are safe verdicts (for example, for some task there are 77057 safes, 43 unsafes and 5572 unknowns), maybe we should not add verifier log to them, especially if we can access the log from the verifier component and most likely the user does not need them. Also in LDV Tools we added only N (which can be specified by the user) last lines of log to the report instead of the whole log.

For your first suggestion there are already opened issues: #6597 and #6598. Anyway these logs should have the way to get into the database - corresponding issues suggest to do this by default in the development mode.

Your second suggestion requires some analysis. I don't understand a good default value of N. Should it depend on verifier (its version/configuration)? It should be enough to catch verifier issues that can be somewhere in the middle of the log files. I guess that more reasonable is to cut off various debug and statistics information if the user asked so at the job start decision page (this can be done by default in the production mode). Anyway please open another issue for this, since this issue should be just for uploading optimizations in Bridge.

Feedback: Using production mode helps to significantly reduce size of an archive (in around 5 times), which also reduces time of its downloading.