Turning the entire line to status color itself will help a lot to identify in large listed data, Something like compated to dirsearch with large listed output data will be helpful

Just lost my status screens with few billions of execs :(
So, my ideas:

1. Can we store all the fuzzer stats as shown in status screen, and then restore it when resuming (with both AFL_AUTORESUME and '-i' option) ? If it somehow affects or depends on inner state of AFL++ instance, can we restore this inner state too?
2. Can we prevent random Ctrl+C presses for example, by asking to confirm? You

Once #1475 is complete, populate part data for all parts that fabric documentation exists for. #1475 should be done first to avoid duplicating all of the fabric data repeatedly.

Feature request

Is your feature request related to a problem? Please describe

The analysis.py script provides just one confidence interval: 95%. While that is related to the 2-sigma interval of normal distribution, so in theory allows for easy estimation of bigger confidence intervals (like 3, 4, 5-sigma), it assumes a normal distribution, which the differences don't follow, and may be

GRR uses GRANARY_ASSERT, which is kind of a weird holdover from writing DBTs that can't depend on system libraries, and it's also very C-like. Now that we've made GRR start using cxx-common, we could easily upgrade it to use Google Log's CHECK macro.