Skip to main content

Browse the archive

https://github.com/opencv/cvat
19 April 2024, 21:00:24 UTC
sort by:
Revision Author Date Message Commit Date
c5d8a16 Yeek Sheng 19 April 2024, 12:10:45 UTC [GSoC2024] Fix import of outside track shapes in Datumaro-based formats (#7669) <!-- 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. --> Main Issue: #7571 Related Issue: #2339 I've reproduced the issue mentioned in #7571 when exporting and importing annotations using both the Datumaro and Coco 1.0 formats. Specifically, the "Switch outside" attribute isn't being applied as expected. After some investigation, I pinpointed the root cause to be the absence of the "outside" attribute in the exported annotations. To address this, I've made adjustments to the binding.py file to bypass the track_id during annotation import. This modification appears to solve the issue regarding the "Switch outside" attribute. However, it introduces a new concern: the potential loss of information, including keyframes and track_id. While this workaround offers a temporary fix, I'm contemplating a more holistic approach that entails properly handling the "outside" attribute during both the export and import processes of annotations. This method could preserve the integrity of the annotations while ensuring the functionality of the "Switch outside" attribute. I'm reaching out for feedback or suggestions on my proposed solution. Is there a preference for one of these approaches, or might there be another avenue I haven't considered? Looking forward to your insights. ### 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)) - [ ] 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> 19 April 2024, 12:10:45 UTC
4ed6d04 Taha 18 April 2024, 13:06:01 UTC [GSoC2024] add return types to fix typescript warnings (#7689) 18 April 2024, 13:06:01 UTC
5b2df0c Boris Sekachev 18 April 2024, 12:37:24 UTC Fixed 504 gateway timeout on admin page (#7767) 18 April 2024, 12:37:24 UTC
70c2fb8 zaha 18 April 2024, 11:58:19 UTC Check ground truth annotations in GT job (#7770) 18 April 2024, 11:58:19 UTC
7340faf Kirill Lakhov 18 April 2024, 11:04:52 UTC Fixed issue with y-slider of objects sidebar (#7781) 18 April 2024, 11:04:52 UTC
a5269b0 Roman Donchenko 17 April 2024, 06:17:56 UTC Remove unused IAM test config (#7746) 17 April 2024, 06:17:56 UTC
7e1fb25 dependabot[bot] 17 April 2024, 06:16:02 UTC Bump express from 4.18.2 to 4.19.2 (#7680) 17 April 2024, 06:16:02 UTC
3f3f314 dependabot[bot] 17 April 2024, 06:14:49 UTC Bump tar from 6.2.0 to 6.2.1 (#7753) 17 April 2024, 06:14:49 UTC
f0f0c15 dependabot[bot] 17 April 2024, 06:14:14 UTC Bump webpack-dev-middleware from 5.3.3 to 5.3.4 (#7668) 17 April 2024, 06:14:14 UTC
e631943 Boris Sekachev 17 April 2024, 06:00:37 UTC Upgrade Node 16 => 20 (#7766) 17 April 2024, 06:00:37 UTC
592c77f Boris Sekachev 16 April 2024, 05:16:20 UTC Merge pull request #7772 from cvat-ai/dev-release-2.12.0 Update develop after v2.12.0 16 April 2024, 05:16:20 UTC
20dfef9 cvat-bot[bot] 15 April 2024, 20:20:23 UTC Update develop after v2.12.0 15 April 2024, 20:20:23 UTC
7401c00 cvat-bot[bot] 15 April 2024, 13:03:17 UTC Prepare release v2.12.0 15 April 2024, 13:03:17 UTC
fbc2610 zaha 12 April 2024, 13:03:09 UTC Updating packages with vulnerabilities (#7713) 12 April 2024, 13:03:09 UTC
f1d308e Kavikumar M 12 April 2024, 08:28:30 UTC [GSoC2024] resolved issue #7443 (navigate over unresolved issues) (#7653) Resolved issue #7443 It skips the frames where all issues have been resolved! ### 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. 12 April 2024, 08:28:30 UTC
b13191d Boris Sekachev 11 April 2024, 15:12:32 UTC Mask stays pixelated during editing (#7747) 11 April 2024, 15:12:32 UTC
3fe396c Kirill Lakhov 11 April 2024, 13:29:28 UTC Added support for `.rar` and some other archives (#7729) <!-- 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 allows users to upload `.rar` archives during task creation. It fixes several problems: 1. Outdated mimetype for `.rar` type which is now `x-rar-compressed` 2. Adds usage of `patool` util for `pyunpack` package, which previously used only `zipfile`. Patool can handle different kinds of archives, current supported list(by mimetype) can be found in the `supportedArchives` 1. The pipeline for rar archives now is `pyunpack` -> `patool` -> `unrar` ### 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)) - ~~[ ] 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. 11 April 2024, 13:29:28 UTC
90d5e1f Ritik Raj 11 April 2024, 08:03:58 UTC [GSoC2024] - fixed attribute rename issue (#7670) This PR fixes two open issues: - Fixed the [issue](https://github.com/opencv/cvat/issues/5978) Unable to edit Attribute name #5978 - Fixed the [issue](https://github.com/opencv/cvat/issues/6503) - REST API renaming an attribute does not work #6503 Used attribute id to fetch attribute from the database and renamed it from the list received in the request. Tested it under multiple scenarios, like different attribute types, input values, and labels. ![image](https://github.com/opencv/cvat/assets/76646497/64bf8a0f-becb-442d-bf27-09e77dddfc86) 11 April 2024, 08:03:58 UTC
55ea04b Harsh Kumar 10 April 2024, 17:40:26 UTC [GSoC2024] feature: allow downloading video frames in custom extension (#7697) <!-- 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. --> Allows to download annotated video frames with custom extensions. Previously, it was only available in .png format. Resolves #3867 ### 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. --------- Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> 10 April 2024, 17:40:26 UTC
82a7635 Mariia Acoca 10 April 2024, 16:55:52 UTC Human protocol integration documentation (#7547) <!-- 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. --------- Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> 10 April 2024, 16:55:52 UTC
2e610ec Boris Sekachev 10 April 2024, 10:37:18 UTC Fix incorrect changelog fragment (#7745) 10 April 2024, 10:37:18 UTC
ada56a7 Taha 10 April 2024, 10:21:00 UTC [GSoC2024] feat: add shortcut support for pinning properties (#7709) 10 April 2024, 10:21:00 UTC
1355725 Roman Donchenko 10 April 2024, 10:15:12 UTC Fix spurious failures in `case_17_lock_hide_features.js` (#7742) 10 April 2024, 10:15:12 UTC
efbafe9 zaha 09 April 2024, 09:20:44 UTC Fix sometimes failed tests problem (#7732) 09 April 2024, 09:20:44 UTC
462b923 Yeek Sheng 08 April 2024, 05:45:21 UTC Fix Typo in "Export annotations and data from CVAT" (#7738) 08 April 2024, 05:45:21 UTC
70a7cc0 Maxim Zhiltsov 05 April 2024, 14:08:34 UTC Update datumaro dependency (#7716) <!-- 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. --> Closes https://github.com/opencv/cvat/pull/7703 Related: https://github.com/opencv/cvat/issues/7258 Related: https://github.com/opencv/cvat/pull/7125 Related: https://github.com/opencv/cvat/pull/7699 Changes: https://github.com/cvat-ai/datumaro/compare/8a14a99fe17f19d98595a2a4a74ab459051cc23b...82982b16b178eb3f39c707795bb68a3306610abf - Fixed WiderFace dataset example - Fixed export without images in Datumaro format - no empty `media` and `point_cloud` fields should be in the results ### 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. 05 April 2024, 14:08:34 UTC
f1db0fd Syed Bariman Jan 05 April 2024, 11:53:22 UTC [GSoC2024] Enhancement of empty list components (#7659) ### Motivation and context Fixes #7657 Made all of the empty-list components ui consistent. ### Checklist - [x] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> - [x] I submit my changes into the `develop` branch - [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)) ### 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: Boris Sekachev <boris.sekachev@yandex.ru> Co-authored-by: Kirill Lakhov <kirill.9992@gmail.com> 05 April 2024, 11:53:22 UTC
6c57c03 Roman Donchenko 05 April 2024, 11:12:59 UTC Update documentation and repo links after transfer to the cvat-ai organization (#7722) 05 April 2024, 11:12:59 UTC
ea47d00 Maria Khrustaleva 04 April 2024, 12:41:35 UTC Migrate to the `dj-rest-auth==5.0.2` and `django-allauth==0.57.2` (#7635) 04 April 2024, 12:41:35 UTC
2a6fd0d Boris Sekachev 04 April 2024, 08:45:47 UTC Fixed annotation menu for GT objects in GT job (#7714) 04 April 2024, 08:45:47 UTC
967a5a6 Nikita Manovich 04 April 2024, 08:40:56 UTC [Snyk] Security upgrade nginx from mainline-alpine to 1.25.4-alpine3.18 (#7625) 04 April 2024, 08:40:56 UTC
69682f2 Krishav 04 April 2024, 07:47:21 UTC [GSoC2024] Displayed total no. of annotations (#7654) 04 April 2024, 07:47:21 UTC
6c12c9e Andrew Lu 04 April 2024, 07:04:20 UTC [GSoC2024] Decode uploaded filename from request header (#7646) <!-- 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 fixes issue #6528, as filenames with special characters must be decoded from the MIME header back into UTF-8. ### 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 - [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: Andrey Zhavoronkov <andrey@cvat.ai> 04 April 2024, 07:04:20 UTC
0f60b27 Roman Donchenko 03 April 2024, 19:23:21 UTC Switch the most time-consuming pipelines to the large runner (#7723) 03 April 2024, 19:23:21 UTC
69f5de4 Roman Donchenko 03 April 2024, 13:38:25 UTC Migrate docs to a custom domain (#7698) 03 April 2024, 13:38:25 UTC
73c7081 Roman Donchenko 02 April 2024, 14:41:25 UTC Docs: fix broken internal links and ensure they stay fixed (#7695) We have quite a few broken links, which is unsurprising, as Hugo does not help detect them. This patch adds a custom shortcode (`ilink`) which validates the target path and then renders as a link. It rewrites most internal links to use this shortcode, and fixes those which were broken. Originally, I was just going to use the builtin `relref` shortcode to build the URLs, but it turns out that that does not play well with remark. It becomes confused and thinks you forgot to specify the URL altogether. `ilink` replaces the entire link, so remark has nothing to complain about. `ilink` supports a default link text, although I haven't yet used this anywhere. I also "fortified" the "about" link in `navbar.html`, although templates don't support shortcodes, so I just used the `relref` function. A few links I had to keep as-is for various reasons: * Links from the `docs/_index.md`, because they are inside a shortcode, and as far as I can tell, you can't put shortcodes in shortcode parameters. * The refresh URLs in `home.html` and `404.html`, for complicated reasons. * Links to autogenerated API documentation pages due to some known problems with generating those pages for previous releases. Finally, I had to update `build_docs.py`, because it neglected to check out `page_404.html` when rendering the docs for previous versions, and the new version of `page_404.html` will not render without the new shortcode. 02 April 2024, 14:41:25 UTC
d87613d Boris Sekachev 02 April 2024, 13:53:58 UTC Update CHANGELOG.md (#7718) 02 April 2024, 13:53:58 UTC
ec4297f Boris Sekachev 02 April 2024, 13:53:06 UTC Merge pull request #7717 from opencv/dev-release-2.11.3 Update develop after v2.11.3 02 April 2024, 13:53:06 UTC
68119c1 cvat-bot[bot] 02 April 2024, 13:48:00 UTC Update develop after v2.11.3 02 April 2024, 13:48:00 UTC
17197bf cvat-bot[bot] 02 April 2024, 12:03:13 UTC Prepare release v2.11.3 02 April 2024, 12:03:13 UTC
9c04b0c Roman Donchenko 02 April 2024, 12:01:59 UTC Remove several fields from `DataSerializer` (#7663) <!-- 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. --> `original_chunk_type` and `compressed_chunk_type` have no effect, because the task creation code overwrites these values based on `use_zip_chunks`. With `size`, the code relies on the default of zero, and attempting to overriding it will just lead to an incorrect value being saved to the database. ### 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. 02 April 2024, 12:01:59 UTC
02889ee Kirill Lakhov 29 March 2024, 13:17:42 UTC Fixed sending `/events` requests from logged out users (#7608) <!-- 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 the following problem: - When user is logged-out, the /events request is still sent. Its failing due with unauthorized request creating lots of error events on the server. They are quite useless. ### 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~~ - [ ] I have added tests to cover my changes - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru> 29 March 2024, 13:17:42 UTC
77378f1 Roman Donchenko 29 March 2024, 11:42:18 UTC Use the same algorithm to throttle quality reports as analytics reports (#7596) <!-- 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. --> See #7576 for more details. This patch extracts the high-level throttling functionality added in that patch and reuses it for quality reports. Note: in that patch I referred to this functionality as debouncing, but throttling seems like a more accurate description. It would be debouncing if the autoupdate job only ran after no updates occurred for a period, which is not how it actually works. ### 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~~ - ~~[ ] 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. 29 March 2024, 11:42:18 UTC
85f5376 Roman Donchenko 28 March 2024, 20:04:26 UTC Streamline API endpoint summaries (#7685) The current summaries are much too verbose. This makes it hard to find the endpoint you're looking for in the API docs, because it takes longer to read & understand each summary. Rewrite them to be more brief. Move any details that are too long to keep, but too important to omit, to the description. 28 March 2024, 20:04:26 UTC
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**: ![image](https://github.com/opencv/cvat/assets/63901956/bd826a8a-aacb-48e1-8501-04a9c730fa86) 3. **Expected Output**: ![image](https://github.com/opencv/cvat/assets/63901956/20a31418-3136-46bc-a04d-3c17e44dcbde) ### 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. ![after ](https://github.com/opencv/cvat/assets/50093149/4e05d9c9-6049-4900-8234-66f719976310) 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
back to top