| bca5f57 | Kirill Lakhov | 03 October 2023, 11:51:51 UTC | Improved Cloud Storage form/create task error message (#6890) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Added form validation. CS manifest can be only in `.jsonl` format  Improved error message on task creation form if some incorrect files are selected. Shown their extensions  ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [x] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 03 October 2023, 11:51:51 UTC |
| e9d485a | Roman Donchenko | 03 October 2023, 06:44:27 UTC | Remove unused class KeyFramesVideoStreamReader (#6935) As far as I can see, the `only_key_frames` parameter to `VideoManifestManager.link` is not, and has never been, used, and therefore `KeyFramesVideoStreamReader` is unused as well. | 03 October 2023, 06:44:27 UTC |
| 885d26b | Nikita Manovich | 02 October 2023, 17:43:26 UTC | Release v2.7.3 | 02 October 2023, 17:43:26 UTC |
| 73199d6 | Nikita Manovich | 02 October 2023, 17:42:01 UTC | Release v2.7.3 | 02 October 2023, 17:42:01 UTC |
| 797de03 | Andrey Zhavoronkov | 02 October 2023, 14:34:27 UTC | Prepare to new version | 02 October 2023, 14:36:01 UTC |
| df959b5 | Andrey Zhavoronkov | 02 October 2023, 14:31:28 UTC | Merge remote-tracking branch 'origin/master' into release-2.7.3 | 02 October 2023, 14:31:28 UTC |
| cc226e2 | Andrey Zhavoronkov | 02 October 2023, 14:31:10 UTC | Bump version to 2.7.3 | 02 October 2023, 14:31:10 UTC |
| 2dfe6db | Andrey Zhavoronkov | 02 October 2023, 14:22:17 UTC | Fixed error when getting data from CS and cache=True (#6932) Fix ```python AttributeError: 'tuple' object has no attribute 'tobytes' ``` | 02 October 2023, 14:22:17 UTC |
| 92906a7 | Kirill Lakhov | 02 October 2023, 09:33:42 UTC | Try to fix unstable `case_69` (#6926) | 02 October 2023, 09:33:42 UTC |
| 7ce2c37 | Cuong Nguyen Duc | 02 October 2023, 07:37:33 UTC | Update attach-cloud-storage.md (#6762) | 02 October 2023, 07:37:33 UTC |
| b3d362f | Kirill Sizov | 02 October 2023, 07:30:56 UTC | Remove preheader for email confirmation message (#6482) ### Motivation and context Sometimes a see this in my emails:  | 02 October 2023, 07:30:56 UTC |
| d31012e | Roman Donchenko | 02 October 2023, 07:25:52 UTC | Security update cryptography from 41.0.3 to 41.0.4 (#6914) See <https://github.com/advisories/GHSA-v8gr-m533-ghj9>. | 02 October 2023, 07:25:52 UTC |
| 78d45fb | Paweł Kotiuk | 02 October 2023, 07:20:14 UTC | New , form-based Issue templates for Github repository (#6919) I think a proper issue template based on simple form would make creating a proper issues easier for users. These templates can be checked on my fork of this repo: https://github.com/pktiuk/cvat/issues/new/choose  | 02 October 2023, 07:20:14 UTC |
| 4cdd68e | Roman Donchenko | 02 October 2023, 07:11:40 UTC | Avoid relying on PyAV-provided video frame count (#6929) They are not reliable. In particular, MP4 has a feature called "edit lists" that allows you to set a custom playback order for the media data. With edit lists, you could only specify that a particular range of frames should be played, or that a range should be played multiple times, etc. See the following for technical details: https://developer.apple.com/documentation/quicktime-file-format/edit_list_atom FFmpeg follows edit lists when decoding videos. However, the frame count returned by PyAV's `Stream.frames` property is the number of frames in the raw media data and does not reflect the modifications applied by an edit list. When we build a video manifest, we use `Stream.frames` if it's non-zero. Therefore, in the presence of an edit list we will obtain a frame count that does not match the actual number of frames that we can get out of the video. FWIW, edit lists are probably not the only way that `Stream.frames` could be inaccurate, it's just the reason behind a specific problem I encountered. Since we already have to handle the situation where `Stream.frames` is not available, just pretend it doesn't exist and always count frames by traversing the entire video. I don't think it even matters much, since we have to do it anyway to build the rest of the manifest. We also have to stop validating the frame count in a user-provided manifest, which is unfortunate, but it doesn't seem worthwhile to decode the entire video just for that. | 02 October 2023, 07:11:40 UTC |
| d497bb6 | Roman Donchenko | 29 September 2023, 07:03:49 UTC | Remove the Git repository synchronization functionality (#6904) This functionality has accumulated significant technical debt: * Most importantly, it does not use the current authorization system, rendering it accessible only for admin users. * It doesn't follow the regular API conventions and is not visible in the API schema. This necessitates a special code in the SDK. * The initialization code in `base.py` is not safe when multiple instances of the server starts at the same time (each instance may end up generating its own key). The team has decided that the cost of fixing these issues outweighs the benefit of the functionality, so remove it. | 29 September 2023, 07:03:49 UTC |
| 4a487c3 | Nikita Manovich | 27 September 2023, 12:51:29 UTC | [Snyk] Security upgrade pillow from 9.3.0 to 10.0.1 (#6907) Co-authored-by: snyk-bot <snyk-bot@snyk.io> Co-authored-by: Roman Donchenko <roman@cvat.ai> | 27 September 2023, 12:51:29 UTC |
| 2451f63 | Anna Petrovicheva | 27 September 2023, 12:25:48 UTC | [Snyk] Security upgrade pillow from 9.5.0 to 10.0.1 (#6909) Co-authored-by: snyk-bot <snyk-bot@snyk.io> Co-authored-by: Roman Donchenko <roman@cvat.ai> | 27 September 2023, 12:25:48 UTC |
| f47f1a3 | Nikita Manovich | 27 September 2023, 10:44:25 UTC | [Snyk] Security upgrade pillow from 9.4.0 to 10.0.1 (#6908) Co-authored-by: snyk-bot <snyk-bot@snyk.io> | 27 September 2023, 10:44:25 UTC |
| d68b359 | Roman Donchenko | 26 September 2023, 09:26:10 UTC | Merge pull request #6897 from opencv/az/dev-release-2.7.2 Dev release 2.7.2 | 26 September 2023, 09:26:10 UTC |
| 4c29752 | Roman Donchenko | 26 September 2023, 09:23:22 UTC | Merge pull request #6896 from opencv/release-2.7.2 Release v2.7.2 | 26 September 2023, 09:23:22 UTC |
| 8b72768 | Andrey Zhavoronkov | 25 September 2023, 11:21:36 UTC | Prepare for 2.8.0 | 25 September 2023, 11:21:36 UTC |
| 2bd22b8 | Andrey Zhavoronkov | 25 September 2023, 11:17:33 UTC | Merge remote-tracking branch 'origin/master' into release-2.7.2 | 25 September 2023, 11:17:33 UTC |
| 58f34e6 | Andrey Zhavoronkov | 25 September 2023, 11:14:37 UTC | Bump version to 2.7.2 | 25 September 2023, 11:14:37 UTC |
| ee1d421 | Andrey Zhavoronkov | 22 September 2023, 13:33:32 UTC | Improved chunk generation from cloud storages (#6881) | 22 September 2023, 13:33:32 UTC |
| adc8895 | Maria Khrustaleva | 22 September 2023, 13:15:59 UTC | Fix leaving the organization (#6422) Users should have the option to leave the organization. | 22 September 2023, 13:15:59 UTC |
| 3220147 | Mariia Acoca | 22 September 2023, 12:17:21 UTC | Gamma Correction and workspace documentation updated (#6873) | 22 September 2023, 12:17:21 UTC |
| 612f0e7 | Mariia Acoca | 22 September 2023, 12:10:22 UTC | Data export documentation update (#6795) | 22 September 2023, 12:10:22 UTC |
| 26693dd | Andrey Zhavoronkov | 21 September 2023, 15:40:41 UTC | Do not copy extra files if both server_files and job_file_mapping are… (#6879) | 21 September 2023, 15:40:41 UTC |
| 657e361 | Boris Sekachev | 15 September 2023, 13:56:21 UTC | [Refactoring] Removed custom exif rotation method (#6835) | 15 September 2023, 13:56:21 UTC |
| b2957ab | Boris Sekachev | 15 September 2023, 13:55:27 UTC | Do not reload the page when changing job state (#6851) | 15 September 2023, 13:55:27 UTC |
| 7297244 | Nikita Manovich | 15 September 2023, 13:52:21 UTC | Release v2.7.1 | 15 September 2023, 13:52:21 UTC |
| 10e71d6 | Nikita Manovich | 15 September 2023, 13:51:23 UTC | Release v2.7.1 | 15 September 2023, 13:51:23 UTC |
| 271daf6 | Andrey Zhavoronkov | 15 September 2023, 12:07:11 UTC | Prepare for 2.8.0 | 15 September 2023, 12:07:11 UTC |
| 68bfdc5 | Andrey Zhavoronkov | 15 September 2023, 12:04:48 UTC | Merge remote-tracking branch 'origin/master' into release-2.7.1 | 15 September 2023, 12:04:48 UTC |
| 70fd466 | Andrey Zhavoronkov | 15 September 2023, 12:04:27 UTC | Bump version to 2.7.1 | 15 September 2023, 12:04:27 UTC |
| 97c7f1d | Maria Khrustaleva | 15 September 2023, 10:26:36 UTC | Fix issues 6836 6837 (#6850) Resolve https://github.com/opencv/cvat/issues/6837 Resolve https://github.com/opencv/cvat/issues/6836 | 15 September 2023, 10:26:36 UTC |
| 76844a6 | Boris Sekachev | 15 September 2023, 09:40:56 UTC | Added plugin option: preventMethodCallWithReturn (#6858) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 15 September 2023, 09:40:56 UTC |
| e2ffbd4 | Kirill Sizov | 14 September 2023, 15:27:56 UTC | Upgrade Datumaro to fix problem with EXIF rotated images during dataset importing in YOLO format (#6860) | 14 September 2023, 15:27:56 UTC |
| b30a5a1 | Boris Sekachev | 13 September 2023, 08:13:11 UTC | Added test to check rotated tif image (#6842) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [x] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: kirill-sizov <sizow.k.d@gmail.com> | 13 September 2023, 08:13:11 UTC |
| 8054543 | Boris Sekachev | 13 September 2023, 07:01:14 UTC | Extended error logging (#6844) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Not all the errors, occured on client are logged now. Only uncaught exceptions. The core idea of this PR is to log all the error message, shown to a user (except of server-related errors 400, 500, 403, 0 and others) ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 13 September 2023, 07:01:14 UTC |
| e986afc | Nikita Manovich | 13 September 2023, 06:44:55 UTC | Release v2.7.0 | 13 September 2023, 06:44:55 UTC |
| b23fe72 | Nikita Manovich | 13 September 2023, 06:43:54 UTC | Release v2.7.0 | 13 September 2023, 06:43:54 UTC |
| 8962c12 | Kirill Lakhov | 12 September 2023, 08:26:46 UTC | Add test for mouseover mask/skeleton (#6828) <!-- 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 #6743, #6753 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 12 September 2023, 08:26:46 UTC |
| 5518cab | Andrey Zhavoronkov | 11 September 2023, 18:52:17 UTC | Prepare for 2.8.0 | 12 September 2023, 04:54:10 UTC |
| b611521 | Andrey Zhavoronkov | 11 September 2023, 18:49:02 UTC | Merge remote-tracking branch 'origin/master' into release-2.7.0 | 11 September 2023, 18:49:02 UTC |
| 8c2a1dd | Andrey Zhavoronkov | 11 September 2023, 18:42:42 UTC | update CHANGELOG | 11 September 2023, 18:42:42 UTC |
| 9345062 | Andrey Zhavoronkov | 11 September 2023, 09:17:00 UTC | Bump version to 2.7.0 | 11 September 2023, 18:41:02 UTC |
| daf774a | Maria Khrustaleva | 11 September 2023, 17:36:47 UTC | Update public repo (#6208) The PR contains several improvements and changes that are mainly aimed at supporting the crowdsourcing plugin. **Server changes:** - Added support for JSON filter description - Fixed converter in AbstractArrayField - Added logic for working with public assets (GET /assets/{uuid}/public endpoint, is_public model field) - Added several fixes for crowdsourcing users to be able to work - Deleted dead code - Added support for OPA rules that are located not in the default directory | 11 September 2023, 17:36:47 UTC |
| 32647e0 | Maria Khrustaleva | 11 September 2023, 10:17:26 UTC | Fix swagger specification (#6825) Resolved #6823 | 11 September 2023, 10:17:26 UTC |
| c87d05a | Nikita Manovich | 11 September 2023, 10:16:21 UTC | Upgraded GitPython and NumPy python packages (#6843) #### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - cvat/requirements/base.txt <details> <summary>⚠️ <b>Warning</b></summary> ``` tensorboard 2.11.2 requires werkzeug, which is not installed. tensorboard 2.11.2 has requirement setuptools>=41.0.0, but you have setuptools 39.0.1. ``` </details> #### Vulnerabilities that will be fixed ##### By pinning: Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:-------------------------  | **658/1000** <br/> **Why?** Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3 | Directory Traversal <br/>[SNYK-PYTHON-GITPYTHON-5876644](https://snyk.io/vuln/SNYK-PYTHON-GITPYTHON-5876644) | `gitpython:` <br> `3.1.33 -> 3.1.35` <br> | No | Proof of Concept (*) Note that the real score may have changed since the PR was raised. Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded. Check the changes in this PR to ensure they won't cause issues with your project. ------------ **Note:** *You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.* For more information: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiJkNTVhNzRlOS03MGJkLTRjZmUtYmEyYi02NjE4NzFjNTA4NmYiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6ImQ1NWE3NGU5LTcwYmQtNGNmZS1iYTJiLTY2MTg3MWM1MDg2ZiJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source=github&utm_medium=referral&page=fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source=github&utm_medium=referral&page=fix-pr/settings) 📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities) [//]: # (snyk:metadata:{"prId":"d55a74e9-70bd-4cfe-ba2b-661871c5086f","prPublicId":"d55a74e9-70bd-4cfe-ba2b-661871c5086f","dependencies":[{"name":"gitpython","from":"3.1.33","to":"3.1.35"}],"packageManager":"pip","projectPublicId":"4bbc4b80-3fb9-4009-a7bb-51016d44946b","projectUrl":"https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-PYTHON-GITPYTHON-5876644"],"upgrade":[],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","pr-warning-shown","priorityScore"],"priorityScoreList":[658],"remediationStrategy":"vuln"}) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Directory Traversal](https://learn.snyk.io/lesson/directory-traversal/?loc=fix-pr) | 11 September 2023, 10:16:21 UTC |
| 705db7b | Paweł Kotiuk | 11 September 2023, 10:15:32 UTC | Add admin action for easy deactivation of users (#6314) Minor quality of life improvement which helps managing status of users. | 11 September 2023, 10:15:32 UTC |
| 6826dda | Boris Sekachev | 11 September 2023, 08:12:35 UTC | Fixed task progress report for 3rdparty users (#6834) | 11 September 2023, 08:12:35 UTC |
| fa688c5 | PMazarovich | 11 September 2023, 07:59:45 UTC | Setup nuclio timeout (#6840) See these several issues. They are connected to each other in some way. The thing is that nuclio has a default timeout of 1 minute. With this change we can force nuclio dashboard not to terminate the connection. https://github.com/nuclio/nuclio/issues/3016 https://github.com/opencv/cvat/issues/3301 https://github.com/opencv/cvat/issues/6041 | 11 September 2023, 07:59:45 UTC |
| 2b29abb | Roman Donchenko | 08 September 2023, 13:39:03 UTC | Sort requirements .in files to make them easier to navigate (#6748) | 08 September 2023, 13:39:03 UTC |
| 8a4ec5d | Kirill Lakhov | 08 September 2023, 11:34:19 UTC | Add test for gamma correction filter (#6833) <!-- 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 #6771 ### 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. --> Added cypress test ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - ~~[ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file~~ - ~~[ ] I have updated the documentation accordingly~~ - [x] I have added tests to cover my changes - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 08 September 2023, 11:34:19 UTC |
| 66fb026 | Nikita Manovich | 06 September 2023, 18:53:07 UTC | Release v2.6.2 | 06 September 2023, 18:53:07 UTC |
| 7721b26 | Nikita Manovich | 06 September 2023, 18:52:11 UTC | Release v2.6.2 ### Added - Gamma correcton filter (<https://github.com/opencv/cvat/pull/6771>) - Introduced the feature to hide or show objects in review mode (<https://github.com/opencv/cvat/pull/6808>) ### Changed - \[Helm\] Database migrations are now executed as a separate job, rather than in the server pod, to mitigate the risk of data corruption when using multiple server replicas (<https://github.com/opencv/cvat/pull/6780>) - Clicking multiple times on icons in the left sidebar now toggles the corresponding popovers open and closed (<https://github.com/opencv/cvat/pull/6817>) - Transitioned to using KeyDB with FLASH for data chunk caching, replacing diskcache (<https://github.com/opencv/cvat/pull/6773>) ### Removed - Removed outdated use of hostnames when accessing Git, OpenCV, or analytics via the UI (<https://github.com/opencv/cvat/pull/6799>) - Removed the Feedback/Share component (<https://github.com/opencv/cvat/pull/6805>) ### Fixed - Resolved the issue of the canvas zooming while scrolling through the comments list in an issue (<https://github.com/opencv/cvat/pull/6758>) - Addressed the bug that allowed for multiple issue creations upon initial submission (<https://github.com/opencv/cvat/pull/6758>) - Fixed the issue of running deep learning models on non-JPEG compressed TIFF images (<https://github.com/opencv/cvat/pull/6789>) - Adjusted padding on the tasks, projects, and models pages (<https://github.com/opencv/cvat/pull/6778>) - Corrected hotkey handlers to avoid overriding default behavior when modal windows are open (<https://github.com/opencv/cvat/pull/6800>) - Resolved the need to move the mouse to activate brush or eraser effects; a single click is now sufficient (<https://github.com/opencv/cvat/pull/6800>) - Fixed a memory leak issue in the logging system (<https://github.com/opencv/cvat/pull/6804>) - Addressed a race condition that occurred during the initial creation of `secret_key.py` (<https://github.com/opencv/cvat/pull/6775>) - Eliminated duplicate log entries generated by the CVAT server (<https://github.com/opencv/cvat/pull/6766>) | 06 September 2023, 18:52:11 UTC |
| 21dccba | Andrey Zhavoronkov | 06 September 2023, 14:57:04 UTC | Prepare to new version | 06 September 2023, 17:59:39 UTC |
| 6545c0a | Andrey Zhavoronkov | 06 September 2023, 16:12:44 UTC | Merge branch 'master' into release-2.6.2 | 06 September 2023, 16:12:44 UTC |
| a5b93fd | Andrey Zhavoronkov | 06 September 2023, 14:54:10 UTC | update CHANGELOG | 06 September 2023, 16:09:25 UTC |
| 60a5ca4 | Andrey Zhavoronkov | 06 September 2023, 14:52:20 UTC | Bump version to 2.6.2 | 06 September 2023, 16:09:25 UTC |
| c4c7d69 | Kirill Lakhov | 06 September 2023, 16:05:33 UTC | Add gamma correction filter (#6821) | 06 September 2023, 16:05:33 UTC |
| b648f74 | Andrey Zhavoronkov | 06 September 2023, 14:54:10 UTC | update CHANGELOG | 06 September 2023, 14:54:10 UTC |
| bf13f75 | Andrey Zhavoronkov | 06 September 2023, 14:52:20 UTC | Bump version to 2.6.2 | 06 September 2023, 14:52:20 UTC |
| 8c2b2d6 | Mariia Acoca | 06 September 2023, 14:47:13 UTC | changelog updates (#6820) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 06 September 2023, 14:47:13 UTC |
| 943fbcb | Boris Sekachev | 06 September 2023, 14:11:53 UTC | Do not trigger hotkeys when modals are opened (#6800) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Resolved #6788 + better UX because now you can use focus and enter/space/tab on modal windows Additionally, minor fix for #6612 (resolved #6612) Better focus handling when remove locked object/issue or changing workspace ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [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> | 06 September 2023, 14:11:53 UTC |
| 4c0a2bc | Andrey Zhavoronkov | 06 September 2023, 13:46:45 UTC | [Snyk] Security upgrade gitpython from 3.1.32 to 3.1.33 (#6784) Co-authored-by: snyk-bot <snyk-bot@snyk.io> | 06 September 2023, 13:46:45 UTC |
| 92f1372 | Roman Donchenko | 06 September 2023, 13:33:43 UTC | Fix log message duplication (#6766) There are two independent problems that cause some log messages to be printed twice: * In the CVAT logging configuration, we attach a console handler to the `cvat` and `django` loggers. However, when any library[1] used by CVAT uses one of the top-level `logging` functions (e.g. `logging.info`), then it will cause the root logger to get autoconfigured with another console handler. Since `cvat` and `django` are configured to propagate events to the ancestor logger's handlers, those events are passed to _two_ console handlers, so they are printed twice. Fix it by moving our handlers to the root logger. If the root logger has handlers, it will no longer get autoconfigured when top-level `logging` functions are invoked; so there will only be one console handler in the logger chain. An alternative would be to configure the root logger with a `NullHandler` (which will also disable autoconfiguration), but this will suppress all logs that are coming from places other than Django and CVAT, which seems undesirable. * The supervisord config file for the server redirects the server's stdout to supervisord's stdout. However, supervisord already displays the stdout of all child processes due to the `loglevel=debug` setting. So all stdout messages of the server are displayed twice. Fix it by removing the redirection. [1] Specifically, Datumaro does this. It could probably be fixed, but that wouldn't fix the root problem, which is the duplicate console handler. | 06 September 2023, 13:33:43 UTC |
| 182a645 | Andrey Zhavoronkov | 06 September 2023, 12:10:47 UTC | Rework chunk cache (#6773) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: Roman Donchenko <roman@cvat.ai> | 06 September 2023, 12:10:47 UTC |
| 84ac0c2 | Boris Sekachev | 06 September 2023, 11:50:56 UTC | Revert "Add gamma correction filter" (#6818) Reverts opencv/cvat#6771 Failed tests | 06 September 2023, 11:50:56 UTC |
| 7a2bde2 | Kirill Lakhov | 06 September 2023, 11:44:47 UTC | Add gamma correction filter (#6771) <!-- 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. --> Adds gamma correction filter  ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - [x] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru> | 06 September 2023, 11:44:47 UTC |
| 84c0816 | Boris Sekachev | 06 September 2023, 09:14:10 UTC | Improved click handling on left sidebar (#6817) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Resolved #6616 Before:  After:  ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 06 September 2023, 09:14:10 UTC |
| ec674ab | Boris Sekachev | 06 September 2023, 06:18:20 UTC | Display hide/show buttons in review mode (#6808) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Resolved #6746 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 06 September 2023, 06:18:20 UTC |
| ab7c663 | Roman Donchenko | 05 September 2023, 20:02:00 UTC | Fix a race condition with initial secret_key.py creation (#6775) Currently, it's possible (even if unlikely) for multiple backend processes to create and use different Django `SECRET_KEY` values, because the following scenario can happen: * process 1: fail to import `secret_key.py` * process 2: fail to import `secret_key.py` * process 1: generate a new `secret_key.py` * process 1: import `secret_key.py` * process 2: generate a new `secret_key.py` * process 2: import `secret_key.py` Fix this by making it so that `secret_key.py` is created atomically, and never overwritten if it already exists. In addition, only generate the secret key if the import fails due to the module not being found, since other failure reasons suggest incorrect configuration or data corruption, and so require administrator attention. | 05 September 2023, 20:02:00 UTC |
| a1a4093 | Boris Sekachev | 05 September 2023, 13:50:34 UTC | Removed unused feedback component (#6805) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 05 September 2023, 13:50:34 UTC |
| dcc0182 | Boris Sekachev | 05 September 2023, 13:25:13 UTC | Fixed error for non-jpeg compressed images in original chunks (#6789) Resolved #6598 | 05 September 2023, 13:25:13 UTC |
| 431cf3d | Nikita Manovich | 05 September 2023, 13:22:31 UTC | Removed separate loggers for each task and project (#6804) We have a memory leak in the logging system. The patch doesn't have the aim to redesign the logging system. Only to fix the memory leak and redirect all messages into cvat_server.log file. In the future it is better to think which error messages are really helpful and send them to ClickHouse instead of a local file. It will allow to avoid any problems with multi processing. Also we have huge amount of logs inside ClickHouse. I don't see any reason to have some of them on the file system. | 05 September 2023, 13:22:31 UTC |
| 2dd4f25 | Mariia Acoca | 05 September 2023, 11:17:05 UTC | images update and other small fixes (#6803) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 05 September 2023, 11:17:05 UTC |
| 46dd95c | Boris Sekachev | 05 September 2023, 08:45:40 UTC | Removed prefix where not necessary (#6799) | 05 September 2023, 08:45:40 UTC |
| ae30755 | Mariia Acoca | 05 September 2023, 08:32:39 UTC | Toloka Requester Documentation (#6744) | 05 September 2023, 08:32:39 UTC |
| b3ef24e | Nikita Manovich | 05 September 2023, 07:29:21 UTC | Merge pull request #6802 from SpecLad/rm-django-configuration Remove the DJANGO_CONFIGURATION environment variable | 05 September 2023, 07:29:21 UTC |
| 57c23b0 | Roman Donchenko | 04 September 2023, 12:10:49 UTC | Remove the DJANGO_CONFIGURATION environment variable There are a few issues with it: * It doesn't work for the Enterprise version, because its settings module is not located under `cvat.settings`. * The name `DJANGO_CONFIGURATION` suggests that it's defined by Django, but it isn't. It's a CVAT-specific variable. There's also a 3rd-party module that uses this variable (django-configurations), but with different semantics, which could cause confusion. * It's just redundant to have two variables that effectively do the same thing (`DJANGO_CONFIGURATION` and `DJANGO_SETTINGS_MODULE`). Besides its runtime effect, `DJANGO_CONFIGURATION` is also used in the Dockerfile to select the packages to install. I could see that still being useful, so replace it with a build-only variable named `CVAT_CONFIGURATION`. | 04 September 2023, 13:57:16 UTC |
| 8c8cf70 | Roman Donchenko | 04 September 2023, 10:30:41 UTC | Bump nodemon version (#6749) <!-- 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 gets rid of a dependency on a vulnerable version of semver. ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - ~~[ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file~~ - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 04 September 2023, 10:30:41 UTC |
| ff44e43 | Roman Donchenko | 04 September 2023, 09:23:34 UTC | helm-chart: make sure database migrations are only run by one process (#6780) To do that, remove the running of migrations from the server pod(s), and add a Kubernetes job to do it instead. This will prevent Django from corrupting the database when two or more instances are started up at the same time. | 04 September 2023, 09:23:34 UTC |
| 62eb867 | Kirill Lakhov | 02 September 2023, 06:35:59 UTC | Fixed paddings on tasks/projects/models pages (#6778) <!-- 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 some small issues on different pages - Task page  - Projects page  ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file -~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [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 September 2023, 06:35:59 UTC |
| cc5a7b4 | Roman Donchenko | 02 September 2023, 06:34:20 UTC | Fix cosmetic issues in the cloud storage creation form (#6783) Specifically, with the AWS credential fields: * Replace SHOUTY CAPS with normal sentence case. * Remove the word "ID" from the label of the second field; it's a key, not an ID. * Remove gratuitous snake_case from the validation messages. <!-- 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 shouty caps were mildly irritating, and once I started fixing them, I decided I might as well fix some other issues too. ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: Boris Sekachev <sekachev.bs@gmail.com> | 02 September 2023, 06:34:20 UTC |
| 3deadda | Roman Donchenko | 01 September 2023, 09:47:58 UTC | helm-chart: move more variables to sharedBackendEnv (#6761) This reduces duplication between deployment templates. | 01 September 2023, 09:47:58 UTC |
| 213bcf0 | Boris Sekachev | 29 August 2023, 08:42:09 UTC | Fixed double issues & scaling (#6758) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context * Resolved: issues created extra times * Resolved #5639 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 29 August 2023, 08:42:09 UTC |
| f9608e8 | Roman Donchenko | 29 August 2023, 08:20:17 UTC | Rework the backend entrypoint (#6750) * Make it possible to run migrations without starting the server, and vice versa. This is not yet used, but it will be needed later to enable database initialization/upgrade in a configuration with multiple server containers. * Wait for migrations to complete in worker containers, to be safe. Workers also use the database. * Add a help message and a way to run the shell (useful for development). * Add support for initialization scripts, which helps simplify the smokescreen hack needed for the webhook tests. | 29 August 2023, 08:20:17 UTC |
| 2ce6a3c | Nikita Manovich | 25 August 2023, 14:30:03 UTC | Release v2.6.1 | 25 August 2023, 14:30:03 UTC |
| 8b93ee2 | Nikita Manovich | 25 August 2023, 14:28:54 UTC | Release v2.6.1 | 25 August 2023, 14:28:54 UTC |
| 7896623 | Andrey Zhavoronkov | 25 August 2023, 12:20:41 UTC | fixed pylint warning | 25 August 2023, 12:20:41 UTC |
| 2726c68 | Andrey Zhavoronkov | 25 August 2023, 11:36:24 UTC | Prepare changelog for development | 25 August 2023, 11:36:24 UTC |
| f5f091b | Andrey Zhavoronkov | 25 August 2023, 11:29:47 UTC | update changelog | 25 August 2023, 11:29:47 UTC |
| d61f170 | Andrey Zhavoronkov | 25 August 2023, 11:27:33 UTC | Merge remote-tracking branch 'origin/master' into release-2.6.1 | 25 August 2023, 11:27:33 UTC |
| 49604e5 | Andrey Zhavoronkov | 25 August 2023, 11:26:44 UTC | Bump version to 2.6.1 | 25 August 2023, 11:26:44 UTC |
| 3be35f6 | Boris Sekachev | 25 August 2023, 10:15:15 UTC | Fixed fail for masks & skeletons with centered text (#6753) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Resolved #6743 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: Kirill Lakhov <kirill.9992@gmail.com> | 25 August 2023, 10:15:15 UTC |
| 8625f06 | Kirill Lakhov | 24 August 2023, 14:30:46 UTC | Fix unstable test with set job assignee (#6730) | 24 August 2023, 14:30:46 UTC |
| 40f2472 | Muhammad Shalahuddin Yahya Sunarko | 24 August 2023, 08:51:57 UTC | Bump nuclio version and fix issues from the outdated version (#6610) Issue https://github.com/opencv/cvat/issues/6183 still exists in CVAT v2.5.2. Following up the addressed issue https://github.com/nuclio/nuclio/issues/2938 in the [nuclio community](https://github.com/nuclio/nuclio), they suggested to use new nuclio version (1.11.x). It seems that the templates fetching mechanism on the old nuclio versions is not supported anymore, causing the mentioned issue. ### How has this been tested? Following the [Semi-automatic and Automatic Annotation](https://opencv.github.io/cvat/docs/administration/advanced/installation_automatic_annotation/) guideline on the CVAT v2.5.2 release branch (for the sake of stability) in a RHEL 8 machine, but changed the nuclio version to 1.11.24 and disabling the `/tmp` mounting to the nuclio container. Additionally, removed the unused static IP address value in the `no_proxy` environment. Tested using [SAM model](https://www.cvat.ai/post/facebook-segment-anything-model-in-cvat) with GPU following that guideline on some random images from a remote client. | 24 August 2023, 08:51:57 UTC |
| 4a5aa28 | Boris Sekachev | 24 August 2023, 08:29:25 UTC | Improved lambda manager (#6734) * First status check request after 20 seconds may confuse users making them think that something going wrong * Fixed a reason of a big amount status check requests (repeated calls for listen() method) when user go from Tasks -> any other page -> Tasks -> any other page -> Task -> any other page -> Task, etc not closing the tab. * Fixed bug when the progress invisible if the app initialized on task page * Fixed 403 code when user tries to cancel automatic annotation * Added missed schema endpoint * Added more informative progress (for queued/in progress/fail): <img width="756" alt="image" src="https://github.com/opencv/cvat/assets/40690378/f01c45a8-a460-48c0-bec4-88266bb65a2c"> <img width="980" alt="image" src="https://github.com/opencv/cvat/assets/40690378/f9e2c5ad-c2b7-4c43-8214-34236f38103b"> | 24 August 2023, 08:29:25 UTC |
