https://github.com/opencv/cvat

sort by:
Revision Author Date Message Commit Date
506c96b Fixed opencv runtime initialization (#7101) 06 November 2023, 13:08:45 UTC
5392763 Merge pull request #7098 from opencv/dev-release-2.8.1 Update develop after v2.8.1 06 November 2023, 07:19:02 UTC
7726281 Update develop after v2.8.1 05 November 2023, 08:50:06 UTC
20892ec Prepare release v2.8.1 03 November 2023, 15:58:34 UTC
9819e6d Fixed user email auto verification on accepting organization invitation (#7073) There is a couple of UX bugs in invite user to organization feature. This pr fixes: - Email is auto-verified after accepting invitation - Stuff can view unaccepted invitations - Stuff can edit unaccepted memberships - User email is now used as username 03 November 2023, 15:56:55 UTC
0535d45 Chunk preparation optimization (#7081) This PR speeds up the preparation of chunks by: 1. loading images once instead of twice in each writer, 2. as well as by allowing simultaneous preparation of more than 1 chunk using multithreading. This allows to reduce the time for preparation of chunks for 4895 images from 0:04:36 to 0:01:20 in case of preparation of 3 chunks in parallel and 0:02:46 in case of 1 chunk in my environment. Co-authored-by: Maria Khrustaleva <maya17grd@gmail.com> 02 November 2023, 15:59:39 UTC
1f8d5d3 REST API tests for default bucket prefix (#7079) This PR contains REST API tests for https://github.com/opencv/cvat/pull/6943 02 November 2023, 15:51:22 UTC
d2b5f3d Compress `changeFrame` events (#7048) We have too many event records of `changeFrame` and `zoomImage` events. They are not really informative. This pr compresses `changeFrame` events and increases ignore events timeouts Co-authored-by: Andrey Zhavoronkov <andrey@cvat.ai> 02 November 2023, 15:37:11 UTC
623476e [AWS S3] Use local session (#7067) Try to fix the issue described in cart 322 ``` File \"/opt/venv/lib/python3.10/site-packages/botocore/session.py\", line 941, in get_component\n del self._deferred[name]\nKeyError: 'endpoint_resolver'\n","status_code":500 ``` Generally, this approach increases the time of creating clients but it does not affect us much because we create a client once or twice times for some operations (cloud storage creating, task creating with cloud storage data, retrieving a chunk, etc) ![image](https://github.com/opencv/cvat/assets/49038720/5adb4434-4d05-4882-b70c-ea760852b367) https://boto3.amazonaws.com/v1/documentation/api/latest/guide/resources.html#multithreading-or-multiprocessing-with-resources https://boto3.amazonaws.com/v1/documentation/api/latest/guide/session.html#multithreading-or-multiprocessing-with-sessions Co-authored-by: Andrey Zhavoronkov <andrey@cvat.ai> 02 November 2023, 14:27:23 UTC
e1fe140 [Snyk] Security upgrade urllib3 from 1.26.17 to 1.26.18 (#7027) Co-authored-by: snyk-bot <snyk-bot@snyk.io> 01 November 2023, 11:45:53 UTC
6833b37 Documentation retouch: cloud storages and mot data format (#7071) - Added videos to Cloud Storages - Updated wording in Cloud Storages - Updated data format for MOT Import 31 October 2023, 13:02:29 UTC
ba3db01 Documentation: Need help -> Support (#7070) 30 October 2023, 13:27:02 UTC
43ff5d4 Added error handling if organizations request is failed (#7063) 30 October 2023, 07:39:31 UTC
fc47f58 Add ability to limit one user to one task at a time (#6975) 29 October 2023, 13:21:55 UTC
060fef0 [Snyk] Security upgrade cryptography from 41.0.4 to 41.0.5 (#7068) Co-authored-by: snyk-bot <snyk-bot@snyk.io> 27 October 2023, 09:34:48 UTC
568f0cb setInterval changed to setTimeout when sending events (#7064) 26 October 2023, 12:51:30 UTC
d274c18 Race condition for the task data upload request (#7025) 26 October 2023, 07:14:56 UTC
f2748a6 Add Regal for linting Rego (#7038) Hello CVAT friends! 👋😃 This PR introduces [Regal](https://github.com/styrainc/regal)) for linting the Rego included in this project. The policy code here is generally in a really good shape, so the linter did not have too much to do. Good work on that! Violations of a few rules were fixed as part of this PR, as they do not change the semantics of evaluation: * [line-length](https://docs.styra.com/regal/rules/style/line-length) * [unconditional-assignment](https://docs.styra.com/regal/rules/style/unconditional-assignment) * [use-assignment-operator](https://docs.styra.com/regal/rules/style/use-assignment-operator) A few other ones were ignored using Regal's configuration file. Whether some of them should be fixed in the future I'll leave up to the project's maintainers. I've also added Regal as a build workflow, along with some documentation. Let me know if I missed anything! Signed-off-by: Anders Eknert <anders@styra.com> 26 October 2023, 07:02:43 UTC
e0d1343 Fix inconsistently-named directory (#7054) 26 October 2023, 06:45:37 UTC
08550f8 Support running CVAT with an external database via Docker Compose (#7055) This would help users who don't want or need the complexity of Kubernetes, but would still like to use an external database. With Docker Compose, you can initialize a secret from an environment variable, but you can't load a secret _into_ an environment variable. So in order to be able to read the DB password from a secret, I had to introduce a new `CVAT_POSTGRES_PASSWORD_FILE` variable. 26 October 2023, 06:44:35 UTC
57dffae Bump the docker/login-action version (#7056) v1 of this action produces several deprecation warnings, which should hopefully be fixed in the most recent version. I don't think v2 has any problems, but I might as well bump it. For example: https://github.com/opencv/cvat/actions/runs/6624722303 26 October 2023, 06:40:29 UTC
1b197e4 Remove unneeded steps in the generate_github_pages CI job (#7057) The job spends about a minute downloading and loading the CVAT server image, but I don't think it's used at all. 26 October 2023, 06:39:29 UTC
c19ea38 Fixed: a mask becomes visible even if hidden after changing opacity level (#7060) 25 October 2023, 10:24:32 UTC
c6682ff TrackerMIL optimizations (#7032) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> This PR fixes some problems with TrackerMIL memory managment - Free up some memory after we are done with tracking - Stable memory consuption while tracking (no endlessly raising heap size) Open a task with quite large images 2k -> create a couple of tracks -> track a couple of frames: ![tracking](https://github.com/opencv/cvat/assets/50956430/087910dd-a0c8-4007-a25c-6952743c2f36) ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 24 October 2023, 11:56:24 UTC
e894e97 reset password procedure added to the documentation (#7035) 24 October 2023, 10:48:06 UTC
c6b660f Documentation: added headers, fixed cropped text and ordered lists (#6947) 24 October 2023, 10:34:08 UTC
f4566eb Bump @babel/traverse from 7.19.3 to 7.23.2 in /tests (#7023) 24 October 2023, 10:33:29 UTC
102b0a0 Bump @babel/traverse from 7.20.12 to 7.23.2 (#7024) 24 October 2023, 10:33:22 UTC
a2a452a Fixed: module 'PIL.Image' has no attribute 'LINEAR' (#7047) 24 October 2023, 10:32:20 UTC
55a22e1 Add support for default bucket prefix and ability to search for files (#6943) 24 October 2023, 10:31:50 UTC
acbb727 manual qa documentation updated (#7028) 24 October 2023, 10:31:26 UTC
bde1207 Merge pull request #7050 from opencv/dev-release-2.8.0 Update develop after v2.8.0 24 October 2023, 10:30:47 UTC
6c7ef41 Update release-2.8.0 after v2.8.0 24 October 2023, 09:08:07 UTC
5e771bb Merge branch 'master' into release-2.8.0 23 October 2023, 18:56:37 UTC
dcdadf6 change log text update 23 October 2023, 12:54:58 UTC
8b0ec00 Add a job for publishing Python packages upon release (#7013) <!-- 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. --> Manually with a modified version of the pipeline that uploads to TestPyPI. See successful run here: <https://github.com/SpecLad/cvat/actions/runs/6509890509/job/17745596516>. ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - ~~[ ] I have created a changelog fragment~~ <!-- see top comment in CHANGELOG.md --> - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 23 October 2023, 12:11:14 UTC
cd57917 Prepare release v2.8.0 23 October 2023, 11:41:49 UTC
e038b7c Factor out shared environment variables in docker-compose.yml (#7016) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> This improves maintainability of the file. ### 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 brought CVAT up using Docker Compose, and checked that the environment variables in containers were as expected. ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - ~~[ ] I have created a changelog fragment~~ <!-- see top comment in CHANGELOG.md --> - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 23 October 2023, 10:23:06 UTC
f8f2052 Do not fetch all organizations when UI opened (#7004) 20 October 2023, 14:45:56 UTC
99e4801 Update nested objects on parent labels update (#6958) Fixes #6871 Added batch update (note - no signals issued on this) for owning and nested objects (tasks, jobs) on parent (task, project) labels updates 20 October 2023, 08:11:52 UTC
9004b27 SDK: determine supported server versions automatically (#7026) This removes what should be the last manual step that used to be involved in making a release. 19 October 2023, 10:30:13 UTC
8197cd2 Don't fetch existing annotations in `cvat_sdk.auto_annotation.annotate_task` (#7019) We don't need existing annotations in order to re-annotate a task, but they were being fetched anyway, because that's how the underlying `TaskDataset` class works. Add an option to `TaskDataset` to disable annotation loading, and use it in `auto_annotate` to prevent those unnecessary fetches. 18 October 2023, 13:51:18 UTC
736881b Remove unnecessary COUNT for labels (#6918) Optimized /api/projects, /api/tasks, and /api/jobs requests. Previously for unification, we decided to add a count of labels into every response for each project, task, and job. It leads to performance issues. UI and probably other clients don't use the information because it is useless. Removing it, helps to optimize the SQL request several times. --------- Co-authored-by: Boris Sekachev <boris@cvat.ai> 18 October 2023, 12:36:33 UTC
c9a6083 Add test for retrieving bucket content when bucket contains manually created dirs (#7018) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> ~~- [ ] I have updated the documentation accordingly~~ - [x] I have added tests to cover my changes ~~- [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ ~~- [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 18 October 2023, 12:14:56 UTC
0f821e4 Add a GitHub workflow for finalizing a release (#6998) This automates the second half of the release process (the first being automated by `prepare-release.yml`). After this workflow completes, the only action that should remain for the releaser to do is to merge the `dev-release-*` pull request. We can't do that as part of this workflow, because CI has to finish first, and it seems pointless to create another workflow just to merge 1 PR. Apply some of the aspects of this pipeline to `prepare-release.yml` as well: * Make the release notes extraction process more sophisticated to work around GitHub's frustrating handling of line breaks in PR and release descriptions. * Use GitHub app credentials in order to be able to trigger other pipelines. 18 October 2023, 11:20:25 UTC
871bd4f Add basic checks for changelog fragments to CI (#7007) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> This'll help prevent simple mistakes that would cause scriv to assemble the changelog incorrectly. ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> Manual testing. ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - ~~[ ] I have created a changelog fragment~~ <!-- see top comment in CHANGELOG.md --> - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 18 October 2023, 06:27:44 UTC
28ea2b4 Add new community links to the `Links` README section (#7014) This PR adds two links to the CVAT README `Links` section. The first link is a tutorial written by the Roboflow team on how to use CVAT and the second link shows the Roboflow guide to using models for automatic labeling in CVAT. I would love for the Roboflow + CVAT integration to be more accessible to new users; the faster someone can label, the quicker they can get a model into production. 18 October 2023, 05:33:50 UTC
e8db2c3 Fix possible double writing of the uploaded client files in Upload-Multiple requests (#6952) Fixes #6878 In the case of big files (>2.5 MB by default), the uploaded files could be write-appended twice, leading to bigger raw file sizes than expected. This PR fixes the behavior by excluding repetitive writes where it was not supposed. - Fixed double append-writing of the uploaded files when Upload-Multiple requests are used - Fixed potential DB - disk inconsistencies in the case of upload errors - Added tests 17 October 2023, 09:12:58 UTC
021e58c Add support for Cloudflare R2 Buckets (#6701) It is currently not possible to add a Cloudflare R2 Bucket as a Cloud Storage source, since the Secret access key of R2 has a length of 64 but the ui/serializer restricts the length to 44. [This issue](https://github.com/opencv/cvat/issues/5512) addresses the same problem when using STORJ but with a max length of `128`. For me it would make the most sense to completely remove the max length, but this PR currently only fixes the R2 compatibility by increasing the max length to `64`. 16 October 2023, 14:54:36 UTC
b7ea8d1 [GCS] Skip manually created dirs (#7006) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> The same problem for GCS as was fixed for AWS S3 https://github.com/opencv/cvat/pull/6997 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> ~~- [ ] I have updated the documentation accordingly~~ ~~- [ ] I have added tests to cover my changes~~ ~~- [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ ~~- [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 16 October 2023, 14:28:45 UTC
b02cbe5 Disable zookeeper (#7003) 16 October 2023, 14:26:29 UTC
e6724fa Release v2.7.6 16 October 2023, 12:34:56 UTC
56f527a Merge pull request #7005 from opencv/release-2.7.6 Release v2.7.6 16 October 2023, 12:33:39 UTC
c1802c4 Update lowlevel-api.md (#6989) Fix the method name from `as_dict()` to `to_dict()` in SDK docs 16 October 2023, 10:15:42 UTC
8b0130f Inviting unregistered users by email (#6901) 16 October 2023, 09:47:22 UTC
fae72e0 prepare to new version 16 October 2023, 06:47:26 UTC
3c05e84 fixed changelog 13 October 2023, 15:35:53 UTC
6eead0d Fix CHANGELOG 13 October 2023, 13:39:25 UTC
f616d6a Prepare release v2.7.6 13 October 2023, 13:28:31 UTC
4d9af86 Removed `Need help` gitter link (#7002) 13 October 2023, 11:53:31 UTC
80e20ff Significant memory optimization when working with masks (#6996) 13 October 2023, 10:51:39 UTC
f938ff3 Fix getting CS content when S3 bucket contains created manually directories (#6997) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> This PR fixes retrieving cloud storage content for an AWS S3 bucket containing manually created "directories" (AWS ListObjectsV2 API returns such objects within the content). ![image](https://github.com/opencv/cvat/assets/49038720/af956beb-9a88-4391-aa17-2a9a0629e16c) A similar problem can be found [here](https://stackoverflow.com/questions/75620230/aws-s3-listobjectsv2-returns-folder-as-an-object). In this case, I prefer to simply filter keys from keys with a trailing slash, rather than filter from objects with 0 size. ### How has this been tested? Manually ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> ~~- [ ] I have updated the documentation accordingly~~ ~~- [ ] I have added tests to cover my changes~~ ~~- [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ ~~- [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 13 October 2023, 10:46:08 UTC
1b77005 Set autorestart=true for all workers (#6945) Helm: set memory request for keydb SUpervisord configs: - Added `autorestart=true` option for all workers - Unified program names to use dashes as delimiter instead of mixed '_' and '-' - Minor improvements to supervisor configurations 12 October 2023, 20:27:30 UTC
2802442 Allow to upload tracks from COCO formats (#6969) This PR resolves the following problems: 1. During import we ignore track_id attribute for annotations if these annotations do not come from one of these formats `('cvat', 'datumaro', 'sly_pointcloud')` this prevents to import tracks in coco format -> this PR extends the list of "track formats" 2. When we convert a dataset from CVAT representation to Datumaro Dataset in all possible situations only the first shape of the skeleton track is a keyframe, all other shapes will be as marked as not keyframes it leads to problems when we try to import such tracks that were exported from CVAT -> this PR adds the following line of code: set `keyframe = True` for skeletons if at least one point of this skeleton is keyframe 3. During import skeleton tracks our code always expects to see a "keyframe" attribute for the skeleton's element, but not all formats support attributes for skeleton points (for example COCO Keypoints doesn't allow to have attributes for each skeleton's point). And if the server doesn't see this attribute for some element we ignore this element -> this PR adds the following logic for skeleton track: if skeleton's elements don't have a keyframe attribute at all then consider such skeleton elements as keyframes = True 12 October 2023, 19:59:30 UTC
93a4f05 Added X-Frame-Options: deny (#6992) 12 October 2023, 19:49:44 UTC
848e373 Enabled nginx proxy buffering (#6991) 12 October 2023, 19:46:26 UTC
d85e3a2 Disabled translation the page causing the issues (#6993) 12 October 2023, 12:08:05 UTC
5545e83 Fixed crash related to issue tries to mount to not existing parent (#6977) 12 October 2023, 10:17:43 UTC
41a6296 plan name changed to solo documentation (#6985) 12 October 2023, 09:24:56 UTC
97a079e Added persist image filters test (#6978) 12 October 2023, 08:28:50 UTC
a2d1c5f Fixed object states memory leak (#6984) 12 October 2023, 08:27:52 UTC
17bef4f Updated asset for 3d tests (added nan values to one of them) (#6981) 12 October 2023, 06:14:44 UTC
b450b44 Fix tracks splitting for tracks that have sub-tracks (#6968) When uploading annotations for the whole task that has few jobs our server splits tracks. Each track we divide into a few tracks in that way that each track corresponds to only one job and all shapes of the track do not extend beyond the frame range corresponding to that job. It mainly works, but we have a problem with skeleton tracks. Due to this problem we if upload skeleton tracks for the whole task all our tracks will be duplicated for each job but not split, it means that we will have tracks that extend beyond the frame range of jobs and it leads to bad side effects, in this case, our exported annotations from such task could be incorrect or we won't be able to export annotations at all. And the reason for this problem is this small bug, which this PR fixes. Our code really slices sub-tracks for the skeleton track, but after this slicing server doesn't save the result. 11 October 2023, 20:10:55 UTC
cf4329a Override EditorConfig settings for YAML files (#6980) I realized that I was fighting my editor, because we indent YAML files with 2 spaces, but `.editorconfig` specifies 4 spaces for all files. Align the config with reality. 11 October 2023, 13:48:55 UTC
80daa10 Fixed Siammask tracker error on grayscale images (#6982) ```python "Exception caught in handler - \"not enough values to unpack (expected 3, got 2)\": Traceback (most recent call last): File \"/opt/nuclio/_nuclio_wrapper.py\", line 143, in serve_requests await self._handle_event(event) File \"/opt/nuclio/_nuclio_wrapper.py\", line 397, in _handle_event entrypoint_output = self._entrypoint(self._context, event) File \"/opt/nuclio/main.py\", line 29, in handler shape, state = context.user_data.model.infer(image, shape, states[i] if i < len(states) else None) File \"/opt/nuclio/model_handler.py\", line 56, in infer self.config['hp'], device=self.device) File \"/opt/nuclio/SiamMask/tools/test.py\", line 152, in siamese_init z_crop = get_subwindow_tracking(im, target_pos, p.exemplar_size, s_z, avg_chans) File \"/opt/nuclio/SiamMask/tools/test.py\", line 88, in get_subwindow_tracking r, c, k = im.shape ValueError: not enough values to unpack (expected 3, got 2) ``` 11 October 2023, 13:45:53 UTC
5219c8f Support rotation in detector results (#6961) 11 October 2023, 11:59:10 UTC
176bac2 Disabled TUS resume upload option (not used, but pollutes local storage) (#6976) 11 October 2023, 10:16:44 UTC
43181a0 Add a GitHub workflow to prepare a release pull request (#6972) This automates the first half of the current release process. The second half will be implemented by another workflow. The reason why it can't all be done in a single workflow is that it's useful to let developers inspect what'll go into the release before actually publishing it, and to apply any last-minute fixes, if necessary. It also allows CI to complete for the release PR. To support the new workflow, add a `--set` option to `update_version.py` that sets the version to a custom value. 11 October 2023, 09:27:43 UTC
ae9cc2e [Snyk] Security upgrade opencv-python-headless from 4.5.5.62 to 4.8.1.78 (#6931) Co-authored-by: snyk-bot <snyk-bot@snyk.io> Co-authored-by: Roman Donchenko <roman@cvat.ai> 10 October 2023, 16:48:02 UTC
fceeeeb Update README for REST API tests (#6971) 10 October 2023, 12:58:47 UTC
6ce88d3 Persist image filters across jobs (#6953) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 10 October 2023, 11:10:13 UTC
3255b09 Release v2.7.5 09 October 2023, 14:56:37 UTC
7956a18 Release v2.7.5 09 October 2023, 14:55:26 UTC
e0ea6d2 prepare to new version 09 October 2023, 12:57:14 UTC
20db599 Merge remote-tracking branch 'origin/master' into release-2.7.5 09 October 2023, 12:55:06 UTC
24d7c26 Bump version to 2.7.5 09 October 2023, 12:55:01 UTC
e699848 Added temporary workaround to fix corrupted zip file (#6965) 09 October 2023, 12:37:14 UTC
bcf1736 Added test for manifest filetype (#6951) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Test for #6890 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 09 October 2023, 09:08:57 UTC
4428e14 Remove dnspython from dependencies (#6944) 09 October 2023, 07:47:49 UTC
7462e03 Documentation: removed outdated links (#6949) Fix [5972](https://github.com/opencv/cvat/issues/5972) 07 October 2023, 08:50:37 UTC
dbff2b2 Release v2.7.4 07 October 2023, 08:06:33 UTC
2ec5c44 Release v2.7.4 07 October 2023, 08:04:56 UTC
701c461 Merge branch 'master' into release-2.7.4 06 October 2023, 14:58:08 UTC
7e35aad prepare to new version 06 October 2023, 13:53:44 UTC
74de11f Bump version to 2.7.4 06 October 2023, 13:47:26 UTC
06bae53 Fixed nan values in .pcd files, fixed broken navigation in 3D workspace, updated three js (#6862) 06 October 2023, 10:04:10 UTC
551d28f Switch to using scriv for maintaining the changelog (#6942) This is beneficial in multiple ways: * No more `CHANGELOG.md` merge conflicts and mis-merges. * At release time all you need to do to update the changelog is run `scriv collect --version X.Y.Z`. Scriv can also create GitHub releases, although I haven't evaluated this feature yet. Configure scriv so that its output format is the same as what we currently use for our changelog. There are only a few minor differences: * scriv prepends an HTML anchor to every version heading. * scriv puts blank lines between list items (in CommonMark terms, the lists are loose rather than tight). 06 October 2023, 09:30:53 UTC
ae1dc1b Sort frames during project dumping (#6927) When we export a task or project in CVAT format [our code uses](https://github.com/opencv/cvat/blob/d497bb6a90dd3c9625c3c8e8f73278019e21983d/cvat/apps/dataset_manager/formats/cvat.py#L717) the `group_by_frame` function. For tasks and for projects behaviour of this function is different since for tasks [we perform sorting frames](https://github.com/opencv/cvat/blob/d497bb6a90dd3c9625c3c8e8f73278019e21983d/cvat/apps/dataset_manager/bindings.py#L420-L421) but for projects [we don't](https://github.com/opencv/cvat/blob/d497bb6a90dd3c9625c3c8e8f73278019e21983d/cvat/apps/dataset_manager/bindings.py#L1152-L1154). As a result, we can have a situation when our annotation file for the project will have a list of images in unsorted form. So this PR adds sorting frames during project export as well. 05 October 2023, 12:42:15 UTC
bfc86ae Improved issues comments pipeline (#6937) 05 October 2023, 08:36:11 UTC
9501bae Bump postcss from 8.4.25 to 8.4.31 (#6938) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 04 October 2023, 14:55:47 UTC
back to top