Right now drakcore manages its own SQLite "cache" that actually contains a whole list of analyses even if user can see only 100 of them in the web interface...
It's another "movable part" that is pretty unobvious to maintain so I decided to replace it with analysis status tracking based on Redis. Analysis status is marked both by drakrun part and drakcore (when user submits analysis using web interface, analysis is registered with "pending" status)
There still some UX issues, but it's a step forward.
As a part of this PR, I also removed drakcore.postprocess completely.
Right now drakcore manages its own SQLite "cache" that actually contains a whole list of analyses even if user can see only 100 of them in the web interface...
It's another "movable part" that is pretty unobvious to maintain so I decided to replace it with analysis status tracking based on Redis. Analysis status is marked both by drakrun part and drakcore (when user submits analysis using web interface, analysis is registered with "pending" status)
There still some UX issues, but it's a step forward.
As a part of this PR, I also removed drakcore.postprocess completely.