| 6d2e909 | Roman Donchenko | 28 March 2024, 15:51:09 UTC | Split off documentation building into its own pipeline (#7692) It has occurred to me that the documentation build happens inside the main workflow, which is configured to ignore changes to the docs when determining whether to run. So if a PR only changes the docs... we don't build the docs. That makes no sense. Fix this by extracting the documentation job into its own workflow, that always runs. The downside of this is that we have to duplicate the work of generating the SDK, but IMO, it's an acceptable sacrifice. A side effect of this is that a failure to build the docs no longer prevents the publishing of Docker images, but I don't think that was needed in the first place. | 28 March 2024, 15:51:09 UTC |
| 6eb7b7d | Maxim Zhiltsov | 28 March 2024, 12:11:52 UTC | Bump server deps (#7694) <!-- 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. --> Launched the command from the server requirements [readme](https://github.com/opencv/cvat/blob/6273b48ae66de565f740b2f839266dc5aeeaffcb/cvat/requirements/README.txt). Helps to clean other PRs from irrelevant changes. ### 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. | 28 March 2024, 12:11:52 UTC |
| f855531 | Roman Donchenko | 28 March 2024, 11:35:32 UTC | Use relative path in layouts/home.html (#7693) It seems much simpler than the current approach, and it avoids hardcoding the `/cvat` prefix. | 28 March 2024, 11:35:32 UTC |
| dcbff88 | Yanghe Sun | 28 March 2024, 11:32:08 UTC | [GSoC2024] fix skeleton tracks slice between jobs (#7615) Fixes #7498 In #6968, sub tracks splitting has been fixed but not entirely, if the user wants to import tracks between more than 2 jobs it can cause malformed annotation like #7498. In the pervious test case, https://github.com/opencv/cvat/blob/d1a300f0189744bef01d2c60135ec474c5004fbc/tests/python/rest_api/test_tasks.py#L543-L563 skeleton track is static so it did not identify any issues. <!-- 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 Pervious interpolate method will drop the last frame. That's correct for most cases, but if slices and tracks are like this: slice: -------------xxxxx--------- track: ---------xxxxxxxxxx------- We have to keep the last frame of slice in the track. If not, this track won't close. ### How has this been tested? I rewrited the testcase `test_can_split_skeleton_tracks_on_jobs` Now it test the split function with a longer input track and stricter interpolate reference. ### 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 - [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. --------- Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> | 28 March 2024, 11:32:08 UTC |
| 6273b48 | zaha | 28 March 2024, 10:32:50 UTC | Merge pull request #7673 from umangapatel123/import_annotation_filename_test [GSoC2024] add test case for subsequent annotation import | 28 March 2024, 10:32:50 UTC |
| 522d48c | Umang Patel | 27 March 2024, 18:14:48 UTC | Merge branch 'opencv:develop' into import_annotation_filename_test | 27 March 2024, 18:14:48 UTC |
| d0e1143 | zaha | 27 March 2024, 15:11:21 UTC | Add test to check "Remove underlying pixels" tool (#7684) | 27 March 2024, 15:11:21 UTC |
| 26750a9 | Taha | 27 March 2024, 10:44:16 UTC | [GSoC2024] fix warped image loading (#7583) | 27 March 2024, 10:44:16 UTC |
| f5dae55 | Kirill Lakhov | 27 March 2024, 10:43:00 UTC | Fixed duplicated notifications for automatic annotation (#7595) | 27 March 2024, 10:43:00 UTC |
| 2433667 | Umang Patel | 26 March 2024, 18:30:14 UTC | Merge branch 'opencv:develop' into import_annotation_filename_test | 26 March 2024, 18:30:14 UTC |
| aec333d | Roman Donchenko | 26 March 2024, 16:07:55 UTC | Fix two problems with the task segmentation algorithm (#7681) 1. When a task has non-zero overlap and exactly as many frames as needed to create 1 or more complete segments, the current algorithm generates a redundant segment at the end. For example, if size is 5, segment size is 3, and overlap is 1, it generates segments (0, 2), (2, 4), and (4, 4). The algorithm attempts to compensate for this, but it only works in the case where the segment size is unspecified (and defaults to the total size). Update the algorithm to handle this correctly in the general case. 2. The algorithm selects a default overlap size of 5 if the media file is a video. However, this might not be a valid value if the task has a very small segment size. In this case, a range of undesirable behaviors may occur, depending on the segment size: * segments getting generated such that more than 2 segments cover a single frame; * task creation crashing with an exception; * a task being created with no segments at all. Fix this by clamping the default overlap size the same way as a user-specified one. Fixes #7675. | 26 March 2024, 16:07:55 UTC |
| 811f6ed | Mariia Acoca | 26 March 2024, 14:08:32 UTC | Single Shape Annotation Mode documentation (#7674) | 26 March 2024, 14:08:32 UTC |
| 2045f80 | Maxim Zhiltsov | 26 March 2024, 11:47:55 UTC | Fix invalid changelog entry (#7682) Fixes opencv/cvat#7678 as it breaks the CI. | 26 March 2024, 11:47:55 UTC |
| e0732a3 | Vidit Agarwal | 26 March 2024, 10:36:16 UTC | [GSoC2024] added entry to changelog.md for PR fixing accumulation of confusion matrix across jobs (#7678) Added entry to `changelog.md` for PR fixing accumulation of confusion matrix across jobs. As mentioned in https://github.com/opencv/cvat/pull/7604 this is a PR where the necessary changelog entry has been added. ### 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. | 26 March 2024, 10:36:16 UTC |
| b1572fc | Mohab Yaser | 26 March 2024, 09:56:50 UTC | Fixing typo in "repo-structure" in docs (#7616) | 26 March 2024, 09:56:50 UTC |
| 087a7ea | Kirill Lakhov | 26 March 2024, 07:49:21 UTC | Fixed remove underlying pixels feature (#7637) | 26 March 2024, 07:49:21 UTC |
| 7533496 | Abhinav Sharma | 26 March 2024, 07:30:47 UTC | [GSoC2024] Update helm documentation for creating superuser (#7631) <!-- 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. --> **Issue: ** #7605 Currently, the command used in the official documentation is not working, and giving error: 1. **Command Used**: ```shell BACKEND_POD_NAME=$(kubectl get pod --namespace $HELM_RELEASE_NAMESPACE -l tier=backend,app.kubernetes.io/instance=$HELM_RELEASE_NAME -o jsonpath='{.items[0].metadata.name}') &&\ kubectl exec -it --namespace $HELM_RELEASE_NAMESPACE $BACKEND_POD_NAME -c cvat-backend-app-container -- python manage.py createsuperuser ``` 2. **Actual Output**:  3. **Expected Output**:  ### 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. --> I have run a minikube cluster, and run the as it is command in cluster, which gives error: ```shell error: cannot exec into a container in a completed pod; current phase is Succeeded ``` ### 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 --> - [x] I have updated the documentation accordingly - [x] 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. Co-authored-by: abhinav.sharma <abhinav.sharma@zeeve.io> | 26 March 2024, 07:30:47 UTC |
| 7c53faa | Umang Patel | 26 March 2024, 04:25:06 UTC | Merge branch 'opencv:develop' into import_annotation_filename_test | 26 March 2024, 04:25:06 UTC |
| f27d268 | Umang Patel | 25 March 2024, 18:34:32 UTC | refactored the test case used `exportTask` from `commands.js` and made a common function for Import Annotation | 25 March 2024, 18:34:32 UTC |
| aab1576 | zaha | 25 March 2024, 15:54:13 UTC | Add notes to Mac users to installation doc (#7662) | 25 March 2024, 15:54:13 UTC |
| 7a07603 | Vidit Agarwal | 25 March 2024, 14:48:24 UTC | [GSoC2024] added accumulation of confusion matrix across various jobs (#7604) Added accumulation of confusion matrix across various jobs under the same task. ### Motivation and context Fixes https://github.com/opencv/cvat/issues/7424 ### How has this been tested? On the backup task containing 10 jobs [task_task.with.10.jobs_backup_2024_03_11_15_48_27.zip](https://github.com/opencv/cvat/files/14561155/task_task.with.10.jobs_backup_2024_03_11_15_48_27.zip) as mentioned in this [issue comment](https://github.com/opencv/cvat/issues/7424#issuecomment-1988787512) ### Checklist - [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~ - [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)) ~- [ ] 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: Maxim Zhiltsov <zhiltsov.max35@gmail.com> | 25 March 2024, 14:48:24 UTC |
| eb5b612 | Maria Khrustaleva | 25 March 2024, 11:07:54 UTC | Move logic for downloading resources from CS into main background process (#7551) <!-- 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. --> Looks like using dependent jobs for downloading resources from cloud storage gives more problems than benefits. With such architecture, it is possible to stop the import queue forever. E.g. RQ_1 process for downloading file from CS fails -> dependent RQ_2 process for importing file will not be started ([1](https://github.dev/rq/rq/blob/3ad86083c33ec28b81a07f94dafdcf1cd56429ea/rq/worker.py#L1562), [2](https://github.dev/rq/rq/blob/3ad86083c33ec28b81a07f94dafdcf1cd56429ea/rq/worker.py#L691-L692)) (it means that this process will be kept in the deferred registry forever since there is no code that cleans the deferred registry + for some reason such jobs are not moved to the failed registry after dependencies fail) -> next request for importing something creates new RQ job dependent from RQ_2. This PR fixes the described issue. ### 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. --> 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 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. --------- Co-authored-by: Andrey Zhavoronkov <andrey@cvat.ai> | 25 March 2024, 11:07:54 UTC |
| bd2f1c7 | Umang Patel | 24 March 2024, 19:46:28 UTC | add test case for subsequent annotation import test case for the pr #7599 | 24 March 2024, 19:46:28 UTC |
| 33f9cc2 | zaha | 24 March 2024, 09:11:50 UTC | Add test for check disabling button while creating gt job (#7649) <!-- 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 feature https://github.com/opencv/cvat/pull/7540 ### 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 - [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. | 24 March 2024, 09:11:50 UTC |
| 8729f45 | Roman Donchenko | 22 March 2024, 13:46:09 UTC | Remove the per-task `artifacts` directory (#7597) This was only used by the Git synchronization functionality, which was removed in #6904. | 22 March 2024, 13:46:09 UTC |
| 173b970 | Mariia Acoca | 22 March 2024, 13:43:17 UTC | Readme Gif & Button forwarding to app (#7405) | 22 March 2024, 13:43:17 UTC |
| 0af1815 | Mann Dharmesh Acharya | 22 March 2024, 13:04:25 UTC | [GSoC2024] Added Validations, testcases to Labels Constructor (#7627) <!-- 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/). --> 1. Added new Label Validation to handle empty label name given to constructor. 2. Fixed existing validation for Duplicate label name to make it more clear. 3. Added tests for both. <!-- 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. --> #### Background - Mentioned as an`ui-ux` `enhancement` issue in #5729, Two problems were raised: 1. Hint when user tries to add existing label in project is incorrect as the same code validation is triggered in both project and task. 2. When user enters an empty label name, It is not intuitively clear that the state of the constructor is reset and skeleton is not added. #### Fix 1. Tests were written for the desired outcome. 2. Fixed the Unique Label Validation by changing the display message to a generalized one. <img width="1511" alt="Screenshot 2024-03-18 at 1 20 47 AM" src="https://github.com/opencv/cvat/assets/89384052/4d29dee0-2859-4219-bdd4-70eb6f42b36d"> <img width="1511" alt="Screenshot 2024-03-18 at 1 21 03 AM" src="https://github.com/opencv/cvat/assets/89384052/6dcdee8c-015d-4558-be77-9db52ae09906"> 4. Added a new Empty Label Validation which stops the form from submitting when label name is empty and displays an error message. <img width="1511" alt="Screenshot 2024-03-18 at 1 21 20 AM" src="https://github.com/opencv/cvat/assets/89384052/9848dde8-f178-412b-ac6c-24ad42c95576"> ### How has this been tested? - The issue was first triggered locally. - Test cases were written using Cypress, Here are the screenshots of the same. <img width="1511" alt="Screenshot 2024-03-18 at 1 22 29 AM" src="https://github.com/opencv/cvat/assets/89384052/2fdc7c5a-e200-461d-b3cb-6cb2a5f8216c"> <img width="1511" alt="Screenshot 2024-03-18 at 1 23 51 AM" src="https://github.com/opencv/cvat/assets/89384052/1eb9c6d1-81f6-4a5e-88b5-62acdf654b41"> <!-- 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 - [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. --------- Co-authored-by: Kirill Lakhov <kirill.9992@gmail.com> | 22 March 2024, 13:04:25 UTC |
| ef67a50 | Andrey Zhavoronkov | 22 March 2024, 08:41:26 UTC | Update installation guide (#7601) <!-- 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 - [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: Mariia Acoca <39969264+mdacoca@users.noreply.github.com> | 22 March 2024, 08:41:26 UTC |
| 7e2f9d3 | Roman Donchenko | 21 March 2024, 18:11:00 UTC | Fix annotation accuracy display in the UI (#7652) <!-- 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 current formula the UI uses to calculate accuracy is incorrect. The denominator is supposed to be the total sample count, but ds_count + gt_count - valid_count is not the same value. To illustrate: **** ***. *... **** **** ***. .*.. **** **** ***. ..*. **** .... ***. .... ***. ds_count gt_count valid_count total_count (expected) Each value is the sum of the values in the confusion matrix marked by `*`. The current formula essentially adds values that are off the diagonal twice. Instead of trying to derive the total count from other values, just transmit the correct value from the server and use it in the UI. ### 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 - [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. | 21 March 2024, 18:11:00 UTC |
| fc54c47 | Roman Donchenko | 21 March 2024, 15:06:00 UTC | quality_control: correct the per-class accuracy formula (#7640) <!-- 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 current formula used to calculate `ConfusionMatrix.accuracy` is, in fact, not accuracy, but the Jaccard index. Replace it with the correct formula. Since the Jaccard index is a useful metric in its own right, calculate it too, but save it in another attribute of `ConfusionMatrix`. ### 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 - [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. --------- Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> | 21 March 2024, 15:06:00 UTC |
| 1749002 | Roman Donchenko | 21 March 2024, 12:54:05 UTC | Redump the test data (#7650) There've been a couple of patches that introduced minor changes to object representations. Recreate the test dump so that these changes don't pollute the diff in future pull requests. | 21 March 2024, 12:54:05 UTC |
| 68ba436 | Syed Bariman Jan | 21 March 2024, 12:29:56 UTC | Update python debugger configuration (#7634) ### Motivation and context The old python debugger configuration will soon be deprecated so I changed it to use debugpy which is the new configuration. ### 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 --> ### 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: syedbarimanjan <syedbarimnajan@gmail.com> Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> | 21 March 2024, 12:29:56 UTC |
| dd64046 | Vidit Agarwal | 21 March 2024, 10:58:17 UTC | [GSoC2024] added filter to not include gt_job when the test intends to create one. (#7623) <!-- 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/). --> Fixes #7622 Added a check to ensure that tests which need to create a gt_job aren't picking up tasks which already have a gt_job ### How has this been tested? I added a new task to the testing database and ran these updated tests. ### 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~ - [x] 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)) ~- [ ] 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: Maxim Zhiltsov <zhiltsov.max35@gmail.com> | 21 March 2024, 10:58:17 UTC |
| d1a300f | Kavikumar M | 20 March 2024, 08:35:07 UTC | [GSoC24] Resolved Issue #7620 (Changed the alignment of the empty component in job page) (#7621) ref issue: https://github.com/opencv/cvat/issues/7620 I've created a class called `cvat-empty-jobs-list` and added it to a div to make the empty component in the job page aligned in the middle as all other pages having empty component aligned to its center.  | 20 March 2024, 08:35:07 UTC |
| 53bf350 | Roman Donchenko | 19 March 2024, 13:18:35 UTC | quality_control: factor out duplicate annotation summary creation logic (#7632) In addition, remove code creating an unused annotation summary object from `generate_report`. <!-- 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. --> 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. | 19 March 2024, 13:18:35 UTC |
| acb68a5 | Roman Donchenko | 15 March 2024, 18:37:06 UTC | quality_control: refactor confusion matrix initialization (#7619) <!-- 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 existing code creates a row and column for each category in the dataset, plus an extra row/column at the end for unmatched annotations. However, it's not immediately clear what order these rows/columns are in, because all access is done indirectly through the `confusion_matrix_labels_rmap` dictionary. IMO, this is an unnecessary level of indirection, which obscures the structure of the matrix. It's easier to just assign rows/columns 0..(N-1) to the categories and N to "unmatched". Do just that. Additionally, factor out the code creating the matrix into a function, because it's used in two places. ### 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. | 15 March 2024, 18:37:06 UTC |
| f513aa1 | dependabot[bot] | 15 March 2024, 08:19:00 UTC | Bump follow-redirects from 1.15.4 to 1.15.6 (#7612) | 15 March 2024, 08:19:00 UTC |
| e431d28 | Maria Khrustaleva | 15 March 2024, 08:05:55 UTC | Fixed scope defining when checking status of project import (#7555) | 15 March 2024, 08:05:55 UTC |
| 787a0c8 | Umang Patel | 15 March 2024, 07:55:20 UTC | [GSoC2024] fix and refactor import-dataset-modal code (#7428) (#7599) Refactor code to use useReducer instead of useState. Fixes #7428 'file' and 'fileName' in the uploadParams were not set to null after import. To avoid this change the code to set 'file' and 'fileName' to null after importing is done. <!-- 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 change is required to make the code clear. The previous code uses many `useState` to manage the state but this version uses `useReducer` to manage all the states. In the previous code `file` and `fileName` in the `uploadParams` were not set to null after importing was done but this version set it to null so it can not use the previous file while importing annotation. it solves issue #7428 ### 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. --> The changes have been tested manually. The code was tested using different sequences of annotation uploads. The state of each parameter is tested by logging its state to the console. ### 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~~ - [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)) - ~~[ ] 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> | 15 March 2024, 07:55:20 UTC |
| 9e605f4 | Boris Sekachev | 15 March 2024, 06:55:34 UTC | Fixed using single shape annotation mode with multiple labels (#7606) | 15 March 2024, 06:55:34 UTC |
| 1f661bc | Boris Sekachev | 15 March 2024, 06:55:23 UTC | Added overflow scroll in attribute annotation editor (#7610) | 15 March 2024, 06:55:23 UTC |
| f22322f | Syed Bariman Jan | 14 March 2024, 13:16:43 UTC | [GSoC2024] Add tooltip to long project card name (#7550) | 14 March 2024, 13:16:43 UTC |
| ae7999b | Vidit Agarwal | 12 March 2024, 10:27:17 UTC | [GSoC2024] fixed path of gen folder which is incorrect in cvat-sdk docs (#7586) Fixes #7585 Fixed the path to `gen` folder which is incorrect in cvat-sdk docs. | 12 March 2024, 10:27:17 UTC |
| 9f0439a | Boris Sekachev | 12 March 2024, 08:38:55 UTC | Merge pull request #7594 from opencv/dev-release-2.11.2 Update develop after v2.11.2 | 12 March 2024, 08:38:55 UTC |
| 6aa6df0 | cvat-bot[bot] | 12 March 2024, 07:46:46 UTC | Update develop after v2.11.2 | 12 March 2024, 07:46:46 UTC |
| 68f13a0 | cvat-bot[bot] | 11 March 2024, 19:25:03 UTC | Prepare release v2.11.2 | 11 March 2024, 19:25:03 UTC |
| 009f9f8 | Roman Donchenko | 11 March 2024, 17:38:00 UTC | Make analytics report update job scheduling more efficient (#7576) Currently, `schedule_analytics_report_autoupdate_job` attempts to debounce job scheduling by examining existing jobs before scheduling a new one. Unfortunately, the `scheduler.get_jobs` function, which it uses for this purpose, scales poorly. Not only does it fetch IDs of all scheduled jobs (and not just ones related to the current object), but it then fetches information about every job, one by one. The current logic doesn't even need this information, but RQ Scheduler provides no method to get just the IDs. Replace the current logic with a new lightweight approach that uses a custom Redis key to block scheduling of additional jobs. | 11 March 2024, 17:38:00 UTC |
| cd5cd44 | Mariia Acoca | 11 March 2024, 11:23:20 UTC | open spec auto (#7587) | 11 March 2024, 11:23:20 UTC |
| 58b6bad | Vidit Agarwal | 11 March 2024, 11:02:02 UTC | [GSoC2024] added better error message when video resolution too large (#7549) On uploading video files exceeding the maximum resolution supported by OpenH264, it raises error while trying to decode the video. To handle this more gracefully I have added dimension check based on which it raises an error beforehand with appropriate message. Fixes #7425 --------- Co-authored-by: Maria Khrustaleva <maria@cvat.ai> | 11 March 2024, 11:02:02 UTC |
| c8376b7 | Roman Donchenko | 11 March 2024, 10:46:14 UTC | Speed up resource updates when there are no matching webhooks (#7553) The signal handling code in `cvat.apps.webhooks.signals` always fetches the old version of the resource from the database and serializes it. But if no webhook is defined for the current resource, this work is pointless. Select the webhooks first, and only then (if necessary) serialize the old resource. Also, move the diffing of the old and new versions to the `post_save` signal handler, to avoid serializing the new version a second time. This leads to a considerable speedup for resources with complicated serializers, such as tasks and jobs, when no webhooks are attached. In my experiments, saving of annotations was sped up by 20-25% with this patch. This patch also makes the signal handlers more hygienic with the use of temporary attributes. Both the attributes it uses are now prefixed with `_webhooks` to avoid collisions, and removed after they are used. | 11 March 2024, 10:46:14 UTC |
| 7a1fc3f | Roman Donchenko | 11 March 2024, 09:47:41 UTC | Fix password handling for in-mem Redis (#7577) The `PASSWORD` setting is not a URL, so it should not be URL-encoded. | 11 March 2024, 09:47:41 UTC |
| 95e6f26 | Kirill Lakhov | 11 March 2024, 09:32:35 UTC | Load decoder.onnx only when necessary (#7564) | 11 March 2024, 09:32:35 UTC |
| b7470e1 | Roman Donchenko | 10 March 2024, 17:03:32 UTC | Remove documentation on Toloka integration (#7578) | 10 March 2024, 17:03:32 UTC |
| bfb902f | Roman Donchenko | 08 March 2024, 15:19:02 UTC | Remove the migration health check (#7573) | 08 March 2024, 15:19:02 UTC |
| a7a69eb | Boris Sekachev | 08 March 2024, 15:18:08 UTC | Updated documentation image (#7575) | 08 March 2024, 15:18:08 UTC |
| 2fe5490 | Kirill Lakhov | 08 March 2024, 11:05:48 UTC | Fix job meta requests (#7560) | 08 March 2024, 11:05:48 UTC |
| 6cac453 | Roman Donchenko | 08 March 2024, 10:24:14 UTC | Optimize `update:*` event logging when only `updated_date` is changed (#7559) Diffing the old and new state of the object is fairly costly, so it helps to avoid doing that when it isn't necessary. | 08 March 2024, 10:24:14 UTC |
| b5014d1 | Roman Donchenko | 08 March 2024, 10:04:38 UTC | Remove double `updated_date` bumping when saving annotations (#7556) <!-- 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. --> Currently, `JobAnnotation.update` needlessly bumps the `updated_date` of the job and the task twice (both via `_delete` and `_create`). These updates are costly in terms of time due to the various side effects associated with them (such as webhook sending and event logging), so it's better to avoid doing them gratuitously. Change the code so that the bumps only happen once. I simplified the code a bit; previously, the code in `_delete` would only bump the date if something was actually deleted (i.e., the annotations passed in actually existed in the database). Now we just check if there were any annotations we _wanted_ to delete. This means that if a request only deletes non-existent annotations, the date will still get bumped. I don't think it's a significant issue, since this is a pathological case. ### 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 - [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. | 08 March 2024, 10:04:38 UTC |
| bf4089e | Roman Donchenko | 06 March 2024, 13:44:16 UTC | Expose Vector and Clickhouse ports in `docker-compose.dev.yml` (#7552) | 06 March 2024, 13:44:16 UTC |
| 5b9ab8e | Boris Sekachev | 06 March 2024, 09:20:43 UTC | Merge pull request #7558 from opencv/dev-release-2.11.1 Update develop after v2.11.1 | 06 March 2024, 09:20:43 UTC |
| e00c902 | cvat-bot[bot] | 05 March 2024, 19:28:55 UTC | Update develop after v2.11.1 | 05 March 2024, 19:28:55 UTC |
| 925ae6a | cvat-bot[bot] | 05 March 2024, 13:16:16 UTC | Prepare release v2.11.1 | 05 March 2024, 13:16:16 UTC |
| f52f0f3 | Kirill Lakhov | 05 March 2024, 10:18:17 UTC | Added test for single shape annotation mode (#7548) | 05 March 2024, 10:18:17 UTC |
| a9333db | Akshay Dilip Kumar | 01 March 2024, 10:21:39 UTC | Updated Python version in development-environment.md to 3.10 🐍 (#7538) | 01 March 2024, 10:21:39 UTC |
| 5d644d6 | Boris Sekachev | 01 March 2024, 06:48:05 UTC | Disable submit button while creating GT job (#7540) | 01 March 2024, 06:48:05 UTC |
| 14b592f | Mariia Acoca | 29 February 2024, 13:22:59 UTC | added videos to documentation (#7534) | 29 February 2024, 13:22:59 UTC |
| 9952456 | Vidit Agarwal | 29 February 2024, 06:36:00 UTC | Fixed the docs link in ISSUE_TEMPLATE (#7532) | 29 February 2024, 06:36:00 UTC |
| 35a934b | Anna Petrovicheva | 28 February 2024, 14:23:33 UTC | [Snyk] Security upgrade cryptography from 42.0.2 to 42.0.4 (#7516) | 28 February 2024, 14:23:33 UTC |
| 6e496a4 | Jiacong Fang | 28 February 2024, 12:17:01 UTC | Remove project id in the comment of `tasks.rego` (#7528) | 28 February 2024, 12:17:01 UTC |
| ab539d2 | Jiacong Fang | 28 February 2024, 12:16:27 UTC | Fix docker registry mirror list (#7529) | 28 February 2024, 12:16:27 UTC |
| ae9f474 | Roman Donchenko | 27 February 2024, 17:48:42 UTC | Fix several problems with the calculation of working time per client event (#7511) The first problem is that in the following case, the algorithm would accrue more working time than was actually spent: A |-----------| ---------+------------+------> time B C A, B and C are events. Let's say that Te(A) is the timestamp of the end of A, while T(B) and T(C) are the timestamps of B and C, respectively. The current code in `ClientEventsSerializer.to_internal_value` adjusts `last_timestamp` after processing every event. After A is processed, `last_timestamp` is set to Te(A). After B is processed, `last_timestamp` goes _backwards_ to T(B). So when the algorithm calculates the working time for C, it gets T(C) - T(B), when the correct answer is T(C) - Te(A). The span from T(B) to Te(A) gets counted twice. Fix this by rewriting the algorithm, so that `last_timestamp` (now renamed `previous_end_timestamp`) can only go forwards. ----- The second problem is that the algorithm is unable to calculate the working time for the first event in each batch that the client sends. This is because to calculate working time for an event, you need the timestamp/duration of the previous event, and this information is unavailable for the first event in the batch. Fix this by resending the most recently sent event along with each batch, and using it to initialize the algorithm. | 27 February 2024, 17:48:42 UTC |
| 5f20678 | Boris Sekachev | 27 February 2024, 06:52:04 UTC | Single object annotation mode (#7486) | 27 February 2024, 06:52:04 UTC |
| 7f92660 | 2h-kim | 25 February 2024, 09:32:50 UTC | Fix bug: Fixed a problem that was overwritten and not inputted when entering Korean (#7380) | 25 February 2024, 09:32:50 UTC |
| 5370363 | Boris Sekachev | 23 February 2024, 14:04:03 UTC | Merge pull request #7513 from opencv/dev-release-2.11.0 Update develop after v2.11.0 | 23 February 2024, 14:04:03 UTC |
| 5812ace | cvat-bot[bot] | 23 February 2024, 12:14:07 UTC | Update develop after v2.11.0 | 23 February 2024, 12:14:07 UTC |
| 0a14ea5 | cvat-bot[bot] | 23 February 2024, 10:35:03 UTC | Prepare release v2.11.0 | 23 February 2024, 10:35:03 UTC |
| 2c5bb69 | Kirill Lakhov | 22 February 2024, 16:54:10 UTC | Add test for Ground truth Job list (#7490) | 22 February 2024, 16:54:10 UTC |
| 7286d65 | Roman Donchenko | 19 February 2024, 14:41:40 UTC | Drop support of the TFRecord format (#7416) Usage statistics on app.cvat.ai show that this format is rarely used, with single-digit numbers of projects/tasks/jobs being exported or imported using this format. Moreover, TensorFlow's popularity appears to be shrinking, so I'm not expecting this format to make a comeback. Meanwhile, supporting this format has a cost that has to be borne by everyone deploying CVAT, because it requires TensorFlow to be installed and loaded. This has various ill effects: 1. Loading time is increased. In my testing, even a command as trivial as `manage.py --help` is slowed down by 3.6 seconds. This may not seem like much, but the effect is compounded, because we have multiple processes (server + workers) all loading the same codebase. Plus, the container entrypoint may execute several Django commands. 2. Memory usage is increased. TensorFlow adds ~100MB of RAM usage per process with data alone; and the libraries add more (although it's hard to estimate the impact of library code, since it can be shared between processes in RAM). 3. Docker image size is increased by ~1.5GB (when unpacked). This is more than half of the current total size! Building time is increased as well. Overall, it seems that the drawbacks of keeping support for this format outweigh the benefits, so it's time to drop it. | 19 February 2024, 14:41:40 UTC |
| f0af22a | Boris Sekachev | 19 February 2024, 13:45:25 UTC | Removed extra cypress configs (#7488) | 19 February 2024, 13:45:25 UTC |
| 42be015 | Roman Donchenko | 16 February 2024, 13:03:07 UTC | Add events for importing/exporting annotations/datasets (#7476) This can provide useful statistics on the use of this functionality. Note that I chose to use the same scope for operations on projects, tasks and jobs, because the import/export operations work more-or-less the same on each of them and have the same parameters. It's still possible to distinguish which type of object the operation was performed on by examining the various `*_id` fields in the event. | 16 February 2024, 13:03:07 UTC |
| 9c048f2 | Roman Donchenko | 16 February 2024, 13:01:30 UTC | Don't save all fields of a model when bumping the update date (#7450) Currently, there are a lot of places where changing one object requires updating the `updated_date` field on other objects. Usually, the `.save` method is used for this purpose, which results in a generic SQL `UPDATE` query that replaces the values in all columns. Introduce and use a specialized method that only changes the date. This provides the following advantages: * Prevents the date updates from overwriting updates to other fields that may happen at the same time. * Possibly makes the updates more efficient due to fewer columns being updated (I have no data on this, though). * Makes it easier to recognize the purpose of the query when analyzing logs/live statistics. * Makes the purpose of the code more obvious. Additionally, update `__save_job_handler`, where we don't want to save _just_ the date, but we still only need to save two fields. | 16 February 2024, 13:01:30 UTC |
| 972a218 | Roman Donchenko | 16 February 2024, 12:31:21 UTC | Make event-related identifiers in cvat-core consistent (#7482) | 16 February 2024, 12:31:21 UTC |
| 6260232 | Roman Donchenko | 15 February 2024, 16:49:16 UTC | Record DB-related events only after changes are committed (#7477) This is a small addendum to #7460, which I couldn't include in that PR, because it was blocked by #7430. | 15 February 2024, 16:49:16 UTC |
| 6673bb1 | Andrey Zhavoronkov | 15 February 2024, 14:08:45 UTC | Modify backend entrypoint to wait redis (inmem and ondisk) (#7479) Currently CVAT is just waiting for the database to start the server process and the worker processes, but if redis instances (for queue and cache processing) are not running we will get a non-functional cvat. This PR adds availability checking for redis_ondisk and redis_inmem | 15 February 2024, 14:08:45 UTC |
| 11cec4c | Kirill Lakhov | 15 February 2024, 13:31:53 UTC | Migrate quality UI changes (#7441) | 15 February 2024, 13:31:53 UTC |
| e8384f8 | Mariia Acoca | 13 February 2024, 14:00:57 UTC | Run actions documentation added (#7448) | 13 February 2024, 14:00:57 UTC |
| f477e0b | Roman Donchenko | 13 February 2024, 13:43:08 UTC | Defer most signal handling code until after the end of the current transaction (#7460) Non-database actions like deleting directories, sending webhooks, scheduling reports should only be done after the current transaction is committed. If we do it immediately, and the transaction is later aborted, then we will have (for example) sent a webhook about an event that didn't actually happen. There's also a secondary benefit to moving this action outside of the transaction; the less time we spend inside a transaction, the better, since a transaction may lock out other clients from working on the affected DB rows. In addition, prevent the affected actions from crashing the view handler with an exception (using the `robust=True` option). I don't think it's reasonable to (for example) return a 500 response to a `PATCH` request just because we failed to send the corresponding webhook. There is one more type of action that should be modified in this way (sending events), but it would be easier to do that after a refactoring that I did in another patch, so I'll do it later. | 13 February 2024, 13:43:08 UTC |
| b2a1065 | Maria Khrustaleva | 13 February 2024, 13:42:08 UTC | Add failure_ttl when enqueueing task creation job (#7475) By default failed rq jobs are kept for 1 year. It is too long and leads to keeping a lot of unnecessary results in Redis. | 13 February 2024, 13:42:08 UTC |
| 58173c4 | Roman Donchenko | 13 February 2024, 13:02:28 UTC | Reduce repetitive code in cvat/apps/events/handlers.py (#7430) <!-- 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 is a preparatory PR before I add more events. ### 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. | 13 February 2024, 13:02:28 UTC |
| ad60b82 | Maria Khrustaleva | 12 February 2024, 14:34:23 UTC | Add the ability to disable sign-in/sign-up in the UI (#7348) Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru> | 12 February 2024, 14:34:23 UTC |
| 4e2b2df | Roman Donchenko | 09 February 2024, 18:00:28 UTC | Remove the "Cancelling Duplicates" workflow (#7467) | 09 February 2024, 18:00:28 UTC |
| 24479c0 | Boris Sekachev | 09 February 2024, 13:41:40 UTC | Click instead of hover to open dropdown menus (#7431) | 09 February 2024, 13:41:40 UTC |
| 8bf8fe5 | Boris Sekachev | 09 February 2024, 11:19:04 UTC | Merge pull request #7468 from opencv/dev-release-2.10.3 Update develop after v2.10.3 | 09 February 2024, 11:19:04 UTC |
| eb2dfa8 | cvat-bot[bot] | 09 February 2024, 11:12:10 UTC | Update develop after v2.10.3 | 09 February 2024, 11:12:10 UTC |
| 73bf676 | cvat-bot[bot] | 09 February 2024, 10:12:43 UTC | Prepare release v2.10.3 | 09 February 2024, 10:12:43 UTC |
| b4eed78 | Roman Donchenko | 09 February 2024, 07:22:08 UTC | Reblacken Python code (#7461) Black 24 is upon us, and with it a new stable code style. Reformat all code to prevent CI failures in future PRs. | 09 February 2024, 07:22:08 UTC |
| 8e6e46a | Boris Sekachev | 08 February 2024, 18:07:23 UTC | Exception event: 'not authentificated' was removed from analytics (#7457) | 08 February 2024, 18:07:23 UTC |
| 9f517d1 | Boris Sekachev | 08 February 2024, 16:12:50 UTC | Reduced number of requests from client to server (#7446) | 08 February 2024, 16:12:50 UTC |
| 22d4e04 | Roman Donchenko | 07 February 2024, 07:43:13 UTC | Add an `application_name` PostgreSQL connection parameter (#7275) <!-- 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 will let us more easily identify PostgreSQL sessions that come from CVAT. See <https://www.postgresql.org/docs/15/runtime-config-logging.html#GUC-APPLICATION-NAME>. ### 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. --> ```sql SELECT * FROM pg_stat_activity; ``` ### 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. | 07 February 2024, 07:43:13 UTC |
| dc40be2 | Roman Donchenko | 06 February 2024, 16:34:37 UTC | Bump actions/checkout and actions/setup-node to v4 (#7442) | 06 February 2024, 16:34:37 UTC |
