ScansWatcher: on_scan_finished can be called with a STOPPING event
While playing with ScansWatcher
, i have noticed that at the on_scan_finished
callback, the state from the metadata can differ from the final scan state
Basically the state can be STOPPING
.
I would only expect one of
DONE
USER_ABORTED
KILLED
Could it be fixed?