Requests page

[klakhov]

Motivation and context

This PR introduces new page with information about data processing(status and progress). For now it will support: task creation, import/export.

For previous discussions refer to: #7537

How has this been tested?

Checklist

• I submit my changes into the develop branch
• I have created a changelog fragment
• I have updated the documentation accordingly
• I have added tests to cover my changes
• [ ] I have linked related issues (see GitHub docs)
• I have increased versions of npm packages if it is necessary
  (cvat-canvas,
  cvat-core,
  cvat-data and
  cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.

[zhiltsov-max]

1. The sorting header seems to be missing on the Requests tab. It's there on all the other tabs, but not in this one
   
2. I'd just show the downloading button on the card. I don't see the point in the actions section with just 1 button. Actions can include some additional actions, but downloading is the key purpose of these cards.
   
3. When we click export, the annotations are not downloaded automatically. To export, we need to make several extra clicks. If we export multiple tasks, this will be multiplied by the number of tasks exported. To me, it doesn't look a good decision. Probably, we can download automatically, if we know there were some downloading requests in this UI session (i.e. before the window was refreshed). If the window was reopened, the exports can be found in the list, as implemented.

[novda]

I see that the latest test runs were successful, looks like an unstable rest-api test. Marked a failed test as unstable, if any test fails which is not related to the PR, please tag me

[bsekachev]

@klakhov

Please, resolve conflicts

[klakhov]

1. The sorting header seems to be missing on the Requests tab. It's there on all the other tabs, but not in this one

The sorting/filtering functionality was not planned in this iteration

2. I'd just show the downloading button on the card. I don't see the point in the actions section with just 1 button. Actions can include some additional actions, but downloading is the key purpose of these cards.

I will think about this. We may need to re-design the card a little bit. Probably this enhancement can be moved to second iteration.

3. When we click export, the annotations are not downloaded automatically. To export, we need to make several extra clicks. If we export multiple tasks, this will be multiplied by the number of tasks exported. To me, it doesn't look a good decision. Probably, we can download automatically, if we know there were some downloading requests in this UI session (i.e. before the window was refreshed). If the window was reopened, the exports can be found in the list, as implemented.

I belive we discussed automatic downloading several times on different meetings, in the end we decided to stick with the simplier version - download by clicks(sometimes we may want to have control what we download and in what order). I agree that sometimes it can be not-so-useful. Probably there should be a setting controlling the behavior. Anyway, the feature looks like an enhancement that needs discussion.

[bsekachev]

I think Expires on on resources exported to a cloud storage may confuse users a little bit

Upd: Better to use Finished on in this case.

[bsekachev]

As discussed, let's increase default value for DATASET_CACHE_TTL.
I believe we may use 24 hours instead of 10 hours and also, avoid dividing this value by 3 for projects

File: cvat/apps/dataset_manager/views.py, line 42

CC: @zhiltsov-max

[klakhov]

I think Expires on on resources exported to a cloud storage may confuse users a little bit

Upd: Better to use Finished on in this case.

Applied

[sonarcloud]

Quality Gate passed

Issues
21 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.8% Duplication on New Code

See analysis details on SonarCloud