Closed lfcnassif closed 5 months ago
I came across this situation a few of weeks ago. However it was a small amount of negative seconds.
I came across this situation a few of weeks ago. However it was a small amount of negative seconds.
Which version have you used? Just remembered you fixed a similar issue recently in master into ParsingTask, right? I'll ask the user to try the latest snapshot.
I've had this situation before, but I didn't care.
Which version have you used?
I am 99% sure that I was using master, but I didn't take a screenshot.
Just remembered you fixed a similar issue recently in master into ParsingTask, right?
Right, but the other issue was with the elapsed time. This one affects the estimated time to finish, which is just a straightforward calculation (looking at the code). I see a couple of possible causes. I will try to reproduce it here when I get some time during this week.
This one affects the estimated time to finish, which is just a straightforward calculation (looking at the code).
Yes, AFAIK it should use just the total volume found, volume processed and current running time to compute the estimated time to finish.
PS: And those values seem fine.
Reproduced with master branch, processing a UFDR.
I managed to find the root cause and fix it. I will post more details and submit a PR tomorrow.
Reported by an user running 4.1.5 on UFDR evidence:![image](https://github.com/sepinf-inc/IPED/assets/7276994/03d86bb2-8326-41dd-9a03-0c68161b06b3)