| 736881b | Nikita Manovich | 18 October 2023, 12:36:33 UTC | Remove unnecessary COUNT for labels (#6918) Optimized /api/projects, /api/tasks, and /api/jobs requests. Previously for unification, we decided to add a count of labels into every response for each project, task, and job. It leads to performance issues. UI and probably other clients don't use the information because it is useless. Removing it, helps to optimize the SQL request several times. --------- Co-authored-by: Boris Sekachev <boris@cvat.ai> | 18 October 2023, 12:36:33 UTC |
| c9a6083 | Maria Khrustaleva | 18 October 2023, 12:14:56 UTC | Add test for retrieving bucket content when bucket contains manually created dirs (#7018) <!-- 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 - [x] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> ~~- [ ] I have updated the documentation accordingly~~ - [x] 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. | 18 October 2023, 12:14:56 UTC |
| 0f821e4 | Roman Donchenko | 18 October 2023, 11:20:25 UTC | Add a GitHub workflow for finalizing a release (#6998) This automates the second half of the release process (the first being automated by `prepare-release.yml`). After this workflow completes, the only action that should remain for the releaser to do is to merge the `dev-release-*` pull request. We can't do that as part of this workflow, because CI has to finish first, and it seems pointless to create another workflow just to merge 1 PR. Apply some of the aspects of this pipeline to `prepare-release.yml` as well: * Make the release notes extraction process more sophisticated to work around GitHub's frustrating handling of line breaks in PR and release descriptions. * Use GitHub app credentials in order to be able to trigger other pipelines. | 18 October 2023, 11:20:25 UTC |
| 871bd4f | Roman Donchenko | 18 October 2023, 06:27:44 UTC | Add basic checks for changelog fragments to CI (#7007) <!-- 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'll help prevent simple mistakes that would cause scriv to assemble the changelog incorrectly. ### 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. --> Manual testing. ### 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 created a changelog fragment~~ <!-- see top comment in CHANGELOG.md --> - ~~[ ] 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. | 18 October 2023, 06:27:44 UTC |
| 28ea2b4 | James | 18 October 2023, 05:33:50 UTC | Add new community links to the `Links` README section (#7014) This PR adds two links to the CVAT README `Links` section. The first link is a tutorial written by the Roboflow team on how to use CVAT and the second link shows the Roboflow guide to using models for automatic labeling in CVAT. I would love for the Roboflow + CVAT integration to be more accessible to new users; the faster someone can label, the quicker they can get a model into production. | 18 October 2023, 05:33:50 UTC |
| e8db2c3 | Maxim Zhiltsov | 17 October 2023, 09:12:58 UTC | Fix possible double writing of the uploaded client files in Upload-Multiple requests (#6952) Fixes #6878 In the case of big files (>2.5 MB by default), the uploaded files could be write-appended twice, leading to bigger raw file sizes than expected. This PR fixes the behavior by excluding repetitive writes where it was not supposed. - Fixed double append-writing of the uploaded files when Upload-Multiple requests are used - Fixed potential DB - disk inconsistencies in the case of upload errors - Added tests | 17 October 2023, 09:12:58 UTC |
| 021e58c | Jonas Hiltl | 16 October 2023, 14:54:36 UTC | Add support for Cloudflare R2 Buckets (#6701) It is currently not possible to add a Cloudflare R2 Bucket as a Cloud Storage source, since the Secret access key of R2 has a length of 64 but the ui/serializer restricts the length to 44. [This issue](https://github.com/opencv/cvat/issues/5512) addresses the same problem when using STORJ but with a max length of `128`. For me it would make the most sense to completely remove the max length, but this PR currently only fixes the R2 compatibility by increasing the max length to `64`. | 16 October 2023, 14:54:36 UTC |
| b7ea8d1 | Maria Khrustaleva | 16 October 2023, 14:28:45 UTC | [GCS] Skip manually created dirs (#7006) <!-- 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. --> The same problem for GCS as was fixed for AWS S3 https://github.com/opencv/cvat/pull/6997 ### 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 created a changelog fragment <!-- see top comment in CHANGELOG.md --> ~~- [ ] 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. | 16 October 2023, 14:28:45 UTC |
| b02cbe5 | Andrey Zhavoronkov | 16 October 2023, 14:26:29 UTC | Disable zookeeper (#7003) | 16 October 2023, 14:26:29 UTC |
| e6724fa | Nikita Manovich | 16 October 2023, 12:34:56 UTC | Release v2.7.6 | 16 October 2023, 12:34:56 UTC |
| c1802c4 | george-kuanli-peng | 16 October 2023, 10:15:42 UTC | Update lowlevel-api.md (#6989) Fix the method name from `as_dict()` to `to_dict()` in SDK docs | 16 October 2023, 10:15:42 UTC |
| 8b0130f | Kirill Lakhov | 16 October 2023, 09:47:22 UTC | Inviting unregistered users by email (#6901) | 16 October 2023, 09:47:22 UTC |
| fae72e0 | Andrey Zhavoronkov | 16 October 2023, 06:47:26 UTC | prepare to new version | 16 October 2023, 06:47:26 UTC |
| 3c05e84 | Andrey Zhavoronkov | 13 October 2023, 15:35:53 UTC | fixed changelog | 13 October 2023, 15:35:53 UTC |
| 6eead0d | Andrey Zhavoronkov | 13 October 2023, 13:39:25 UTC | Fix CHANGELOG | 13 October 2023, 13:39:25 UTC |
| f616d6a | github-actions[bot] | 13 October 2023, 13:28:31 UTC | Prepare release v2.7.6 | 13 October 2023, 13:28:31 UTC |
| 4d9af86 | Kirill Lakhov | 13 October 2023, 11:53:31 UTC | Removed `Need help` gitter link (#7002) | 13 October 2023, 11:53:31 UTC |
| 80e20ff | Boris Sekachev | 13 October 2023, 10:51:39 UTC | Significant memory optimization when working with masks (#6996) | 13 October 2023, 10:51:39 UTC |
| f938ff3 | Maria Khrustaleva | 13 October 2023, 10:46:08 UTC | Fix getting CS content when S3 bucket contains created manually directories (#6997) <!-- 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 retrieving cloud storage content for an AWS S3 bucket containing manually created "directories" (AWS ListObjectsV2 API returns such objects within the content).  A similar problem can be found [here](https://stackoverflow.com/questions/75620230/aws-s3-listobjectsv2-returns-folder-as-an-object). In this case, I prefer to simply filter keys from keys with a trailing slash, rather than filter from objects with 0 size. ### How has this been 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 - [x] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> ~~- [ ] 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. | 13 October 2023, 10:46:08 UTC |
| 1b77005 | Andrey Zhavoronkov | 12 October 2023, 20:27:30 UTC | Set autorestart=true for all workers (#6945) Helm: set memory request for keydb SUpervisord configs: - Added `autorestart=true` option for all workers - Unified program names to use dashes as delimiter instead of mixed '_' and '-' - Minor improvements to supervisor configurations | 12 October 2023, 20:27:30 UTC |
| 2802442 | Kirill Sizov | 12 October 2023, 19:59:30 UTC | Allow to upload tracks from COCO formats (#6969) This PR resolves the following problems: 1. During import we ignore track_id attribute for annotations if these annotations do not come from one of these formats `('cvat', 'datumaro', 'sly_pointcloud')` this prevents to import tracks in coco format -> this PR extends the list of "track formats" 2. When we convert a dataset from CVAT representation to Datumaro Dataset in all possible situations only the first shape of the skeleton track is a keyframe, all other shapes will be as marked as not keyframes it leads to problems when we try to import such tracks that were exported from CVAT -> this PR adds the following line of code: set `keyframe = True` for skeletons if at least one point of this skeleton is keyframe 3. During import skeleton tracks our code always expects to see a "keyframe" attribute for the skeleton's element, but not all formats support attributes for skeleton points (for example COCO Keypoints doesn't allow to have attributes for each skeleton's point). And if the server doesn't see this attribute for some element we ignore this element -> this PR adds the following logic for skeleton track: if skeleton's elements don't have a keyframe attribute at all then consider such skeleton elements as keyframes = True | 12 October 2023, 19:59:30 UTC |
| 93a4f05 | Andrey Zhavoronkov | 12 October 2023, 19:49:44 UTC | Added X-Frame-Options: deny (#6992) | 12 October 2023, 19:49:44 UTC |
| 848e373 | Andrey Zhavoronkov | 12 October 2023, 19:46:26 UTC | Enabled nginx proxy buffering (#6991) | 12 October 2023, 19:46:26 UTC |
| d85e3a2 | Boris Sekachev | 12 October 2023, 12:08:05 UTC | Disabled translation the page causing the issues (#6993) | 12 October 2023, 12:08:05 UTC |
| 5545e83 | Boris Sekachev | 12 October 2023, 10:17:43 UTC | Fixed crash related to issue tries to mount to not existing parent (#6977) | 12 October 2023, 10:17:43 UTC |
| 41a6296 | Mariia Acoca | 12 October 2023, 09:24:56 UTC | plan name changed to solo documentation (#6985) | 12 October 2023, 09:24:56 UTC |
| 97a079e | Kirill Lakhov | 12 October 2023, 08:28:50 UTC | Added persist image filters test (#6978) | 12 October 2023, 08:28:50 UTC |
| a2d1c5f | Kirill Lakhov | 12 October 2023, 08:27:52 UTC | Fixed object states memory leak (#6984) | 12 October 2023, 08:27:52 UTC |
| 17bef4f | Boris Sekachev | 12 October 2023, 06:14:44 UTC | Updated asset for 3d tests (added nan values to one of them) (#6981) | 12 October 2023, 06:14:44 UTC |
| b450b44 | Kirill Sizov | 11 October 2023, 20:10:55 UTC | Fix tracks splitting for tracks that have sub-tracks (#6968) When uploading annotations for the whole task that has few jobs our server splits tracks. Each track we divide into a few tracks in that way that each track corresponds to only one job and all shapes of the track do not extend beyond the frame range corresponding to that job. It mainly works, but we have a problem with skeleton tracks. Due to this problem we if upload skeleton tracks for the whole task all our tracks will be duplicated for each job but not split, it means that we will have tracks that extend beyond the frame range of jobs and it leads to bad side effects, in this case, our exported annotations from such task could be incorrect or we won't be able to export annotations at all. And the reason for this problem is this small bug, which this PR fixes. Our code really slices sub-tracks for the skeleton track, but after this slicing server doesn't save the result. | 11 October 2023, 20:10:55 UTC |
| cf4329a | Roman Donchenko | 11 October 2023, 13:48:55 UTC | Override EditorConfig settings for YAML files (#6980) I realized that I was fighting my editor, because we indent YAML files with 2 spaces, but `.editorconfig` specifies 4 spaces for all files. Align the config with reality. | 11 October 2023, 13:48:55 UTC |
| 80daa10 | Andrey Zhavoronkov | 11 October 2023, 13:45:53 UTC | Fixed Siammask tracker error on grayscale images (#6982) ```python "Exception caught in handler - \"not enough values to unpack (expected 3, got 2)\": Traceback (most recent call last): File \"/opt/nuclio/_nuclio_wrapper.py\", line 143, in serve_requests await self._handle_event(event) File \"/opt/nuclio/_nuclio_wrapper.py\", line 397, in _handle_event entrypoint_output = self._entrypoint(self._context, event) File \"/opt/nuclio/main.py\", line 29, in handler shape, state = context.user_data.model.infer(image, shape, states[i] if i < len(states) else None) File \"/opt/nuclio/model_handler.py\", line 56, in infer self.config['hp'], device=self.device) File \"/opt/nuclio/SiamMask/tools/test.py\", line 152, in siamese_init z_crop = get_subwindow_tracking(im, target_pos, p.exemplar_size, s_z, avg_chans) File \"/opt/nuclio/SiamMask/tools/test.py\", line 88, in get_subwindow_tracking r, c, k = im.shape ValueError: not enough values to unpack (expected 3, got 2) ``` | 11 October 2023, 13:45:53 UTC |
| 5219c8f | WilliamKyle | 11 October 2023, 11:59:10 UTC | Support rotation in detector results (#6961) | 11 October 2023, 11:59:10 UTC |
| 176bac2 | Boris Sekachev | 11 October 2023, 10:16:44 UTC | Disabled TUS resume upload option (not used, but pollutes local storage) (#6976) | 11 October 2023, 10:16:44 UTC |
| 43181a0 | Roman Donchenko | 11 October 2023, 09:27:43 UTC | Add a GitHub workflow to prepare a release pull request (#6972) This automates the first half of the current release process. The second half will be implemented by another workflow. The reason why it can't all be done in a single workflow is that it's useful to let developers inspect what'll go into the release before actually publishing it, and to apply any last-minute fixes, if necessary. It also allows CI to complete for the release PR. To support the new workflow, add a `--set` option to `update_version.py` that sets the version to a custom value. | 11 October 2023, 09:27:43 UTC |
| ae9cc2e | Nikita Manovich | 10 October 2023, 16:48:02 UTC | [Snyk] Security upgrade opencv-python-headless from 4.5.5.62 to 4.8.1.78 (#6931) Co-authored-by: snyk-bot <snyk-bot@snyk.io> Co-authored-by: Roman Donchenko <roman@cvat.ai> | 10 October 2023, 16:48:02 UTC |
| fceeeeb | Kirill Sizov | 10 October 2023, 12:58:47 UTC | Update README for REST API tests (#6971) | 10 October 2023, 12:58:47 UTC |
| 6ce88d3 | Kirill Lakhov | 10 October 2023, 11:10:13 UTC | Persist image filters across jobs (#6953) <!-- 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 created a changelog fragment <!-- see top comment in CHANGELOG.md --> - [ ] 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. | 10 October 2023, 11:10:13 UTC |
| 3255b09 | Nikita Manovich | 09 October 2023, 14:56:37 UTC | Release v2.7.5 | 09 October 2023, 14:56:37 UTC |
| e0ea6d2 | Andrey Zhavoronkov | 09 October 2023, 12:57:14 UTC | prepare to new version | 09 October 2023, 12:57:14 UTC |
| 20db599 | Andrey Zhavoronkov | 09 October 2023, 12:55:06 UTC | Merge remote-tracking branch 'origin/master' into release-2.7.5 | 09 October 2023, 12:55:06 UTC |
| 24d7c26 | Andrey Zhavoronkov | 09 October 2023, 12:49:59 UTC | Bump version to 2.7.5 | 09 October 2023, 12:55:01 UTC |
| e699848 | Boris Sekachev | 09 October 2023, 12:37:14 UTC | Added temporary workaround to fix corrupted zip file (#6965) | 09 October 2023, 12:37:14 UTC |
| bcf1736 | Kirill Lakhov | 09 October 2023, 09:08:57 UTC | Added test for manifest filetype (#6951) <!-- 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. --> Test for #6890 ### 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. | 09 October 2023, 09:08:57 UTC |
| 4428e14 | Roman Donchenko | 09 October 2023, 07:47:49 UTC | Remove dnspython from dependencies (#6944) | 09 October 2023, 07:47:49 UTC |
| 7462e03 | Mariia Acoca | 07 October 2023, 08:50:37 UTC | Documentation: removed outdated links (#6949) Fix [5972](https://github.com/opencv/cvat/issues/5972) | 07 October 2023, 08:50:37 UTC |
| dbff2b2 | Nikita Manovich | 07 October 2023, 08:06:33 UTC | Release v2.7.4 | 07 October 2023, 08:06:33 UTC |
| 2ec5c44 | Nikita Manovich | 07 October 2023, 08:04:56 UTC | Release v2.7.4 | 07 October 2023, 08:04:56 UTC |
| 701c461 | Andrey Zhavoronkov | 06 October 2023, 14:58:08 UTC | Merge branch 'master' into release-2.7.4 | 06 October 2023, 14:58:08 UTC |
| 7e35aad | Andrey Zhavoronkov | 06 October 2023, 13:49:50 UTC | prepare to new version | 06 October 2023, 13:53:44 UTC |
| 74de11f | Andrey Zhavoronkov | 06 October 2023, 13:47:26 UTC | Bump version to 2.7.4 | 06 October 2023, 13:47:26 UTC |
| 06bae53 | Boris Sekachev | 06 October 2023, 10:04:10 UTC | Fixed nan values in .pcd files, fixed broken navigation in 3D workspace, updated three js (#6862) | 06 October 2023, 10:04:10 UTC |
| 551d28f | Roman Donchenko | 06 October 2023, 09:30:53 UTC | Switch to using scriv for maintaining the changelog (#6942) This is beneficial in multiple ways: * No more `CHANGELOG.md` merge conflicts and mis-merges. * At release time all you need to do to update the changelog is run `scriv collect --version X.Y.Z`. Scriv can also create GitHub releases, although I haven't evaluated this feature yet. Configure scriv so that its output format is the same as what we currently use for our changelog. There are only a few minor differences: * scriv prepends an HTML anchor to every version heading. * scriv puts blank lines between list items (in CommonMark terms, the lists are loose rather than tight). | 06 October 2023, 09:30:53 UTC |
| ae1dc1b | Kirill Sizov | 05 October 2023, 12:42:15 UTC | Sort frames during project dumping (#6927) When we export a task or project in CVAT format [our code uses](https://github.com/opencv/cvat/blob/d497bb6a90dd3c9625c3c8e8f73278019e21983d/cvat/apps/dataset_manager/formats/cvat.py#L717) the `group_by_frame` function. For tasks and for projects behaviour of this function is different since for tasks [we perform sorting frames](https://github.com/opencv/cvat/blob/d497bb6a90dd3c9625c3c8e8f73278019e21983d/cvat/apps/dataset_manager/bindings.py#L420-L421) but for projects [we don't](https://github.com/opencv/cvat/blob/d497bb6a90dd3c9625c3c8e8f73278019e21983d/cvat/apps/dataset_manager/bindings.py#L1152-L1154). As a result, we can have a situation when our annotation file for the project will have a list of images in unsorted form. So this PR adds sorting frames during project export as well. | 05 October 2023, 12:42:15 UTC |
| bfc86ae | Boris Sekachev | 05 October 2023, 08:36:11 UTC | Improved issues comments pipeline (#6937) | 05 October 2023, 08:36:11 UTC |
| 9501bae | dependabot[bot] | 04 October 2023, 14:55:47 UTC | Bump postcss from 8.4.25 to 8.4.31 (#6938) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | 04 October 2023, 14:55:47 UTC |
| 3b15362 | dependabot[bot] | 04 October 2023, 11:55:22 UTC | Bump postcss from 8.3.9 to 8.4.31 in /site (#6939) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | 04 October 2023, 11:55:22 UTC |
| b2b4974 | Nikita Manovich | 04 October 2023, 10:35:45 UTC | [Snyk] Security upgrade urllib3 from 1.26.16 to 1.26.17 (#6936) Co-authored-by: snyk-bot <snyk-bot@snyk.io> | 04 October 2023, 10:35:45 UTC |
| 060d05c | Paweł Kotiuk | 04 October 2023, 09:12:45 UTC | Bump Grafana version (#6912) Bump Grafana version to 10.1.2 | 04 October 2023, 09:12:45 UTC |
| 0be063e | Kirill Lakhov | 04 October 2023, 07:28:35 UTC | Add support for about plugins (#6928) <!-- 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. | 04 October 2023, 07:28:35 UTC |
| bca5f57 | Kirill Lakhov | 03 October 2023, 11:51:51 UTC | Improved Cloud Storage form/create task error message (#6890) <!-- 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. --> Added form validation. CS manifest can be only in `.jsonl` format  Improved error message on task creation form if some incorrect files are selected. Shown their extensions  ### 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 - [ ] 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. | 03 October 2023, 11:51:51 UTC |
| e9d485a | Roman Donchenko | 03 October 2023, 06:44:27 UTC | Remove unused class KeyFramesVideoStreamReader (#6935) As far as I can see, the `only_key_frames` parameter to `VideoManifestManager.link` is not, and has never been, used, and therefore `KeyFramesVideoStreamReader` is unused as well. | 03 October 2023, 06:44:27 UTC |
| 885d26b | Nikita Manovich | 02 October 2023, 17:43:26 UTC | Release v2.7.3 | 02 October 2023, 17:43:26 UTC |
| 73199d6 | Nikita Manovich | 02 October 2023, 17:42:01 UTC | Release v2.7.3 | 02 October 2023, 17:42:01 UTC |
| 797de03 | Andrey Zhavoronkov | 02 October 2023, 14:34:27 UTC | Prepare to new version | 02 October 2023, 14:36:01 UTC |
| df959b5 | Andrey Zhavoronkov | 02 October 2023, 14:31:28 UTC | Merge remote-tracking branch 'origin/master' into release-2.7.3 | 02 October 2023, 14:31:28 UTC |
| cc226e2 | Andrey Zhavoronkov | 02 October 2023, 14:31:10 UTC | Bump version to 2.7.3 | 02 October 2023, 14:31:10 UTC |
| 2dfe6db | Andrey Zhavoronkov | 02 October 2023, 14:22:17 UTC | Fixed error when getting data from CS and cache=True (#6932) Fix ```python AttributeError: 'tuple' object has no attribute 'tobytes' ``` | 02 October 2023, 14:22:17 UTC |
| 92906a7 | Kirill Lakhov | 02 October 2023, 09:33:42 UTC | Try to fix unstable `case_69` (#6926) | 02 October 2023, 09:33:42 UTC |
| 7ce2c37 | Cuong Nguyen Duc | 02 October 2023, 07:37:33 UTC | Update attach-cloud-storage.md (#6762) | 02 October 2023, 07:37:33 UTC |
| b3d362f | Kirill Sizov | 02 October 2023, 07:30:56 UTC | Remove preheader for email confirmation message (#6482) ### Motivation and context Sometimes a see this in my emails:  | 02 October 2023, 07:30:56 UTC |
| d31012e | Roman Donchenko | 02 October 2023, 07:25:52 UTC | Security update cryptography from 41.0.3 to 41.0.4 (#6914) See <https://github.com/advisories/GHSA-v8gr-m533-ghj9>. | 02 October 2023, 07:25:52 UTC |
| 78d45fb | Paweł Kotiuk | 02 October 2023, 07:20:14 UTC | New , form-based Issue templates for Github repository (#6919) I think a proper issue template based on simple form would make creating a proper issues easier for users. These templates can be checked on my fork of this repo: https://github.com/pktiuk/cvat/issues/new/choose  | 02 October 2023, 07:20:14 UTC |
| 4cdd68e | Roman Donchenko | 02 October 2023, 07:11:40 UTC | Avoid relying on PyAV-provided video frame count (#6929) They are not reliable. In particular, MP4 has a feature called "edit lists" that allows you to set a custom playback order for the media data. With edit lists, you could only specify that a particular range of frames should be played, or that a range should be played multiple times, etc. See the following for technical details: https://developer.apple.com/documentation/quicktime-file-format/edit_list_atom FFmpeg follows edit lists when decoding videos. However, the frame count returned by PyAV's `Stream.frames` property is the number of frames in the raw media data and does not reflect the modifications applied by an edit list. When we build a video manifest, we use `Stream.frames` if it's non-zero. Therefore, in the presence of an edit list we will obtain a frame count that does not match the actual number of frames that we can get out of the video. FWIW, edit lists are probably not the only way that `Stream.frames` could be inaccurate, it's just the reason behind a specific problem I encountered. Since we already have to handle the situation where `Stream.frames` is not available, just pretend it doesn't exist and always count frames by traversing the entire video. I don't think it even matters much, since we have to do it anyway to build the rest of the manifest. We also have to stop validating the frame count in a user-provided manifest, which is unfortunate, but it doesn't seem worthwhile to decode the entire video just for that. | 02 October 2023, 07:11:40 UTC |
| d497bb6 | Roman Donchenko | 29 September 2023, 07:03:49 UTC | Remove the Git repository synchronization functionality (#6904) This functionality has accumulated significant technical debt: * Most importantly, it does not use the current authorization system, rendering it accessible only for admin users. * It doesn't follow the regular API conventions and is not visible in the API schema. This necessitates a special code in the SDK. * The initialization code in `base.py` is not safe when multiple instances of the server starts at the same time (each instance may end up generating its own key). The team has decided that the cost of fixing these issues outweighs the benefit of the functionality, so remove it. | 29 September 2023, 07:03:49 UTC |
| 4a487c3 | Nikita Manovich | 27 September 2023, 12:51:29 UTC | [Snyk] Security upgrade pillow from 9.3.0 to 10.0.1 (#6907) Co-authored-by: snyk-bot <snyk-bot@snyk.io> Co-authored-by: Roman Donchenko <roman@cvat.ai> | 27 September 2023, 12:51:29 UTC |
| 2451f63 | Anna Petrovicheva | 27 September 2023, 12:25:48 UTC | [Snyk] Security upgrade pillow from 9.5.0 to 10.0.1 (#6909) Co-authored-by: snyk-bot <snyk-bot@snyk.io> Co-authored-by: Roman Donchenko <roman@cvat.ai> | 27 September 2023, 12:25:48 UTC |
| f47f1a3 | Nikita Manovich | 27 September 2023, 10:44:25 UTC | [Snyk] Security upgrade pillow from 9.4.0 to 10.0.1 (#6908) Co-authored-by: snyk-bot <snyk-bot@snyk.io> | 27 September 2023, 10:44:25 UTC |
| d68b359 | Roman Donchenko | 26 September 2023, 09:26:10 UTC | Merge pull request #6897 from opencv/az/dev-release-2.7.2 Dev release 2.7.2 | 26 September 2023, 09:26:10 UTC |
| 4c29752 | Roman Donchenko | 26 September 2023, 09:23:22 UTC | Merge pull request #6896 from opencv/release-2.7.2 Release v2.7.2 | 26 September 2023, 09:23:22 UTC |
| 8b72768 | Andrey Zhavoronkov | 25 September 2023, 11:21:36 UTC | Prepare for 2.8.0 | 25 September 2023, 11:21:36 UTC |
| 2bd22b8 | Andrey Zhavoronkov | 25 September 2023, 11:17:33 UTC | Merge remote-tracking branch 'origin/master' into release-2.7.2 | 25 September 2023, 11:17:33 UTC |
| 58f34e6 | Andrey Zhavoronkov | 25 September 2023, 11:14:37 UTC | Bump version to 2.7.2 | 25 September 2023, 11:14:37 UTC |
| ee1d421 | Andrey Zhavoronkov | 22 September 2023, 13:33:32 UTC | Improved chunk generation from cloud storages (#6881) | 22 September 2023, 13:33:32 UTC |
| adc8895 | Maria Khrustaleva | 22 September 2023, 13:15:59 UTC | Fix leaving the organization (#6422) Users should have the option to leave the organization. | 22 September 2023, 13:15:59 UTC |
| 3220147 | Mariia Acoca | 22 September 2023, 12:17:21 UTC | Gamma Correction and workspace documentation updated (#6873) | 22 September 2023, 12:17:21 UTC |
| 612f0e7 | Mariia Acoca | 22 September 2023, 12:10:22 UTC | Data export documentation update (#6795) | 22 September 2023, 12:10:22 UTC |
| 26693dd | Andrey Zhavoronkov | 21 September 2023, 15:40:41 UTC | Do not copy extra files if both server_files and job_file_mapping are… (#6879) | 21 September 2023, 15:40:41 UTC |
| 657e361 | Boris Sekachev | 15 September 2023, 13:56:21 UTC | [Refactoring] Removed custom exif rotation method (#6835) | 15 September 2023, 13:56:21 UTC |
| b2957ab | Boris Sekachev | 15 September 2023, 13:55:27 UTC | Do not reload the page when changing job state (#6851) | 15 September 2023, 13:55:27 UTC |
| 7297244 | Nikita Manovich | 15 September 2023, 13:52:21 UTC | Release v2.7.1 | 15 September 2023, 13:52:21 UTC |
| 10e71d6 | Nikita Manovich | 15 September 2023, 13:51:23 UTC | Release v2.7.1 | 15 September 2023, 13:51:23 UTC |
| 271daf6 | Andrey Zhavoronkov | 15 September 2023, 12:07:11 UTC | Prepare for 2.8.0 | 15 September 2023, 12:07:11 UTC |
| 68bfdc5 | Andrey Zhavoronkov | 15 September 2023, 12:04:48 UTC | Merge remote-tracking branch 'origin/master' into release-2.7.1 | 15 September 2023, 12:04:48 UTC |
| 70fd466 | Andrey Zhavoronkov | 15 September 2023, 12:04:27 UTC | Bump version to 2.7.1 | 15 September 2023, 12:04:27 UTC |
| 97c7f1d | Maria Khrustaleva | 15 September 2023, 10:26:36 UTC | Fix issues 6836 6837 (#6850) Resolve https://github.com/opencv/cvat/issues/6837 Resolve https://github.com/opencv/cvat/issues/6836 | 15 September 2023, 10:26:36 UTC |
| 76844a6 | Boris Sekachev | 15 September 2023, 09:40:56 UTC | Added plugin option: preventMethodCallWithReturn (#6858) <!-- 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 September 2023, 09:40:56 UTC |
| e2ffbd4 | Kirill Sizov | 14 September 2023, 15:27:56 UTC | Upgrade Datumaro to fix problem with EXIF rotated images during dataset importing in YOLO format (#6860) | 14 September 2023, 15:27:56 UTC |
| b30a5a1 | Boris Sekachev | 13 September 2023, 08:13:11 UTC | Added test to check rotated tif image (#6842) <!-- 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 - [x] 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: kirill-sizov <sizow.k.d@gmail.com> | 13 September 2023, 08:13:11 UTC |
| 8054543 | Boris Sekachev | 13 September 2023, 07:01:14 UTC | Extended error logging (#6844) <!-- 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 Not all the errors, occured on client are logged now. Only uncaught exceptions. The core idea of this PR is to log all the error message, shown to a user (except of server-related errors 400, 500, 403, 0 and others) ### 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. | 13 September 2023, 07:01:14 UTC |
