Project

General

Profile

Actions
Copy link

Feature #8299

closed

Implement a new request to get statuses of solving tasks

Added by Ilja Zakharov over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Vladimir Gratinskiy
Category:
Bridge
Target version:
0.2
Start date:
07/17/2017
Due date:
07/18/2017
% Done:

0%

Estimated time:
Published in build:

Description

To decrease the number of requests from Core to Bridge to get statuses of solving tasks there is an idea to implement another one request to get all statuses within the one json file.

Related issues 1 (0 open — 1 closed)

Blocks Klever - Feature #6906: Make VTG strategies task decision requests delay configurableClosedIlja Zakharov02/26/2016

Actions
Actions
Copy link
 #1

Updated by Ilja Zakharov over 7 years ago

As soon as I describe in the specification all necessary changes, I will reassign the task.

Actions
Copy link
 #2

Updated by Ilja Zakharov over 7 years ago

  • Assignee changed from Ilja Zakharov to Vladimir Gratinskiy

Please, find all necessary changes in the corresponding specification.

Actions
Copy link
 #3

Updated by Vladimir Gratinskiy over 7 years ago

  • Due date set to 07/18/2017
  • Status changed from New to Resolved
Implemented in feature_8299. Changes:
  • url "/service/get_task_status/" was replaced with "/service/get_tasks_statuses/";
  • Parameter "task id" (str) for this POST request was repalced with "tasks" (json str - list of task idetnifiers);
  • Return data "task status" (str) was replaces with "tasks statuses" (json str):
    {'pending': <list of tasks ids>, 'processing': <list of tasks ids>, 'finished': <list of tasks ids>, 'error': <list of tasks ids>}
Actions
Copy link
 #4

Updated by Ilja Zakharov over 7 years ago

Thanks! I will provide feedback as soon as I fix independent task managing in VTG.

Actions
Copy link
 #5

Updated by Evgeny Novikov about 7 years ago

  • Target version set to 2.0
Actions
Copy link
 #6

Updated by Evgeny Novikov about 7 years ago

Looks like it works and the branch was merged to branch core-refactoring.

Actions
Copy link
 #7

Updated by Evgeny Novikov about 7 years ago

  • Target version changed from 2.0 to 0.2

The related considerable Core refactoring is always completed and it would be better to have it in master ASAP while Klever 1.0 will be devoted to great conceptual improvements.

Actions
Copy link
 #8

Updated by Evgeny Novikov about 7 years ago

  • Status changed from Resolved to Closed

I merged the branch to master in aec48ac1.

Actions
Copy link

Also available in: Atom PDF