Describe the bug
In the global scan progress line the time estimation goes to 0s after a time of the program running.
To Reproduce
This bug should be automatically reproducible. I have witnessed it in the following scenarios:
A scan finishes and another concurrent scan takes its place.
You open the Scan Management Menu and add a manual additional url to scan.
Expected behavior
The total time estimator should output the estimated time. Instead it is displaying "0s"
Describe the bug In the global scan progress line the time estimation goes to 0s after a time of the program running.
To Reproduce This bug should be automatically reproducible. I have witnessed it in the following scenarios: A scan finishes and another concurrent scan takes its place. You open the Scan Management Menu and add a manual additional url to scan.
Expected behavior The total time estimator should output the estimated time. Instead it is displaying "0s"
Traceback / Error Output [##############>-----] - 45m 104568/140835 >>> 0s <<< found:12 errors:0
Environment (please complete the following information):
Additional context