Ada Böhm
Ada Böhm
Great work! Just two comments: - In the current version, there is no *finish_time* in task info, but there is *duration* that contains duration of the task in milliseconds. (Also...
Is this still relevant or we can close it without merge after introducing new attributes?
Hi, I am not sure what exactly @gavento meant by this todo list item. However, we should implement something like your suggestion. So "await" API should go on our list...
I have made a quick look on Python3 futures and I do not see how to simply combine futures and capnp promises (however it may still need only few lines...
We can introduce an internal fragmentation of submits to multiple calls that is composed in the server and pushed to scheduler at once. This way allows us to avoid "keeping"...
Executor (=subworker) crashing is now handled with a graceful error with logs. Governor (=worker) crash still results into overall panic.
I would also note that, maybe the protocol will be changed later, but type of events are more or less fixed and do not see any major flow in design....
@Trojan295 Great! You are right, basic summaries like task durations, number of submits, IP of client, number of tasks/object are welcome. The current dashboard now supports only the chart of...
We have made some progress with Dashboard. @Kobzol migrate whole dashboard into TypeScript and we have added task inspector and basic task summary.
Task names and tasks groups are implemented in the current master, with some basic statistics in dashboard task inspector