ipazc / oculus-crawl Goto Github PK

This issue happens the first time the crawler is initiated on a machine and the factory does not contain any dataset request available. Eventually it will collapse the machine's resources, spawning and leaking on process each second.
Nonetheless, a crawler that has already processed requests previously and is still running does not show this behavior.

When showing the output, Oculus-Crawl tries to reuse same lines to print its state not taking into account the size of the window, leading to an incorrect display order when console size is smaller than the length of the lines.

Docker complains about using both flags (-d and --rm) at the same time.