| 822f87b | Kirill Lakhov | 06 March 2023, 08:46:10 UTC | Reset notifications on login/logout/register (#5788) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Just simple UX improvement that allows to hide notifications on login/logout. For example if we entered wrong credentials, and then logined successfully, notification is still on the screen. ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 06 March 2023, 08:46:10 UTC |
| 7ecda9f | Saif Khan | 05 March 2023, 07:48:00 UTC | Minor English-language improvements in installation.md (#5805) | 05 March 2023, 07:48:00 UTC |
| 8df8b1f | Andrey Zhavoronkov | 02 March 2023, 12:32:22 UTC | Updated analytics section of k8s guide (#5796) | 02 March 2023, 12:32:22 UTC |
| 5784556 | Boris Sekachev | 02 March 2023, 12:27:51 UTC | Fixed models running with a new API (#5798) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 02 March 2023, 12:27:51 UTC |
| a313fd1 | Maria Khrustaleva | 02 March 2023, 12:22:41 UTC | Fix missing CVAT_BASE_URL env (#5792) | 02 March 2023, 12:22:41 UTC |
| 9ac1272 | Kirill Sizov | 02 March 2023, 12:08:17 UTC | Fix cache workflow (#5799) | 02 March 2023, 12:08:17 UTC |
| e3e4230 | Kirill Sizov | 02 March 2023, 10:16:40 UTC | Disable django check for number of upload files (#5790) | 02 March 2023, 10:16:40 UTC |
| 15cbbbb | Andrey Zhavoronkov | 02 March 2023, 08:39:42 UTC | Minor improvements of monitoring dashboard (#5795) | 02 March 2023, 08:39:42 UTC |
| 1c9bc48 | Maria Khrustaleva | 02 March 2023, 08:38:33 UTC | [UI] SSO OIDC (#5684) | 02 March 2023, 08:38:33 UTC |
| 29be40d | Kirill Lakhov | 01 March 2023, 17:31:31 UTC | Hide analytics link from non-admin users (#5789) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Default user does'nt have access to Analytics page, so there is no reason to show Analytics link in the header ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 01 March 2023, 17:31:31 UTC |
| d0c7aa2 | Kirill Sizov | 28 February 2023, 18:02:56 UTC | Allow lambda requests for worker user (#5785) | 28 February 2023, 18:02:56 UTC |
| 19719a0 | Maria Khrustaleva | 28 February 2023, 14:21:23 UTC | Update djnago allauth version (#5768) | 28 February 2023, 14:21:23 UTC |
| d2fa246 | Anastasia Yasakova | 28 February 2023, 14:20:51 UTC | Remove social authentication from running-tests.md (#5777) | 28 February 2023, 14:20:51 UTC |
| 39930ee | Andrey Zhavoronkov | 28 February 2023, 14:19:33 UTC | helm new analytics support (#5783) | 28 February 2023, 14:19:33 UTC |
| cdb4eb0 | Boris Sekachev | 28 February 2023, 10:33:29 UTC | Fixed freezing browser when request a job by NaN id (#5763) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Resolved #5581 <img width="917" alt="image" src="https://user-images.githubusercontent.com/40690378/221108673-5f1b78fd-1f92-440f-a27f-bd46806fdc74.png"> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [x] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 28 February 2023, 10:33:29 UTC |
| 783c7a5 | Andrey Zhavoronkov | 27 February 2023, 10:18:05 UTC | Fixed missed job_id for Issue and Comment models (#5772) | 27 February 2023, 10:18:05 UTC |
| 838f1da | Maxim Zhiltsov | 26 February 2023, 15:19:22 UTC | Allow typed simple filters (#5760) | 26 February 2023, 15:19:22 UTC |
| a491c56 | Andrey Zhavoronkov | 26 February 2023, 15:15:28 UTC | Send backend (mod_wsgi + rq_workers) exceptions into clickhouse db (#5743) | 26 February 2023, 15:15:28 UTC |
| 77d33eb | Anastasia Yasakova | 24 February 2023, 11:14:01 UTC | Add test to remove project data (#5752) - Added test to remove project data (#5632) | 24 February 2023, 11:14:01 UTC |
| 8dc272f | Anastasia Yasakova | 24 February 2023, 08:32:07 UTC | Fix /api/tasks leads to 500 server error (#5700) - Fixed re-deleting of skeleton sublabels (attempt to remove already removed sublabels)  - Updated Label model (added `project` to `unique_together`) - Added migration to remove or rename wrong labels | 24 February 2023, 08:32:07 UTC |
| 05b9941 | Mariia Acoca | 24 February 2023, 08:20:36 UTC | Cloud storages documentation update (#5741) | 24 February 2023, 08:20:36 UTC |
| 4351d7a | Kirill Lakhov | 23 February 2023, 15:03:03 UTC | Fixed bug: some models are not shown (#5754) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> It seems after merging #5575 we need to get models in a new way. If we are sending default request(without page params, only first page is returned). This pr users fetchAll function to fetch models. Also fixes bug with incorrect 0 in result.count if there is only one page. Model page pagination should work fine when all models would be correctly fetched ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - ~~[ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file~~ - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 23 February 2023, 15:03:03 UTC |
| 48a57c9 | Boris Sekachev | 23 February 2023, 14:13:48 UTC | Fixed infinite preview loading for cloud storages (#5759) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Resolved #5727 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 23 February 2023, 14:13:48 UTC |
| 43da7ab | Boris Sekachev | 23 February 2023, 14:13:32 UTC | Lock 'Ok' button when there is no selected file to upload (#5757) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Resolved #5633 Also fixed storage selection when uploading a dataset <img width="268" alt="image" src="https://user-images.githubusercontent.com/40690378/220912019-b0596c2d-94f4-4b8f-a26f-18b0cfb6efa4.png"> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [x] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 23 February 2023, 14:13:32 UTC |
| 3066c6e | Maria Khrustaleva | 22 February 2023, 19:37:32 UTC | [Social authentication] Remove server part && tests (#5691) | 22 February 2023, 19:37:32 UTC |
| f7838b1 | Maxim Zhiltsov | 22 February 2023, 19:19:10 UTC | Add spell checker extension to recommendations (#5756) Often, there are typos in the code and documentation. This PR tries to prevent them in future by adding a recommendation to install a VS code extension. | 22 February 2023, 19:19:10 UTC |
| 909ce1b | Kirill Lakhov | 22 February 2023, 13:28:14 UTC | Updated logo on main/docs sites (#5753) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> - Changed Logo in header - Changed favicon ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - ~~[ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file~~ - [x] I have updated the documentation accordingly - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 22 February 2023, 13:28:14 UTC |
| bad1dc2 | Maxim Zhiltsov | 21 February 2023, 20:00:59 UTC | Update changelog (#5748) Updates changelog after #5662 | 21 February 2023, 20:00:59 UTC |
| e95aa38 | Maxim Zhiltsov | 21 February 2023, 15:50:39 UTC | Fix debug configurations for vs code (#5708) - Fixed naming and added a missing debug config for rq workers | 21 February 2023, 15:50:39 UTC |
| d0c419c | Roman Donchenko | 21 February 2023, 15:46:34 UTC | cvat-sdk/gen/postprocess.py: don't suppress exceptions from `process_file` (#5740) Suppressing the exception means that the script returns a success exit code (preventing errors from being noticed) and that the stacktrace is omitted from the output (preventing errors from being easily analyzed). | 21 February 2023, 15:46:34 UTC |
| 76f7156 | Roman Donchenko | 21 February 2023, 15:25:21 UTC | Remove the /analytics endpoints from the OpenAPI schema (#5745) As far as I can tell, these aren't supposed to be part of the public API, and they break the SDK generator due to not being in the `/api/` namespace (if you get the schema from a server with analytics enabled). | 21 February 2023, 15:25:21 UTC |
| 36e1220 | Boris Sekachev | 21 February 2023, 15:24:22 UTC | Instrumented more buttons (#5738) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 21 February 2023, 15:24:22 UTC |
| 40931e7 | Roman Donchenko | 21 February 2023, 15:24:15 UTC | Fix slow shutdown for the Grafana container (#5746) The root process of the container is `/bin/sh`, which ignores the initial `SIGTERM` that Docker sends. So Docker has to wait 10 seconds and then kill everything with `SIGKILL`. Make Grafana itself the root process instead. Grafana handles the `SIGTERM` and shuts down quickly. | 21 February 2023, 15:24:15 UTC |
| 4fc494f | Maxim Zhiltsov | 21 February 2023, 15:23:32 UTC | Remove collections in endpoints (#5662) This PR is focused on server performance optimization for requests with collections. - Collections with user-controlled size are removed from server output and replaced with structures providing links to the matching paginated endpoints and summary info: - /api/projects/{id}.tasks -> /api/tasks?project_id={id} - /api/tasks/{id}.segments -> /api/jobs?task_id={id}: .start_frame, .stop_frame - /api/jobs/{id}.issues -> /api/issues?job_id={id} - /api/issues/{id}.comments -> /api/comments?issue_id={id} - /api/projects | tasks | jobs/{id}.labels -> /api/labels? project_id|task_id|job_id={id} - Added Label-related endpoints: - /api/labels (GET) - /api/labels/{id} (GET, PATCH, DELETE) - PATCH and DELETE both cannot be used for sublabels - Added and updated tests - Removed unused test server data - Added several new cases with skeletons and ownerships - Fixed possible problems with duplicate labels appearing on renaming | 21 February 2023, 15:23:32 UTC |
| e816bbf | Roman Donchenko | 20 February 2023, 16:18:59 UTC | SDK: Add organization support to the high-level layer (#5718) This consists of two parts: * API to work with organizations; * API to work with other resources in the context of an organization. | 20 February 2023, 16:18:59 UTC |
| f88ee3f | Roman Donchenko | 20 February 2023, 15:16:41 UTC | Make Python shebang lines refer to `python3` (#5739) All scripts require Python 3; this change lets them be used in environments where `python` is either Python 2 or missing. `email_settings.py` is not a script, so it doesn't need a shebang line at all. | 20 February 2023, 15:16:41 UTC |
| e8024a9 | Kirill Lakhov | 20 February 2023, 14:16:23 UTC | Fix excessive notifications (#5737) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> This PR fixes two annoying notifications: 1. On models page if there is no models (Resolves #5728) 2. On login page if token sesssion is expired ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 20 February 2023, 14:16:23 UTC |
| 27224f2 | Andrey Zhavoronkov | 18 February 2023, 20:35:56 UTC | Audit logs (#5646) | 18 February 2023, 20:35:56 UTC |
| 8956a36 | PMazarovich | 17 February 2023, 10:39:21 UTC | UI change frame optimization (#5657) ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Currently user have to delete current frame and enter needed one, then press enter. With this change, when user click on InputNumber, this field automatically clears and user don't need to do it manually. ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> It was tested manually ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: Boris Sekachev <sekachev.bs@gmail.com> | 17 February 2023, 10:39:21 UTC |
| 0ae8952 | Nikita Manovich | 17 February 2023, 10:24:01 UTC | Remove werkzeug dependency | 17 February 2023, 10:24:01 UTC |
| 55c613a | Kirill Lakhov | 17 February 2023, 08:19:49 UTC | Added test for missing authentication token (#5450) <!-- Raised an issue to propose your change (https://github.com/cvat-ai/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [CONTRIBUTION](https://github.com/cvat-ai/cvat/blob/develop/CONTRIBUTING.md) guide. --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Related #5331 Added test, changed fix because of temporary solutions in #5344 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable by a reason then ~~explicitly strikethrough~~ the whole line. If you don't do that github will show an incorrect process for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into [CHANGELOG](https://github.com/cvat-ai/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the [documentation]( https://github.com/cvat-ai/cvat/blob/develop/README.md#documentation) accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues ([read github docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/cvat-ai/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/cvat-ai/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/cvat-ai/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/cvat-ai/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: Maya <maya17grd@gmail.com> | 17 February 2023, 08:19:49 UTC |
| ba97625 | Roman Donchenko | 16 February 2023, 20:09:33 UTC | Add online documentation for the PyTorch adapter (#5703) | 16 February 2023, 20:09:33 UTC |
| 771c13c | Boris Sekachev | 15 February 2023, 15:16:19 UTC | Added cypress test for 3D cuboids interpolation (#5699) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 15 February 2023, 15:16:19 UTC |
| f38e87a | Snyk bot | 15 February 2023, 10:47:48 UTC | [Snyk] Security upgrade django from 3.2.17 to 3.2.18 (#5709) <h3>Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.</h3> #### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - cvat/requirements/base.txt <details> <summary>⚠️ <b>Warning</b></summary> ``` Jinja2 3.1.2 requires MarkupSafe, which is not installed. h5py 3.6.0 requires numpy, which is not installed. azure-storage-blob 12.13.0 requires cryptography, which is not installed. ``` </details> #### Vulnerabilities that will be fixed ##### By pinning: Severity | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|:-------------------------|:-------------------------|:-------------------------|:-------------------------  | Denial of Service (DoS) <br/>[SNYK-PYTHON-DJANGO-3319450](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-3319450) | `django:` <br> `3.2.17 -> 3.2.18` <br> | No | No Known Exploit Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded. Check the changes in this PR to ensure they won't cause issues with your project. ------------ **Note:** *You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.* For more information: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiJjYTZlODVhMS1jNjNlLTQyMzAtOTUxNC1hNjZiMjc0NTg1ODUiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6ImNhNmU4NWExLWM2M2UtNDIzMC05NTE0LWE2NmIyNzQ1ODU4NSJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source=github&utm_medium=referral&page=fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source=github&utm_medium=referral&page=fix-pr/settings) 📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities) [//]: # (snyk:metadata:{"prId":"ca6e85a1-c63e-4230-9514-a66b27458585","prPublicId":"ca6e85a1-c63e-4230-9514-a66b27458585","dependencies":[{"name":"django","from":"3.2.17","to":"3.2.18"}],"packageManager":"pip","projectPublicId":"4bbc4b80-3fb9-4009-a7bb-51016d44946b","projectUrl":"https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-PYTHON-DJANGO-3319450"],"upgrade":[],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","pr-warning-shown"],"priorityScoreList":[null]}) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Denial of Service (DoS)](https://learn.snyk.io/lessons/redos/javascript/?loc=fix-pr) | 15 February 2023, 10:47:48 UTC |
| 3c8d67c | Roman Donchenko | 15 February 2023, 10:47:11 UTC | Build the documentation as part of PR checks (#5711) I broke the documentation build in #5678 and I want to make sure it doesn't happen again. | 15 February 2023, 10:47:11 UTC |
| f52902b | Anastasia Yasakova | 15 February 2023, 10:44:34 UTC | Fix redundant writing of skeleton annotations (CVAT for images) (#5387) Fixed #5279 | 15 February 2023, 10:44:34 UTC |
| 4c32be5 | Roman Donchenko | 15 February 2023, 06:10:51 UTC | Fix the documentation build (#5704) In #5678, I thought that the extra README that eventually ended up in `cvat-sdk/docs/README.md` was unused, which turned out to be not quite true. One section from it _was_ used to generate the online API index page. Since I removed the file, the online docs now fail to build. Rather than restore the entire README, restore just that one section as a standalone file. This achieves the same result as before, but with simpler code. | 15 February 2023, 06:10:51 UTC |
| 86a0d51 | Andrey Zhavoronkov | 14 February 2023, 15:31:29 UTC | fix empty redis password (#5702) | 14 February 2023, 15:31:29 UTC |
| 87f07fd | Roman Donchenko | 14 February 2023, 09:39:55 UTC | Various improvements to the SDK generation process (#5678) | 14 February 2023, 09:39:55 UTC |
| 89f403b | Roman Donchenko | 13 February 2023, 21:24:39 UTC | Fix typos/misspellings in the documentation (#5687) | 13 February 2023, 21:24:39 UTC |
| 1ab80f8 | Roman Donchenko | 13 February 2023, 21:23:30 UTC | SDK: Remove unused module (#5695) | 13 February 2023, 21:23:30 UTC |
| e601270 | Kirill Lakhov | 13 February 2023, 09:28:58 UTC | Upgrade Cypress to 12.x (#5681) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 13 February 2023, 09:28:58 UTC |
| a72f5d1 | Andrey Zhavoronkov | 12 February 2023, 15:11:54 UTC | Added more logs to try debuging the issue with labels (#5694) | 12 February 2023, 15:11:54 UTC |
| 6bf098c | Kirill Sizov | 10 February 2023, 09:18:36 UTC | Fix version of buildx for full.yml workflow (#5692) | 10 February 2023, 09:18:36 UTC |
| c06e91d | Nikita Manovich | 10 February 2023, 08:15:26 UTC | Enhance readme, add information about Enterprise Support (#5690) | 10 February 2023, 08:15:26 UTC |
| 912e47e | Kirill Lakhov | 08 February 2023, 16:08:52 UTC | Added special description to built-in models (#5682) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 08 February 2023, 16:08:52 UTC |
| 5e0160b | Boris Sekachev | 08 February 2023, 14:45:42 UTC | Supported interpolation for 3D cuboids (#5629) | 08 February 2023, 14:45:42 UTC |
| b263d87 | Kirill Sizov | 08 February 2023, 11:57:15 UTC | [Snyk] Security upgrade django from 3.2.16 to 3.2.17 (#5665) <p>This PR was automatically created by Snyk using the credentials of a real user.</p><br /><h3>Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.</h3> #### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - cvat/requirements/base.txt <details> <summary>⚠️ <b>Warning</b></summary> ``` Jinja2 3.1.2 requires MarkupSafe, which is not installed. h5py 3.6.0 requires numpy, which is not installed. azure-storage-blob 12.13.0 requires cryptography, which is not installed. ``` </details> #### Vulnerabilities that will be fixed ##### By pinning: Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:-------------------------  | **551/1000** <br/> **Why?** Recently disclosed, Has a fix available, CVSS 5.3 | Denial of Service (DoS) <br/>[SNYK-PYTHON-DJANGO-3266406](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-3266406) | `django:` <br> `3.2.16 -> 3.2.17` <br> | No | No Known Exploit (*) Note that the real score may have changed since the PR was raised. Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded. Check the changes in this PR to ensure they won't cause issues with your project. ------------ **Note:** *You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.* For more information: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiJiZTIyZjVmOS03Y2IzLTRiYmEtODdjZS0xOGY1ZDIzZmFkNmUiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6ImJlMjJmNWY5LTdjYjMtNGJiYS04N2NlLTE4ZjVkMjNmYWQ2ZSJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source=github&utm_medium=referral&page=fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source=github&utm_medium=referral&page=fix-pr/settings) 📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities) [//]: # (snyk:metadata:{"prId":"be22f5f9-7cb3-4bba-87ce-18f5d23fad6e","prPublicId":"be22f5f9-7cb3-4bba-87ce-18f5d23fad6e","dependencies":[{"name":"django","from":"3.2.16","to":"3.2.17"}],"packageManager":"pip","projectPublicId":"4bbc4b80-3fb9-4009-a7bb-51016d44946b","projectUrl":"https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-PYTHON-DJANGO-3266406"],"upgrade":[],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","pr-warning-shown","priorityScore"],"priorityScoreList":[551]}) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Denial of Service (DoS)](https://learn.snyk.io/lessons/redos/javascript/?loc=fix-pr) --------- Co-authored-by: snyk-bot <snyk-bot@snyk.io> Co-authored-by: Nikita Manovich <nikita@cvat.ai> | 08 February 2023, 11:57:15 UTC |
| 4a45321 | Kirill Sizov | 08 February 2023, 11:41:24 UTC | Fix Helm tests (#5579) | 08 February 2023, 11:41:24 UTC |
| e24bace | Kirill Lakhov | 07 February 2023, 07:38:27 UTC | Fixed model pagination (#5674) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 07 February 2023, 07:38:27 UTC |
| e194f5b | Mariia Acoca | 06 February 2023, 10:23:13 UTC | Banner for welcome mail (#5650) | 06 February 2023, 10:23:13 UTC |
| 2ab66fc | Kirill Sizov | 03 February 2023, 18:08:49 UTC | Remove limit manager (#5642) | 03 February 2023, 18:08:49 UTC |
| 654ff12 | Mariia Acoca | 03 February 2023, 17:00:57 UTC | Context images docs update (#5659) | 03 February 2023, 17:00:57 UTC |
| 8eb5ce0 | dependabot[bot] | 03 February 2023, 16:09:18 UTC | Bump http-cache-semantics from 4.1.0 to 4.1.1 (#5663) Bumps [http-cache-semantics](https://github.com/kornelski/http-cache-semantics) from 4.1.0 to 4.1.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/kornelski/http-cache-semantics/commit/24496504352199caf360d1b4d4a01efdc8a7249e"><code>2449650</code></a> Update mocha</li> <li><a href="https://github.com/kornelski/http-cache-semantics/commit/560b2d8ef452bbba20ffed69dc155d63ac757b74"><code>560b2d8</code></a> Don't use regex to trim whitespace</li> <li><a href="https://github.com/kornelski/http-cache-semantics/commit/b1bdb92638426fab978f31e1330b6833015cabf0"><code>b1bdb92</code></a> Remove linting package zoo</li> <li><a href="https://github.com/kornelski/http-cache-semantics/commit/c20dc7eeca608339143857953ee7ed9343fe6d3d"><code>c20dc7e</code></a> Cache 308</li> <li>See full diff in <a href="https://github.com/kornelski/http-cache-semantics/compare/v4.1.0...v4.1.1">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/opencv/cvat/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | 03 February 2023, 16:09:18 UTC |
| 0280b5f | Maxim Zhiltsov | 03 February 2023, 16:07:05 UTC | Add simple filters for collections (#5575) Added simple filter queries for collections in the server API. Such queries should cover simpler cases, while more complex filters should use the JSON syntax. - Added simple filters for collection endpoints in API (e.g. `/tasks?project_id=42&user=myusername`) - Removed duplicating collection endpoints in API in favor of their full versions: - `/projects/{id}/tasks` -> `/tasks?project_id={id}` - `/tasks/{id}/jobs` -> `/jobs?task_id={id}` - `/jobs/{id}/issues` -> `/issues?job_id={id}` - `/issue/{id}/comments` -> `/comments?issue_id={id}` - Corresponding owning objects now return a link to the collection: - `/projects/{id}`: `.tasks` - `/tasks/{id}`: `.jobs` - `/jobs/{id}`: `.issues` - `/issue/{id}`: `.comments` - Fixed errors in the generated server API schema: - Input and output types in all the basic model methods (`Create`, `Update`, `Retrieve`, `Delete`) - Removed invalid separation for the project list operation response type - File structure for projects in the dataset cache is updated to store the new project representation. Old caches will be invalidated. - Added tests | 03 February 2023, 16:07:05 UTC |
| ba49fc4 | Maria Khrustaleva | 02 February 2023, 18:49:33 UTC | Remove limit on maximum number of manifest files that can be added for cloud storage (#5660) | 02 February 2023, 18:49:33 UTC |
| 4df7c4c | Anastasia Yasakova | 01 February 2023, 16:46:12 UTC | Fix SiamMask and TransT serverless functions (#5658) While deploying I got the following error: ``` ./Miniconda3-latest-Linux-x86_64.sh: 438: [[: not found ./Miniconda3-latest-Linux-x86_64.sh: 444: [[: not found CondaFileIOError: '/root/miniconda3/pkgs/envs/*/env.txt'. [Errno 2] No such file or directory: '/root/miniconda3/pkgs/envs/*/env.txt' ``` | 01 February 2023, 16:46:12 UTC |
| 051316d | Kirill Lakhov | 01 February 2023, 15:07:40 UTC | Hotfix: Fix models page issues (#5655) - Added pagination - Fixed trackers & interactors | 01 February 2023, 15:07:40 UTC |
| f82d7f5 | Roman Donchenko | 01 February 2023, 09:03:16 UTC | Fix most ESLint errors/warnings in tests (#5647) After this, there's only 12 files with ESLint errors left. I didn't fix those because they all have at least one `cypress/no-unnecessary-waiting` error, and I don't have enough Cypress expertise to fix those. | 01 February 2023, 09:03:16 UTC |
| 3775bc2 | Kirill Lakhov | 30 January 2023, 19:44:51 UTC | New models UI (#5635) | 30 January 2023, 19:44:51 UTC |
| 91b36ce | Roman Donchenko | 30 January 2023, 19:08:30 UTC | Replace appdirs with platformdirs (#5644) Turns out, appdirs is not very well maintained; even its own README suggests switching: <https://github.com/ActiveState/appdirs>. | 30 January 2023, 19:08:30 UTC |
| d99125a | Nikita Manovich | 27 January 2023, 15:55:38 UTC | Clean up data when a project is deleted (#5632) Fix https://github.com/opencv/cvat/issues/5595 | 27 January 2023, 15:55:38 UTC |
| 7b86ed8 | Kirill Sizov | 26 January 2023, 12:38:35 UTC | Use 'ParseError' instead of 'BadRequest' (#5625) When we use `BadRequest` our responses doesn't contain error message, so it's better to use exceptions from `rest_framework.exceptions` | 26 January 2023, 12:38:35 UTC |
| d5f3f93 | Roman Donchenko | 25 January 2023, 12:10:01 UTC | Allow the documentation website to be indexed by search engines (#5623) Our HTML documentation template slaps a `<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">` on every page unless the `HUGO_ENV` environment variable is set to `production`, thereby excluding the entire documentation website from web search results. Set the variable to fix it. This behavior is inherited from Docsy, although they have changed it since: <https://github.com/google/docsy/pull/653>. | 25 January 2023, 12:10:01 UTC |
| 64fc53e | Roman Donchenko | 25 January 2023, 10:41:14 UTC | Update issue and pull request templates (#5620) * Move the reproduction recipe above the expected & actual behavior. Otherwise it's a bit awkward to fill out the template, because you have to describe what happens before you describe how to get there. * Fix references to the old `cvat-ai/cvat` GitHub project. * Update/remove broken links. * Fix wording. <!-- Raised an issue to propose your change (https://github.com/cvat-ai/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [CONTRIBUTION](https://github.com/cvat-ai/cvat/blob/develop/CONTRIBUTING.md) guide. --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Just fixing some things that keep annoying me when I create issues/PRs. ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable by a reason then ~~explicitly strikethrough~~ the whole line. If you don't do that github will show an incorrect process for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - ~~[ ] I have added a description of my changes into [CHANGELOG](https://github.com/cvat-ai/cvat/blob/develop/CHANGELOG.md) file~~ - ~~[ ] I have updated the [documentation]( https://github.com/cvat-ai/cvat/blob/develop/README.md#documentation) accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues ([read github docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/cvat-ai/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/cvat-ai/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/cvat-ai/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/cvat-ai/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 25 January 2023, 10:41:14 UTC |
| 2dc7412 | Kirill Sizov | 24 January 2023, 16:29:14 UTC | Fix webhook signature (#5622) | 24 January 2023, 16:29:14 UTC |
| 41c6728 | Roman Donchenko | 24 January 2023, 06:39:07 UTC | Fix more ESLint errors (#5619) | 24 January 2023, 06:39:07 UTC |
| 54e3198 | Boris Sekachev | 23 January 2023, 14:29:52 UTC | Reduced number of noisy information on ortho views for 3D canvas (#5608) ### Motivation and context <img width="1252" alt="image" src="https://user-images.githubusercontent.com/40690378/213575152-087aa6c8-48a8-483c-bdb9-927c5147a4f3.png"> Related #3438 | 23 January 2023, 14:29:52 UTC |
| 5a9858c | Roman Donchenko | 23 January 2023, 14:21:07 UTC | SDK: Update parameter type annotation in TasksRepo.create_from_data (#5606) | 23 January 2023, 14:21:07 UTC |
| 14bb0b7 | Roman Donchenko | 23 January 2023, 14:14:03 UTC | Fix a CI issue that causes unit tests to run against the wrong version of CVAT (#5612) There seems to be a bug somewhere in the Docker ecosystem (it's probably either Docker Compose, Docker Buildx or BuildKit) that causes `docker compose build` to ignore base images that are already present in the system, and instead fetch them from Docker Hub, if there's a custom Buildx builder configured. There's a bug report here: <https://github.com/docker/compose/issues/9939>. This bug means that when the build pipeline builds the `cvat_ci` image, it's based on the latest release of `cvat/server` from Docker Hub instead of the version that we just built. Consequently, we run the unit tests against that release instead of the development version. Fortunately, we don't actually need to set up a Buildx builder in most jobs (including the `unit_testing` job), so just don't do that. Also, use `cvat/server:local` as the base image in `Dockerfile.ci`. This will prevent a similar bug from reoccurring in the future, since the `local` tag should never be uploaded to Docker Hub. | 23 January 2023, 14:14:03 UTC |
| 6e0b8b6 | Kirill Lakhov | 23 January 2023, 14:12:18 UTC | Added upgrade button (#5610) | 23 January 2023, 14:12:18 UTC |
| a0b70fc | Maxim Zhiltsov | 23 January 2023, 14:07:27 UTC | Change default temporary directory for import and export (#5613) | 23 January 2023, 14:07:27 UTC |
| a9476cb | Padraig X. Lamont | 21 January 2023, 20:02:00 UTC | Fix typing of credentials parameter of make_client in the Python SDK (#5609) ### Motivation and context This is a very simple pull request. The type of the credentials parameter of `make_client` is currently `Optional[Tuple[int, int]]`, but it should be `Optional[Tuple[str, str]]` as used by `Client#login`. This PR makes that change. ### How has this been tested? The typing does not affect the functionality of the code (just the warnings I get in an IDE). | 21 January 2023, 20:02:00 UTC |
| 4e3d81c | Kirill Sizov | 20 January 2023, 12:58:49 UTC | Fix webhooks (#5611) | 20 January 2023, 12:58:49 UTC |
| 58b0553 | Maxim Zhiltsov | 19 January 2023, 12:24:51 UTC | Fix pagination in some endpoints (#5557) - Added missing pagination or page parameters in `/projects/{id}/tasks`, `/tasks/{id}/jobs`, `/jobs/{id}/issues`, `/jobs/{id}/commits`, `/issues/{id}/comments`, `/organizations` - Updated SDK, tests and UI | 19 January 2023, 12:24:51 UTC |
| 330f123 | Roman Donchenko | 19 January 2023, 08:35:38 UTC | Fix some typos (#5601) | 19 January 2023, 08:35:38 UTC |
| 0f0913c | ddx-day | 18 January 2023, 14:34:00 UTC | Django social account sso (#5059) Issue: https://github.com/opencv/cvat/issues/1217 Currently there are a few proposals for SSO authentication to bypass the current user/password login on the UI. By using Django social accounts it is also possible to use SSO on the API, retrieving the security token by passing the code from the OAuth2 workflow. This is an example using Amazon Cognito, but any other social account could also be added. ### Motivation and context Currently CVAT has no functionality to log in with SSO. Other current proposals bypass the current Django framework to add SSO in the UI only, but still use username and password for the API. Using Django social accounts integrates SSO with the API as well, allowing it to be used as an alternative to the username and password, but can also be used together with other SSO frameworks that are UI only. ### How has this been tested? Unit tests for SSO manager in cvat-core and integration test with cvat-sdk for /auth/cognito endpoint. ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable by a reason then ~~explicitly strikethrough~~ the whole line. If you don't do that github will show an incorrect process for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into [CHANGELOG](https://github.com/cvat-ai/cvat/blob/develop/CHANGELOG.md) file - [x] I have updated the [documentation]( https://github.com/cvat-ai/cvat/blob/develop/README.md#documentation) accordingly - [x] I have added tests to cover my changes - [x] I have linked related issues ([read github docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/cvat-ai/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/cvat-ai/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/cvat-ai/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/cvat-ai/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. Co-authored-by: Melanie Day <mday@EYEDIAGNOSIS.local> Co-authored-by: Maria Khrustaleva <maria@cvat.ai> Co-authored-by: Nikita Manovich <nikita@cvat.ai> | 18 January 2023, 14:34:00 UTC |
| 9b55a7f | Boris Sekachev | 18 January 2023, 11:11:55 UTC | Hide dashboard elements if only one canvas view (#5599) <!-- Raised an issue to propose your change (https://github.com/cvat-ai/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [CONTRIBUTION](https://github.com/cvat-ai/cvat/blob/develop/CONTRIBUTING.md) guide. --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable by a reason then ~~explicitly strikethrough~~ the whole line. If you don't do that github will show an incorrect process for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into [CHANGELOG](https://github.com/cvat-ai/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the [documentation]( https://github.com/cvat-ai/cvat/blob/develop/README.md#documentation) accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues ([read github docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/cvat-ai/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/cvat-ai/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/cvat-ai/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/cvat-ai/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 18 January 2023, 11:11:55 UTC |
| a8052fc | vainkop | 18 January 2023, 07:34:31 UTC | Update upgrade_guide.md (#5585) Add How to upgrade CVAT from v2.2.0 to v2.3.0 | 18 January 2023, 07:34:31 UTC |
| 6acf244 | Mariia Acoca | 18 January 2023, 06:25:55 UTC | Documentation for multitask updated (#5590) | 18 January 2023, 06:25:55 UTC |
| dfb6586 | Maria Khrustaleva | 18 January 2023, 06:15:24 UTC | Fix Upload data annotation from CVAT to Azure Blob storage (#5596) Fix issue #5149 | 18 January 2023, 06:15:24 UTC |
| 3fa6f35 | Andrey Zhavoronkov | 17 January 2023, 20:27:39 UTC | Debug health check (#5587) | 17 January 2023, 20:27:39 UTC |
| 8f71d90 | Kazuki Matsuda | 16 January 2023, 18:49:58 UTC | Enable to set callback_url via environment variables (#5533) The callback url is hardcoded, so I cannot run CVAT on Cloud platform. This patch enable to replace these parameters via environment variables. #5526 | 16 January 2023, 18:49:58 UTC |
| fb0b867 | Boris Sekachev | 16 January 2023, 17:54:07 UTC | Grid view and multiple context images supported (#5542) ### Motivation and context <img width="1918" alt="image" src="https://user-images.githubusercontent.com/40690378/210207552-7a7dcb0b-4f0c-4cb6-a030-9522ff68a710.png"> <img width="1920" alt="image" src="https://user-images.githubusercontent.com/40690378/210207577-d05503e8-71d5-4e5c-aecd-03e5a762d7b1.png"> | 16 January 2023, 17:54:07 UTC |
| bc33ba4 | Kirill Lakhov | 16 January 2023, 16:28:05 UTC | Hotfix: Fixed continiously popping error notification on `GET /api/lambda/requests` (#5593) | 16 January 2023, 16:28:05 UTC |
| 31f0578 | Maxim Zhiltsov | 13 January 2023, 16:23:57 UTC | Add a way to create task with custom jobs (#5536) This PR adds an option to specify file to job mapping explicitly during task creation. This option is incompatible with most other job-related parameters like `sorting_method` and `frame_step`. - Added a new task creation parameter (`job_file_mapping`) to set a custom file to job mapping during task creation | 13 January 2023, 16:23:57 UTC |
| b00bc65 | Maria Khrustaleva | 12 January 2023, 17:36:34 UTC | Social account authentication tests (#5444) Depends on #5349 Related #5432 Added tests for social account authentication functionality: cypress test with dummy auth server | 12 January 2023, 17:36:34 UTC |
| 71a0aaf | Kirill Sizov | 12 January 2023, 12:00:24 UTC | Improve error messages when limits reached (#5556) | 12 January 2023, 12:00:24 UTC |
| 81f2b90 | Andrey Zhavoronkov | 12 January 2023, 10:39:48 UTC | Updated installation guide and workflows (#5578) | 12 January 2023, 10:39:48 UTC |
| 4e42530 | Boris Sekachev | 12 January 2023, 07:42:09 UTC | Refactoring: Removed old docs from cvat-core, added more types, fixed import (#5572) <!-- Raised an issue to propose your change (https://github.com/cvat-ai/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [CONTRIBUTION](https://github.com/cvat-ai/cvat/blob/develop/CONTRIBUTING.md) guide. --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable by a reason then ~~explicitly strikethrough~~ the whole line. If you don't do that github will show an incorrect process for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into [CHANGELOG](https://github.com/cvat-ai/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the [documentation]( https://github.com/cvat-ai/cvat/blob/develop/README.md#documentation) accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues ([read github docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/cvat-ai/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/cvat-ai/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/cvat-ai/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/cvat-ai/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 12 January 2023, 07:42:09 UTC |
