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
a4de2fc Andrey Zhavoronkov 09 June 2023, 14:55:56 UTC Merge remote-tracking branch 'origin/master' into release-2.4.6 09 June 2023, 14:55:56 UTC
aef7a98 Andrey Zhavoronkov 09 June 2023, 13:46:52 UTC Bump version to 2.4.6 09 June 2023, 13:46:52 UTC
7181946 Paul Barsic 09 June 2023, 08:56:22 UTC Error while enabling SAM on CPU (#6249) This PR solves issue #6247 "Error while enabling SAM on CPU". It looks like the `--file` argument to `nuctl deploy` was inadvertently removed in the most recent release. This causes the process to fail with `**Error - Function name cannot be empty`. I was able to reproduce this error on my own system. ### Motivation and context This change fixes a minor error. ### How has this been tested? I tested this by reproducing the bug with the command from the `cvat/components` directory: `nuctl deploy --project-name cvat --path "./serverless/pytorch/foolwood/siammask/nuclio" --platform local` I then edited the `deploy_cpu.sh` file, executed the same command, and completed a successful deployment, which I verified with `nuctl get functions`. 09 June 2023, 08:56:22 UTC
e5ea213 Paweł Kotiuk 08 June 2023, 20:27:48 UTC Add support for semi-auto annotations (#6263) Closes: https://github.com/opencv/cvat/issues/6261 <!-- 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 kind of annotations was already mentioned in docs, but it was not implemented. ### 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 just deployed it with help of the docker-compose.dev.yml you provided. ### 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. (it was already in docs) - [ ] 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> Co-authored-by: Boris Sekachev <sekachev.bs@gmail.com> 08 June 2023, 20:27:48 UTC
9fab8c5 Maxim Zhiltsov 08 June 2023, 16:01:26 UTC Add dataset examples and update some links in docs (#6259) <!-- 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 dataset example links - Fixed COCO links to Datumaro docs ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 08 June 2023, 16:01:26 UTC
6233491 Mariia Acoca 08 June 2023, 15:55:22 UTC webhooks documentation updated (#6246) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 08 June 2023, 15:55:22 UTC
cb207b6 Kirill Sizov 08 June 2023, 15:54:52 UTC Update documentation (#6270) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 08 June 2023, 15:54:52 UTC
7fa1925 Kirill Lakhov 08 June 2023, 15:53:41 UTC Allow slashes in export filename (#6265) <!-- 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. Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru> 08 June 2023, 15:53:41 UTC
504a66e Kirill Sizov 08 June 2023, 14:45:05 UTC lambda manager: send signal before calling function (#6215) 08 June 2023, 14:45:05 UTC
8df8872 Maxim Zhiltsov 08 June 2023, 12:32:14 UTC Fix predefined sorting for task data (#5083) Fixes #5061, #4179 - Added a way to declare custom file ordering for the local task data uploads via TUS protocol - Added an option to use a manifest to support the `predefined` sorting method - This file is required for the `predefined` sorting mode with image archives - Fixed file ordering when tasks are created from SDK or CLI in the `predefined` sorting mode - Added more tests for task data uploading API The uploading protocol is implemented: The user specifies `sorting_method=predefined` if the task creation request. Then the data is uploaded. 1. Client files uploading 1.1. The files are uploaded as separate files (using the TUS protocol) or grouped files (using the `Upload-Multiple` requests). 1.2. The `Upload-Finish` request comes (or its unlabeled legacy equivalent). The new optional field can be supplied: `upload_file_order` - a list of strings. It allows to override the input file order, if necessary, and is only valid with the `predefined` sorting method specified. 1.2.1. If the field is empty or missing, the client files in the data requests are considered ordered. 1.2.2. If the field is not empty, a list containing the file list in the required order is expected in the `upload_file_order` field. 1.2.2.1. If there are `client_files` in the request, the files are sorted 1.2.2.2. If file lists mismatch, an explanatory error is raised. 2. Data processing 2.1. At this point, all `*_files` are considered ordered as requested. 2.2. Require a metafile for zip uploads with predefined sorting. The file is expected to accompany the uploaded zip file, not to be inside of the archive. 2.3. If there is a metafile in the input data, files are ordered after the metafile. 2.3.1. If the data is extracted from cloud, only the specified subset of the files is kept in the manifest. 2.3.2. If the upload data doesn't exist in the metafile, an error is raised. 2.3.3. A `job_file_mapping` has higher priority than metafile, if specified. Co-authored-by: Roman Donchenko <roman@cvat.ai> 08 June 2023, 12:32:14 UTC
04a1f0b Andrey Zhavoronkov 05 June 2023, 10:44:00 UTC Added logs for chunk cache (#6209) 05 June 2023, 10:44:00 UTC
20f65e5 Anastasia Yasakova 04 June 2023, 07:44:38 UTC Fix nightly build (#6225) 04 June 2023, 07:44:38 UTC
75acfc5 Andrey Zhavoronkov 04 June 2023, 07:43:57 UTC Fix analytics tests (#6231) 04 June 2023, 07:43:57 UTC
520d219 Andrey Zhavoronkov 02 June 2023, 15:40:28 UTC Updated CHANGELOG for v2.5.0 (#6234) 02 June 2023, 15:40:28 UTC
0900b52 Andrey Zhavoronkov 02 June 2023, 15:28:28 UTC Release v2.4.5 (#6233) ## \[2.4.5] - 2023-06-02 ### Added - Integrated support for sharepoint and cloud storage files, along with directories to be omitted during task creation (server) (<https://github.com/opencv/cvat/pull/6074>) - Enabled task creation with directories from cloud storage or sharepoint (<https://github.com/opencv/cvat/pull/6074>) - Enhanced task creation to support any data type supported by the server by default, from cloud storage without the necessity for the `use_cache` option (<https://github.com/opencv/cvat/pull/6074>) - Added capability for task creation with data from cloud storage without the `use_cache` option (<https://github.com/opencv/cvat/pull/6074>) ### Changed - User can now access resource links from any organization or sandbox, granted it's available to them (<https://github.com/opencv/cvat/pull/5892>) - Cloud storage manifest files have been made optional (<https://github.com/opencv/cvat/pull/6074>) - Updated Django to the 4.2.x version (<https://github.com/opencv/cvat/pull/6122>) - Renamed certain Nuclio functions to adhere to a common naming convention. For instance, `onnx-yolov7` -> `onnx-wongkinyiu-yolov7`, `ultralytics-yolov5` -> `pth-ultralytics-yolov5` (<https://github.com/opencv/cvat/pull/6140>) ### Deprecated - Deprecated the endpoint `/cloudstorages/{id}/content` (<https://github.com/opencv/cvat/pull/6074>) ### Fixed - Fixed the issue of skeletons dumping on created tasks/projects (<https://github.com/opencv/cvat/pull/6157>) - Resolved an issue related to saving annotations for skeleton tracks (<https://github.com/opencv/cvat/pull/6075>) --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru> Co-authored-by: Roman Donchenko <roman@cvat.ai> Co-authored-by: Maria Khrustaleva <maya17grd@gmail.com> Co-authored-by: Boris Sekachev <sekachev.bs@gmail.com> Co-authored-by: Nikita Manovich <nikita@cvat.ai> Co-authored-by: Anastasia Yasakova <yasakova_anastasiya@mail.ru> Co-authored-by: Snyk bot <snyk-bot@snyk.io> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Kirill Sizov <kirill.sizov@cvat.ai> Co-authored-by: Paweł Kotiuk <kotiuk@zohomail.eu> Co-authored-by: SK <450723+senthilkumarkj@users.noreply.github.com> Co-authored-by: Kirill Lakhov <kirill.9992@gmail.com> 02 June 2023, 15:28:28 UTC
679fcad Mariia Acoca 02 June 2023, 10:27:38 UTC Release notes updated (#6232) 02 June 2023, 10:27:38 UTC
85ffdd2 Maxim Zhiltsov 02 June 2023, 09:10:31 UTC Improve container debugging experience (#6211) - Fixed `django.db.utils.operationalerror: server closed the connection unexpectedly` errors during debugging rq workers 02 June 2023, 09:10:31 UTC
a76428f Snyk bot 02 June 2023, 09:01:31 UTC [Snyk] Security upgrade cryptography from 40.0.2 to 41.0.0 (#6227) <h3>Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.</h3> #### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - cvat/requirements/base.txt <details> <summary>⚠️ <b>Warning</b></summary> ``` tensorboard 2.11.2 requires werkzeug, which is not installed. ``` </details> #### Vulnerabilities that will be fixed ##### By pinning: Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png "medium severity") | **581/1000** <br/> **Why?** Recently disclosed, Has a fix available, CVSS 5.9 | Denial of Service (DoS) <br/>[SNYK-PYTHON-CRYPTOGRAPHY-5663682](https://snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-5663682) | `cryptography:` <br> `40.0.2 -> 41.0.0` <br> | No | No Known Exploit (*) Note that the real score may have changed since the PR was raised. Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded. Check the changes in this PR to ensure they won't cause issues with your project. ------------ **Note:** *You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.* For more information: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiI3NzQ2NTYwNC0wZDQ5LTQwODUtOTlhYi0yNjVmN2NmNmNjMzciLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6Ijc3NDY1NjA0LTBkNDktNDA4NS05OWFiLTI2NWY3Y2Y2Y2MzNyJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source&#x3D;github&amp;utm_medium&#x3D;referral&amp;page&#x3D;fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/cvat/project/4bbc4b80-3fb9-4009-a7bb-51016d44946b?utm_source&#x3D;github&amp;utm_medium&#x3D;referral&amp;page&#x3D;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":"77465604-0d49-4085-99ab-265f7cf6cc37","prPublicId":"77465604-0d49-4085-99ab-265f7cf6cc37","dependencies":[{"name":"cryptography","from":"40.0.2","to":"41.0.0"}],"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-CRYPTOGRAPHY-5663682"],"upgrade":[],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","pr-warning-shown","priorityScore"],"priorityScoreList":[581],"remediationStrategy":"vuln"}) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Denial of Service (DoS)](https://learn.snyk.io/lessons/redos/javascript/?loc&#x3D;fix-pr) 02 June 2023, 09:01:31 UTC
f7fd06c Maria Khrustaleva 02 June 2023, 08:54:07 UTC Fixed resources import (#5909) Fixed: - wrong location of tmp file when importing job annotations - ```Traceback (most recent call last): File "/home/maya/Documents/cvat/.env/lib/python3.8/site-packages/rq/worker.py", line 795, in work self.execute_job(job, queue) File "/home/maya/Documents/cvat/cvat/rqworker.py", line 37, in execute_job return self.perform_job(*args, **kwargs) File "/home/maya/Documents/cvat/.env/lib/python3.8/site-packages/rq/worker.py", line 1389, in perform_job self.handle_exception(job, *exc_info) File "/home/maya/Documents/cvat/.env/lib/python3.8/site-packages/rq/worker.py", line 1438, in handle_exception fallthrough = handler(job, *exc_info) File "/home/maya/Documents/cvat/cvat/apps/engine/views.py", line 2233, in rq_exception_handler rq_job.exc_info = "".join( AttributeError: can't set attribute ``` Resolves https://github.com/opencv/cvat/issues/5773 Resolves https://github.com/opencv/cvat/issues/5563 - root causes of the issues: - the annotation file was uploaded to the server by tus protocol and rq job was created but no one next requests for checking status were not made. (e.g. user closed the browser tab) - the annotation file was uploaded to the server by tus protocol but rq job has not yet been created (e.g cvat instance restarted) - tasks/projects creation from backups with the same name at the same time by different users Co-authored-by: Roman Donchenko <roman@cvat.ai> Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> 02 June 2023, 08:54:07 UTC
2584b96 Kirill Sizov 31 May 2023, 18:38:47 UTC Fix comments for PR 5892 (#6206) ### Motivation and context Applied comments: - [x] Aligning ORGANIZATION_OPEN_API_PARAMETERS https://github.com/opencv/cvat/pull/5892#discussion_r1207319660 - [x] Moving ORGANIZATION_OPEN_API_PARAMETERS https://github.com/opencv/cvat/pull/5892#discussion_r1207320699 ~~- [ ] Moving CustomerAutoSchema https://github.com/opencv/cvat/pull/5892#discussion_r1207326857~~ this uncritical comment that cannot be done easily, [see answer](https://github.com/opencv/cvat/pull/5892#discussion_r1209015397) - [x] Raise error if cannot get `organization_id` for objects https://github.com/opencv/cvat/pull/5892#discussion_r1207365213 - [x] Multiply fields for `iam_organization_field` https://github.com/opencv/cvat/pull/5892#issuecomment-1566841192 Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> 31 May 2023, 18:38:47 UTC
21503b3 Mariia Acoca 31 May 2023, 18:28:59 UTC analytics documentation updated (#6205) 31 May 2023, 18:28:59 UTC
87dd7ff Andrey Zhavoronkov 30 May 2023, 12:24:58 UTC Switch to uvicorn (#6195) 30 May 2023, 12:24:58 UTC
ed3dbe8 Kirill Lakhov 26 May 2023, 19:01:38 UTC Open resource links from any organization/sandbox (#5892) 26 May 2023, 19:01:38 UTC
23e5998 SK 26 May 2023, 18:53:30 UTC Add annotations to frontend helm template. (#6163) This is similar to annotations in backend template at https://github.com/tidaltech/cvat/blob/develop/helm-chart/templates/cvat_backend/service.yml#L10-L13 26 May 2023, 18:53:30 UTC
9b38f3e Kirill Sizov 26 May 2023, 12:00:37 UTC Fix skeleton tracks (#6075) Currently, we don't have validation of incoming annotations, as a result, there is exist some cases when annotations successfully saved in DB, but it's impossible to export them. In order to successfully export a dataset with a skeleton track it's required that each track satisfy the following condition: ` {frame number of track} == {frame number of parent track} == {frame number of the first shape of the track}` This PR adds an additional step during saving annotation in DB. This additional step check that all these there "frame numbers" are equal and try to automatically fix it's not true. 26 May 2023, 12:00:37 UTC
a5cbd1a Roman Donchenko 26 May 2023, 11:22:46 UTC Make serverless function naming and Docker image naming consistent (#6140) For function names, take the relative path, lowercase, join with dashes and replace underscores with dashes. For image names, take the relative path, lowercase and join with dots. In a couple cases, rename the function directory instead of fixing the config. 26 May 2023, 11:22:46 UTC
36d8913 Paweł Kotiuk 26 May 2023, 11:18:53 UTC Update traefik version used in HTTPS config (#6164) Just to match version used in docker-compose.yml I just think Someone forgot about updating it when version from docker-compose.yml was updated ( https://github.com/opencv/cvat/commit/980c019427422e4a13e9f5b3c7c20de3264513cb ) 26 May 2023, 11:18:53 UTC
37d24e4 Kirill Sizov 25 May 2023, 15:47:16 UTC Fix linters (#6199) 25 May 2023, 15:47:16 UTC
6d7050d Kirill Sizov 25 May 2023, 12:18:03 UTC Use new github action for getting changed files (#6114) <!-- 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 [Github Action that we use for getting changed files is deprecated](https://github.com/jitterbit/get-changed-files), as a result, we receive warning messages in our linter workflows (e.g. [1](https://github.com/opencv/cvat/actions/runs/4906955272), [2](https://github.com/opencv/cvat/actions/runs/4894049447), [3](https://github.com/opencv/cvat/actions/runs/4890905271)). This workflow rid of these warnings by using another Github Action for getting changed files. If do not do this our linter workflows will stop working this summer [link1](https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/) [link2](https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/) ### 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. 25 May 2023, 12:18:03 UTC
f93cbba dependabot[bot] 25 May 2023, 12:16:45 UTC Bump requests from 2.26.0 to 2.31.0 in /tests/python (#6184) Bumps [requests](https://github.com/psf/requests) from 2.26.0 to 2.31.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/psf/requests/releases">requests's releases</a>.</em></p> <blockquote> <h2>v2.31.0</h2> <h2>2.31.0 (2023-05-22)</h2> <p><strong>Security</strong></p> <ul> <li> <p>Versions of Requests between v2.3.0 and v2.30.0 are vulnerable to potential forwarding of <code>Proxy-Authorization</code> headers to destination servers when following HTTPS redirects.</p> <p>When proxies are defined with user info (<a href="https://user:pass@proxy:8080">https://user:pass@proxy:8080</a>), Requests will construct a <code>Proxy-Authorization</code> header that is attached to the request to authenticate with the proxy.</p> <p>In cases where Requests receives a redirect response, it previously reattached the <code>Proxy-Authorization</code> header incorrectly, resulting in the value being sent through the tunneled connection to the destination server. Users who rely on defining their proxy credentials in the URL are <em>strongly</em> encouraged to upgrade to Requests 2.31.0+ to prevent unintentional leakage and rotate their proxy credentials once the change has been fully deployed.</p> <p>Users who do not use a proxy or do not supply their proxy credentials through the user information portion of their proxy URL are not subject to this vulnerability.</p> <p>Full details can be read in our <a href="https://github.com/psf/requests/security/advisories/GHSA-j8r2-6x86-q33q">Github Security Advisory</a> and <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-32681">CVE-2023-32681</a>.</p> </li> </ul> <h2>v2.30.0</h2> <h2>2.30.0 (2023-05-03)</h2> <p><strong>Dependencies</strong></p> <ul> <li> <p>⚠️ Added support for urllib3 2.0. ⚠️</p> <p>This may contain minor breaking changes so we advise careful testing and reviewing <a href="https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html">https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html</a> prior to upgrading.</p> <p>Users who wish to stay on urllib3 1.x can pin to <code>urllib3&lt;2</code>.</p> </li> </ul> <h2>v2.29.0</h2> <h2>2.29.0 (2023-04-26)</h2> <p><strong>Improvements</strong></p> <ul> <li>Requests now defers chunked requests to the urllib3 implementation to improve standardization. (<a href="https://redirect.github.com/psf/requests/issues/6226">#6226</a>)</li> <li>Requests relaxes header component requirements to support bytes/str subclasses. (<a href="https://redirect.github.com/psf/requests/issues/6356">#6356</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/psf/requests/blob/main/HISTORY.md">requests's changelog</a>.</em></p> <blockquote> <h2>2.31.0 (2023-05-22)</h2> <p><strong>Security</strong></p> <ul> <li> <p>Versions of Requests between v2.3.0 and v2.30.0 are vulnerable to potential forwarding of <code>Proxy-Authorization</code> headers to destination servers when following HTTPS redirects.</p> <p>When proxies are defined with user info (<a href="https://user:pass@proxy:8080">https://user:pass@proxy:8080</a>), Requests will construct a <code>Proxy-Authorization</code> header that is attached to the request to authenticate with the proxy.</p> <p>In cases where Requests receives a redirect response, it previously reattached the <code>Proxy-Authorization</code> header incorrectly, resulting in the value being sent through the tunneled connection to the destination server. Users who rely on defining their proxy credentials in the URL are <em>strongly</em> encouraged to upgrade to Requests 2.31.0+ to prevent unintentional leakage and rotate their proxy credentials once the change has been fully deployed.</p> <p>Users who do not use a proxy or do not supply their proxy credentials through the user information portion of their proxy URL are not subject to this vulnerability.</p> <p>Full details can be read in our <a href="https://github.com/psf/requests/security/advisories/GHSA-j8r2-6x86-q33q">Github Security Advisory</a> and <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-32681">CVE-2023-32681</a>.</p> </li> </ul> <h2>2.30.0 (2023-05-03)</h2> <p><strong>Dependencies</strong></p> <ul> <li> <p>⚠️ Added support for urllib3 2.0. ⚠️</p> <p>This may contain minor breaking changes so we advise careful testing and reviewing <a href="https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html">https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html</a> prior to upgrading.</p> <p>Users who wish to stay on urllib3 1.x can pin to <code>urllib3&lt;2</code>.</p> </li> </ul> <h2>2.29.0 (2023-04-26)</h2> <p><strong>Improvements</strong></p> <ul> <li>Requests now defers chunked requests to the urllib3 implementation to improve standardization. (<a href="https://redirect.github.com/psf/requests/issues/6226">#6226</a>)</li> <li>Requests relaxes header component requirements to support bytes/str subclasses. (<a href="https://redirect.github.com/psf/requests/issues/6356">#6356</a>)</li> </ul> <h2>2.28.2 (2023-01-12)</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/psf/requests/commit/147c8511ddbfa5e8f71bbf5c18ede0c4ceb3bba4"><code>147c851</code></a> v2.31.0</li> <li><a href="https://github.com/psf/requests/commit/74ea7cf7a6a27a4eeb2ae24e162bcc942a6706d5"><code>74ea7cf</code></a> Merge pull request from GHSA-j8r2-6x86-q33q</li> <li><a href="https://github.com/psf/requests/commit/302225334678490ec66b3614a9dddb8a02c5f4fe"><code>3022253</code></a> test on pypy 3.8 and pypy 3.9 on windows and macos (<a href="https://redirect.github.com/psf/requests/issues/6424">#6424</a>)</li> <li><a href="https://github.com/psf/requests/commit/b639e66c816514e40604d46f0088fbceec1a5149"><code>b639e66</code></a> test on py3.12 (<a href="https://redirect.github.com/psf/requests/issues/6448">#6448</a>)</li> <li><a href="https://github.com/psf/requests/commit/d3d504436ef0c2ac7ec8af13738b04dcc8c694be"><code>d3d5044</code></a> Fixed a small typo (<a href="https://redirect.github.com/psf/requests/issues/6452">#6452</a>)</li> <li><a href="https://github.com/psf/requests/commit/2ad18e0e10e7d7ecd5384c378f25ec8821a10a29"><code>2ad18e0</code></a> v2.30.0</li> <li><a href="https://github.com/psf/requests/commit/f2629e9e3c7ce3c3c8c025bcd8db551101cbc773"><code>f2629e9</code></a> Remove strict parameter (<a href="https://redirect.github.com/psf/requests/issues/6434">#6434</a>)</li> <li><a href="https://github.com/psf/requests/commit/87d63de8739263bbe17034fba2285c79780da7e8"><code>87d63de</code></a> v2.29.0</li> <li><a href="https://github.com/psf/requests/commit/51716c4ef390136b0d4b800ec7665dd5503e64fc"><code>51716c4</code></a> enable the warnings plugin (<a href="https://redirect.github.com/psf/requests/issues/6416">#6416</a>)</li> <li><a href="https://github.com/psf/requests/commit/a7da1ab3498b10ec3a3582244c94b2845f8a8e71"><code>a7da1ab</code></a> try on ubuntu 22.04 (<a href="https://redirect.github.com/psf/requests/issues/6418">#6418</a>)</li> <li>Additional commits viewable in <a href="https://github.com/psf/requests/compare/v2.26.0...v2.31.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=requests&package-manager=pip&previous-version=2.26.0&new-version=2.31.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/opencv/cvat/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 25 May 2023, 12:16:45 UTC
0a5bad7 Snyk bot 25 May 2023, 12:15:28 UTC [Snyk] Security upgrade pillow from 9.3.0 to 9.4.0 (#6092) <h3>Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.</h3> #### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - utils/dicom_converter/requirements.txt #### Vulnerabilities that will be fixed ##### By pinning: Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png "medium severity") | **561/1000** <br/> **Why?** Recently disclosed, Has a fix available, CVSS 5.5 | Denial of Service (DoS) <br/>[SNYK-PYTHON-PILLOW-5489784](https://snyk.io/vuln/SNYK-PYTHON-PILLOW-5489784) | `pillow:` <br> `9.3.0 -> 9.4.0` <br> | No | No Known Exploit (*) Note that the real score may have changed since the PR was raised. Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded. Check the changes in this PR to ensure they won't cause issues with your project. ------------ **Note:** *You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.* For more information: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiJjM2I0Yjk2Zi1hM2FlLTQzNDctYjAxNS0wMjZkNWI4ZTkwZTMiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6ImMzYjRiOTZmLWEzYWUtNDM0Ny1iMDE1LTAyNmQ1YjhlOTBlMyJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/cvat/project/a64d2f26-c553-4cc8-a452-1ec1b5a48355?utm_source&#x3D;github&amp;utm_medium&#x3D;referral&amp;page&#x3D;fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/cvat/project/a64d2f26-c553-4cc8-a452-1ec1b5a48355?utm_source&#x3D;github&amp;utm_medium&#x3D;referral&amp;page&#x3D;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":"c3b4b96f-a3ae-4347-b015-026d5b8e90e3","prPublicId":"c3b4b96f-a3ae-4347-b015-026d5b8e90e3","dependencies":[{"name":"pillow","from":"9.3.0","to":"9.4.0"}],"packageManager":"pip","projectPublicId":"a64d2f26-c553-4cc8-a452-1ec1b5a48355","projectUrl":"https://app.snyk.io/org/cvat/project/a64d2f26-c553-4cc8-a452-1ec1b5a48355?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-PYTHON-PILLOW-5489784"],"upgrade":[],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","priorityScore"],"priorityScoreList":[561],"remediationStrategy":"vuln"}) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Denial of Service (DoS)](https://learn.snyk.io/lessons/redos/javascript/?loc&#x3D;fix-pr) 25 May 2023, 12:15:28 UTC
aee9fff Boris Sekachev 24 May 2023, 12:35:34 UTC Adjusted documentation to shared storage mounting (#6193) <!-- 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 #5887 Resolved #6017 ### 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. 24 May 2023, 12:35:34 UTC
cfe2ea3 Andrey Zhavoronkov 22 May 2023, 10:14:14 UTC Update Django to 4.x (#6122) - Reduced rest_api testing time by ~25% in my environment: 430s vs 560s - Enabled gzip compression - Fixed webhook tests that not actually waiting for the required number of delivered messages in response. - Fixed `preview` tests 22 May 2023, 10:14:14 UTC
0a092f9 Andrey Zhavoronkov 22 May 2023, 10:10:15 UTC Bump SDK and CLI versions (#6170) 22 May 2023, 10:10:15 UTC
9c8b8b2 Anastasia Yasakova 22 May 2023, 09:14:33 UTC Fix development environment documentation (#6099) <!-- 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. --> Updated development environment documentation (fixed links, moved some steps) ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [x] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 22 May 2023, 09:14:33 UTC
df31dc7 Maria Khrustaleva 20 May 2023, 08:46:25 UTC Improve task creation with cloud storage and share data (#6074) ### Motivation and context Resolved #6037 Related https://github.com/opencv/cvat/issues/4400 Related https://github.com/opencv/cvat/issues/6028 ![image](https://user-images.githubusercontent.com/49038720/236890662-c44b578e-5808-4fde-a216-2dcab6e95ab0.png) Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru> Co-authored-by: Boris Sekachev <sekachev.bs@gmail.com> Co-authored-by: Roman Donchenko <roman@cvat.ai> Co-authored-by: Nikita Manovich <nikita@cvat.ai> 20 May 2023, 08:46:25 UTC
692b16c Roman Donchenko 19 May 2023, 19:48:56 UTC pth-facebookresearch-sam-vit-h: add NVIDIA environment variables to the GPU image (#6171) Without these variables, the container cannot actually use CUDA. At least that was my experience on AWS; it's possible that in other configurations the defaults are different. See <https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/user-guide.html>. 19 May 2023, 19:48:56 UTC
8ad485b Boris Sekachev 19 May 2023, 07:53:17 UTC Fixed skeleton dumping (#6157) <!-- 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 #5706 Resolved #6022 ### 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. 19 May 2023, 07:53:17 UTC
960e614 Andrey Zhavoronkov 18 May 2023, 18:51:11 UTC Bump version for next release v2.5.0 (#6168) 18 May 2023, 18:51:11 UTC
d5ef45a Nikita Manovich 18 May 2023, 18:40:40 UTC Release v2.4.4 ### Added - Introduced a new configuration option for controlling the invocation of Nuclio functions. (<https://github.com/opencv/cvat/pull/6146>) ### Changed - Relocated SAM masks decoder to frontend operation. (<https://github.com/opencv/cvat/pull/6019>) - Switched `person-reidentification-retail-0300` and `faster_rcnn_inception_v2_coco` Nuclio functions with `person-reidentification-retail-0277` and `faster_rcnn_inception_resnet_v2_atrous_coco` respectively. (<https://github.com/opencv/cvat/pull/6129>) - Upgraded OpenVINO-based Nuclio functions to utilize the OpenVINO 2022.3 runtime. (<https://github.com/opencv/cvat/pull/6129>) ### Fixed - Resolved issues with tracking multiple objects (30 and more) using the TransT tracker. (<https://github.com/opencv/cvat/pull/6073>) - Addressed azure.core.exceptions.ResourceExistsError: The specified blob already exists. (<https://github.com/opencv/cvat/pull/6082>) - Corrected image scaling issues when transitioning between images of different resolutions. (<https://github.com/opencv/cvat/pull/6081>) - Fixed inaccurate reporting of completed job counts. (<https://github.com/opencv/cvat/issues/6098>) - Allowed OpenVINO-based Nuclio functions to be deployed to Kubernetes. (<https://github.com/opencv/cvat/pull/6129>) - Improved skeleton size checks after drawing. (<https://github.com/opencv/cvat/pull/6156>) - Fixed HRNet CPU serverless function. (<https://github.com/opencv/cvat/pull/6150>) - Prevented sending of empty list of events. (<https://github.com/opencv/cvat/pull/6154>) 18 May 2023, 18:40:40 UTC
fa4a200 Andrey Zhavoronkov 18 May 2023, 14:26:19 UTC Merge remote-tracking branch 'origin/master' into release-2.4.4 18 May 2023, 14:26:19 UTC
617dc40 Andrey Zhavoronkov 18 May 2023, 14:22:04 UTC update version in CHANGELOG.md 18 May 2023, 14:22:04 UTC
0805a6d Andrey Zhavoronkov 18 May 2023, 13:56:56 UTC update version 18 May 2023, 14:20:02 UTC
7e619b2 Mariia Acoca 18 May 2023, 14:18:58 UTC Changelog update (#6165) 18 May 2023, 14:18:58 UTC
8ae3ac3 Andrey Zhavoronkov 18 May 2023, 10:05:02 UTC Enable gzip compression for UI assets (#6162) <!-- 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. --> before: ![f_gzip_before](https://github.com/opencv/cvat/assets/41117609/a6ed0fd5-26d7-469d-904a-b310cd493b14) after: ![f_gzip_after](https://github.com/opencv/cvat/assets/41117609/3487a5c5-fb96-4eeb-acad-d2209e05721b) ### 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. 18 May 2023, 10:05:02 UTC
7141f3b Andrey Zhavoronkov 16 May 2023, 17:59:12 UTC Revert "Fix version of postgres image (#6136)" (#6151) This reverts commit 2754504bb291a96b0f7c42783bbbff006a2f47d4. <!-- 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. --> Resolved in https://github.com/docker-library/postgres/issues/1076 ### 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. Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> 16 May 2023, 17:59:12 UTC
6a374b4 Boris Sekachev 16 May 2023, 17:31:06 UTC Fixed area checking for skeleton in case with two points (#6156) <!-- 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. 16 May 2023, 17:31:06 UTC
4eb333e Andrey Zhavoronkov 16 May 2023, 11:10:17 UTC Fix array length check condition (#6154) <!-- 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. 16 May 2023, 11:10:17 UTC
fe78da2 Maria Khrustaleva 15 May 2023, 14:52:19 UTC Update license header for new files (#6152) <!-- 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. 15 May 2023, 14:52:19 UTC
7d21a73 Roman Donchenko 15 May 2023, 14:48:26 UTC Add an option to call Nuclio functions via the dashboard (#6146) Currently, this only happens when running in Kubernetes. This option lets CVAT use Nuclio that's deployed to Kubernetes without being deployed to Kubernetes itself, or just to use Nuclio that is deployed on another machine. 15 May 2023, 14:48:26 UTC
c005d6c Roman Donchenko 15 May 2023, 14:17:54 UTC Fix the CPU HRNet Nuclio function (#6150) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> It was broken for two reasons: * Due to some changes on the PyTorch website, the old way of installing the PyTorch packages now installs the ROCm version rather than the CPU version (and it doesn't work doe to a missing dependency). * The newest version of NumPy doesn't work with HRNet due to the latter's usage of `np.int`. Fix these problems, and in addition, rework the build recipe to avoid installing unneeded packages. Altogether, the changes massively shrink the Docker image size (from ~14 GB to ~2 GB). I didn't update the GPU version, because a) the first issue doesn't affect it, b) the second issue is already fixed in it, and c) I don't have a GPU to test it on. ### 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 with CVAT. ### 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: Boris Sekachev <boris.sekachev@yandex.ru> 15 May 2023, 14:17:54 UTC
98616c7 Roman Donchenko 15 May 2023, 10:17:03 UTC Modernize OpenVINO-based Nuclio functions and allow them to run on Kubernetes (#6129) Currently, OpenVINO-based functions assume that a local directory will be mounted into the container. In Kubernetes, that isn't possible, so implement an alternate approach: create a separate base image and inherit the function image from it. In addition, implement some modernizations: * Upgrade the version of OpenVINO to the latest (2022.3). Make the necessary updates to the code. Note that 2022.1 introduced an entirely new inference API, but I haven't switched to it yet to minimize changes. * Use the runtime version of the Docker image as the base instead of the dev version. This significantly reduces the size of the final image (by ~3GB). * Replace the `faster_rcnn_inception_v2_coco` model with `faster_rcnn_inception_resnet_v2_atrous_coco`, as the former has been removed from OMZ. * Ditto with `person-reidentification-retail-0300` -> `0277`. * The IRs used in the DEXTR function are not supported by OpenVINO anymore (format too old), so rewrite the build process to create them from the original code/weights instead. 15 May 2023, 10:17:03 UTC
2a41d59 Boris Sekachev 12 May 2023, 15:00:08 UTC Correct destructuring plugins array (#6139) <!-- 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 - [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 May 2023, 15:00:08 UTC
2754504 Kirill Sizov 12 May 2023, 13:27:14 UTC Fix version of postgres image (#6136) 12 May 2023, 13:27:14 UTC
0712d7d Boris Sekachev 11 May 2023, 11:05:54 UTC Running SAM backbone on frontend (#6019) <!-- 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 #5984 Resolved #6049 Resolved #6041 - Compatible only with ``sam_vit_h_4b8939.pth`` weights. Need to re-export ONNX mask decoder with some custom model changes (see below) to support other weights (or just download them using links below) - Need to redeploy the serverless function because its interface has been changed. Decoders for other weights: sam_vit_l_0b3195.pth: [Download](https://drive.google.com/file/d/1Nb5CJKQm_6s1n3xLSZYso6VNgljjfR-6/view?usp=sharing) sam_vit_b_01ec64.pth: [Download](https://drive.google.com/file/d/17cZAXBPaOABS170c9bcj9PdQsMziiBHw/view?usp=sharing) Changes done in ONNX part: ``` git diff scripts/export_onnx_model.py diff --git a/scripts/export_onnx_model.py b/scripts/export_onnx_model.py index 8441258..18d5be7 100644 --- a/scripts/export_onnx_model.py +++ b/scripts/export_onnx_model.py @@ -138,7 +138,7 @@ def run_export( _ = onnx_model(**dummy_inputs) - output_names = ["masks", "iou_predictions", "low_res_masks"] + output_names = ["masks", "iou_predictions", "low_res_masks", "xtl", "ytl", "xbr", "ybr"] with warnings.catch_warnings(): warnings.filterwarnings("ignore", category=torch.jit.TracerWarning) bsekachev@DESKTOP-OTBLK26:~/sam$ git diff segment_anything/utils/onnx.py diff --git a/segment_anything/utils/onnx.py b/segment_anything/utils/onnx.py index 3196bdf..85729c1 100644 --- a/segment_anything/utils/onnx.py +++ b/segment_anything/utils/onnx.py @@ -87,7 +87,15 @@ class SamOnnxModel(nn.Module): orig_im_size = orig_im_size.to(torch.int64) h, w = orig_im_size[0], orig_im_size[1] masks = F.interpolate(masks, size=(h, w), mode="bilinear", align_corners=False) - return masks + masks = torch.gt(masks, 0).to(torch.uint8) + nonzero = torch.nonzero(masks) + xindices = nonzero[:, 3:4] + yindices = nonzero[:, 2:3] + ytl = torch.min(yindices).to(torch.int64) + ybr = torch.max(yindices).to(torch.int64) + xtl = torch.min(xindices).to(torch.int64) + xbr = torch.max(xindices).to(torch.int64) + return masks[:, :, ytl:ybr + 1, xtl:xbr + 1], xtl, ytl, xbr, ybr def select_masks( self, masks: torch.Tensor, iou_preds: torch.Tensor, num_points: int @@ -132,7 +140,7 @@ class SamOnnxModel(nn.Module): if self.return_single_mask: masks, scores = self.select_masks(masks, scores, point_coords.shape[1]) - upscaled_masks = self.mask_postprocessing(masks, orig_im_size) + upscaled_masks, xtl, ytl, xbr, ybr = self.mask_postprocessing(masks, orig_im_size) if self.return_extra_metrics: stability_scores = calculate_stability_score( @@ -141,4 +149,4 @@ class SamOnnxModel(nn.Module): areas = (upscaled_masks > self.model.mask_threshold).sum(-1).sum(-1) return upscaled_masks, scores, stability_scores, areas, masks - return upscaled_masks, scores, masks + return upscaled_masks, scores, masks, xtl, ytl, xbr, ybr ``` ### 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. 11 May 2023, 11:05:54 UTC
df72796 Mariia Acoca 10 May 2023, 13:35:46 UTC Subscription management (#6086) 10 May 2023, 13:35:46 UTC
a490632 Boris Sekachev 10 May 2023, 13:25:11 UTC Fixed headers on prod (#6123) 10 May 2023, 13:25:11 UTC
5f25a09 Andrey Zhavoronkov 09 May 2023, 16:38:29 UTC Increase lambda requests timeout (#6101) 09 May 2023, 16:38:29 UTC
aa25c97 Andrey Zhavoronkov 09 May 2023, 16:37:19 UTC Fix lambda manager requests visibility (#6116) 09 May 2023, 16:37:19 UTC
546bd40 Boris Sekachev 09 May 2023, 09:39:06 UTC Added test for fit issue (#6117) <!-- 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 Before/after fix execution: ![image](https://user-images.githubusercontent.com/40690378/236913420-6165e7aa-8758-4efd-be8b-825304e92c19.png) ![image](https://user-images.githubusercontent.com/40690378/236913439-862d60a7-1d90-463f-8129-acb5f2727eb9.png) ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] 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. 09 May 2023, 09:39:06 UTC
255f2d0 Maxim Zhiltsov 05 May 2023, 13:38:23 UTC Fix completed job count reporting (#6106) - Fixed completed task job count reporting in the task summary - Added a test Fixes #6098 Fixes #6034 05 May 2023, 13:38:23 UTC
8f033b3 Roman Donchenko 05 May 2023, 07:52:47 UTC Ensure that Nuclio function names are valid Kubernetes service names (#6100) 05 May 2023, 07:52:47 UTC
5399f6e Boris Sekachev 01 May 2023, 10:23:52 UTC Fixed fit for images with different resolution (#6081) <!-- 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. 01 May 2023, 10:23:52 UTC
d026dbf Maria Khrustaleva 28 April 2023, 05:43:34 UTC Fix issue azure.core.exceptions.ResourceExistsError: The specified blob already exists. (#6082) 28 April 2023, 05:43:34 UTC
091a035 Andrey Zhavoronkov 26 April 2023, 19:24:15 UTC Increase request body size for TransT tracker (#6073) 26 April 2023, 19:24:15 UTC
269545b Andrey Zhavoronkov 25 April 2023, 15:22:17 UTC develop 2.5.0 (#6070) 25 April 2023, 15:22:17 UTC
8a2c23f Nikita Manovich 25 April 2023, 15:20:58 UTC Release v2.4.3 25 April 2023, 15:20:58 UTC
d2ba56d Andrey Zhavoronkov 25 April 2023, 06:40:25 UTC Fix pylint workflow 25 April 2023, 06:40:25 UTC
da0466d Andrey Zhavoronkov 24 April 2023, 17:47:20 UTC Merge remote-tracking branch 'origin/master' into release-2.4.3 24 April 2023, 17:47:20 UTC
eb15937 Andrey Zhavoronkov 24 April 2023, 17:40:15 UTC Update CHANGELOG.md 24 April 2023, 17:40:15 UTC
8fa0956 Andrey Zhavoronkov 24 April 2023, 17:37:11 UTC Update version 24 April 2023, 17:37:54 UTC
d3d5f9b Andrey Zhavoronkov 24 April 2023, 16:48:45 UTC Set default TUS chunk size from 100 to 2 MB (#6058) 24 April 2023, 16:48:45 UTC
c657c82 Roman Donchenko 21 April 2023, 12:03:11 UTC Dockerfile: build PyAV and its dependencies in a separate stage (#6054) This way, it can be done in parallel with pip fetching all other packages in the main build stage. In practice, I find that the build of PyAV finishes before pip is done downloading, so we basically get it done for free (in terms of time). With this change, I measured a build time of 9:09 (starting from scratch). 21 April 2023, 12:03:11 UTC
157f7e3 Roman Donchenko 20 April 2023, 11:27:02 UTC Implement Python dependency pinning via pip-compile-multi (#6048) This improves the reproducibility of the server build process. Now new versions of dependencies can no longer break the server unless we explicitly upgrade to them. To minimize changes, I did not update any of the version constraints we currently have; however, in the future, we should be able to relax a lot of them. Resolves #5310. 20 April 2023, 11:27:02 UTC
a353497 Roman Donchenko 19 April 2023, 08:40:50 UTC Stop adding package source code into the release Docker images (#6040) The policy that mandated this is no longer relevant now that CVAT is no longer developed by Intel. Moreover, the source code included was not even complete (it didn't contain Python or NPM packages). This saves ~1.6 GB in the unpacked image (and probably a bunch of build time too, but I didn't measure it). 19 April 2023, 08:40:50 UTC
b8cdd4e Roman Donchenko 18 April 2023, 18:35:56 UTC Update Redis and Redis accessories (#6016) This originally started as a security update for redis-py (see <https://github.com/redis/redis-py/releases/tag/v4.5.3>, <https://github.com/redis/redis-py/releases/tag/v4.5.4>). However, I also had to update other Redis-related components because of incompatibilities. * The old version of fakeredis is not compatible with the redis-py 4.x, so I bumped it too. This also allowed me to remove the six workaround. * redis-py 4.1.0 and newer don't support Redis < 5, so I bumped Redis itself in `docker-compose.yml`. Note that the Helm chart is already using Redis 7.0.x. Obsoletes #5946. 18 April 2023, 18:35:56 UTC
65d43aa Roman Donchenko 18 April 2023, 18:31:29 UTC Dockerfile: retain the pip download cache between builds (#6035) This speeds up the build when the entire step can't be cached (e.g. the requirements file changed), but the package list remains mostly the same. The savings are... rather underwhelming, actually. I have observed about a minute in savings, although it obviously depends on the network connection speed. I think this is because pip is inefficient at loading from its own cache (I have observed it loading the entire cached file into memory, for example). Still, savings are savings, and we're getting them basically for free, so why not. Note that I only persist the HTTP cache, and not the wheel cache. That's because any wheels that pip builds could depend on the system packages, and I don't want old wheels to be reused if the system packages change. Also, disable the pip autoupdate checks, which isn't much of an optimization, but it gets rid of some pointless warnings. 18 April 2023, 18:31:29 UTC
ad534b2 Maxim Zhiltsov 17 April 2023, 15:26:28 UTC Refactor server api tests and dataset_manifest (#5997) Extracted from #5083 - Fixed test data placement in tests - Fixed cache cleaning in tests - Refactored server API tests and dataset_manifest - Added more tests 17 April 2023, 15:26:28 UTC
31c1ecc Andrey Zhavoronkov 14 April 2023, 15:58:52 UTC Update the changelog for the next version 2.5.0 (#6031) 14 April 2023, 15:58:52 UTC
b4549f4 Nikita Manovich 14 April 2023, 15:56:47 UTC Merge pull request #6030 from opencv/release-2.4.2 Release v2.4.2 14 April 2023, 15:56:47 UTC
a40deb9 Andrey Zhavoronkov 14 April 2023, 14:47:13 UTC update schema version 14 April 2023, 14:47:13 UTC
883bb23 Andrey Zhavoronkov 14 April 2023, 14:36:20 UTC update schema version 14 April 2023, 14:36:20 UTC
de704ff Andrey Zhavoronkov 14 April 2023, 14:12:11 UTC Update vesrion 14 April 2023, 14:12:11 UTC
d764635 Kirill Sizov 14 April 2023, 13:54:33 UTC Add missing line CHANGELOG.md (#6027) 14 April 2023, 13:54:33 UTC
3717060 Andrey Zhavoronkov 14 April 2023, 13:48:16 UTC Added missed line to changelog (#6029) Update CHANGELOG.md 14 April 2023, 13:48:16 UTC
8a14ce8 Andrey Zhavoronkov 14 April 2023, 13:10:18 UTC Update base imege to ubuntu:22.04 (#6021) Update base image ubuntu 20.04 -> 22.04 update python 3.8 -> 3.10 update sqlite3 from 3.31 -> 3.37 14 April 2023, 13:10:18 UTC
d3bc72b Mariia Acoca 14 April 2023, 13:00:15 UTC Update CHANGELOG.md (#6025) Fix typos in CHANGELOG 14 April 2023, 13:00:15 UTC
dfcb154 Mariia Acoca 14 April 2023, 12:48:30 UTC Update CHANGELOG.md (#6024) Update CHANGELOG.md 14 April 2023, 12:48:30 UTC
1c753d5 Andrey Zhavoronkov 13 April 2023, 12:44:43 UTC Fix tus loading if multiple apache processes are used (#6006) 13 April 2023, 12:44:43 UTC
61adec5 Roman Donchenko 12 April 2023, 12:02:31 UTC Make mild improvements to the main Dockerfile (#5994) This applies several minor improvements that together shave off a little bit of build time (on my machine, it goes down from 14:10 to 13:20) and a little bit of size of the final image (likely just a few megabytes, so I didn't measure it exactly). 12 April 2023, 12:02:31 UTC
10fb2b4 Boris Sekachev 12 April 2023, 09:12:02 UTC Plugins updated in core app (#6000) <!-- 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. 12 April 2023, 09:12:02 UTC
9cbd510 Boris Sekachev 12 April 2023, 08:11:34 UTC Added Segment Anything interactor for GPU/CPU (#6008) Idea of the PR is to finish this one #5990 Deploy for GPU: ``./deploy_gpu.sh pytorch/facebookresearch/sam/nuclio/`` Deploy for CPU: ``./deploy_cpu.sh pytorch/facebookresearch/sam/nuclio/`` If you want to use GPU, be sure you setup docker for this [guide](https://github.com/NVIDIA/nvidia-docker/blob/master/README.md#quickstart). Resolved issue #5984 But the interface probably can be improved Co-authored-by: Alx-Wo <alexander.wolpert@googlemail.com> 12 April 2023, 08:11:34 UTC
6852cae Nikita Manovich 11 April 2023, 20:06:28 UTC Use PostgreSQL in debug mode (#5999) Fix #5996 We have multiple problems with sqlite on different operation systems. The idea here is to use the same DB in debug and in production. sqlite database is locked errors: - https://www2.sqlite.org/cvstrac/wiki?p=DatabaseIsLocked - https://docs.djangoproject.com/en/4.2/ref/databases/#database-is-locked-errors --------- Co-authored-by: kirill-sizov <sizow.k.d@gmail.com> 11 April 2023, 20:06:28 UTC
14dc68e Nikita Manovich 11 April 2023, 05:21:17 UTC Optimized jobs request (#5962) 11 April 2023, 05:21:17 UTC
c5156f4 Kirill Sizov 10 April 2023, 19:07:16 UTC Verifying API schema before running tests (#5998) 10 April 2023, 19:07:16 UTC
2505b31 Roman Donchenko 10 April 2023, 18:26:12 UTC SDK: fix urllib3 deprecation warnings (#6002) `HTTPResponse.getheader` and `getheaders` are slated to be removed in urllib3 2.1.0. 10 April 2023, 18:26:12 UTC
0c853b1 Maxim Zhiltsov 09 April 2023, 05:46:22 UTC Fix version checks in SDK (#5991) - Added missing compatibility with micro- and smaller releases 09 April 2023, 05:46:22 UTC
7a7267d Anastasia Yasakova 07 April 2023, 10:30:27 UTC Update REST API tests documentation (#5993) 07 April 2023, 10:30:27 UTC
7cff867 Kirill Sizov 07 April 2023, 09:20:05 UTC Refactor webhooks (#5916) This PR fixes the following problems: - #5631 - This will allow webhooks to be sent not only when an explicit request has been sent to the server. Co-authored-by: Nikita Manovich <nikita@cvat.ai> Co-authored-by: yasakova-anastasia <anastasia@cvat.ai> Co-authored-by: Roman Donchenko <roman@cvat.ai> 07 April 2023, 09:20:05 UTC
37427bb Nikita Manovich 06 April 2023, 19:00:21 UTC Merge branch 'develop' of https://github.com/opencv/cvat into develop 06 April 2023, 19:00:21 UTC
back to top