swh:1:snp:973504f75325e1c705c39106a2685791af62e9e3
- HEAD
- refs/heads/az/fix_analytics
- refs/heads/az/helm_e2e
- refs/heads/az/helm_enable_e2e
- refs/heads/az/hotfix-2.8.2
- refs/heads/az/k8s_probes
- refs/heads/az/update_dev_docs
- refs/heads/bs/disable_throttling_test
- refs/heads/bs/do_not_fail_job
- refs/heads/bs/fixed_admin_504
- refs/heads/bs/fixed_types
- refs/heads/bs/manual_analytics_report
- refs/heads/bs/upgrade_node
- refs/heads/bs/upgrade_react
- refs/heads/dev-release-2.12.0
- refs/heads/develop
- refs/heads/django-social-account-sso
- refs/heads/gh-pages
- refs/heads/hotfix-2.4.1
- refs/heads/hotfix-2.4.7
- refs/heads/kl/data-processing
- refs/heads/kl/dataset-not-found-logging
- refs/heads/ma/analytics-cloud
- refs/heads/ma/documentation-small-fixes
- refs/heads/ma/filters-doc
- refs/heads/ma/payment-management
- refs/heads/ma/user-roles
- refs/heads/ma/vat-and-tax
- refs/heads/master
- refs/heads/mk/disable_authentication_for_public_endpoints
- refs/heads/mk/fix_issue_5954
- refs/heads/mk/handle_validation_error
- refs/heads/mk/increase_delay_to_start_cleaning_job
- refs/heads/mk/optimize-retrieving-annotations
- refs/heads/mk/social_accounts_auth_doc
- refs/heads/nm/cluster_app
- refs/heads/nm/fix_memory_leak_v2
- refs/heads/release-1.5.0
- refs/heads/release-1.7.0
- refs/heads/release-2.1.0
- refs/heads/release-2.2.0
- refs/heads/release-2.3.0
- refs/heads/release-2.4.0
- refs/heads/release-2.4.2
- refs/heads/release-2.4.3
- refs/heads/release-2.4.4
- refs/heads/release-2.4.5
- refs/heads/release-2.4.6
- refs/heads/release-2.4.7
- refs/heads/release-2.4.9
- refs/heads/release-2.5.1
- refs/heads/release-2.6.2
- refs/heads/release-2.7.1
- refs/heads/release-2.7.4
- refs/heads/release-2.7.6
- refs/heads/revert-6668-kl/add-analytics-ui-test
- refs/heads/sk/add-test-for-getting-swagger-docs
- refs/heads/sk/fix-lambda-manager-permissions
- refs/heads/sk/improve-error-messaging
- refs/heads/sk/prevent-export-dataset-with-images
- refs/heads/sk/refactor-tests
- refs/heads/sk/remove-limit-manager
- refs/heads/snyk-fix-eeeaef7319c23e97ad6742712856b4c5
- refs/heads/welcome_email
- refs/heads/zm/add-query-cli-command
- refs/heads/zm/cli-usecases
- refs/heads/zm/enable-backups-from-share
- refs/heads/zm/fix-skeleton-sublabels
- refs/heads/zm/migrate-server-tests-to-pylint
- refs/heads/zm/project-quality-server
- refs/heads/zm/project-quality-server-3
- refs/heads/zm/update-dm-format
- refs/remotes/ivk/ivk
- refs/remotes/origin/develop
- refs/remotes/origin/mk/add_filter_description
- refs/remotes/sam/develop
- refs/remotes/semiauto/handle-semi-auto
- refs/tags/v0.3.0
- refs/tags/v0.4.0
- refs/tags/v0.4.1
- refs/tags/v0.5.0
- refs/tags/v0.5.1
- refs/tags/v0.5.2
- refs/tags/v0.6.0
- refs/tags/v0.6.1
- refs/tags/v1.0.0
- refs/tags/v1.0.0-alpha
- refs/tags/v1.0.0-beta.1
- refs/tags/v1.0.0-beta.2
- refs/tags/v1.1.0
- refs/tags/v1.1.0-alpha
- refs/tags/v1.1.0-beta
- refs/tags/v1.2.0
- refs/tags/v1.2.0-alpha
- refs/tags/v1.2.0-beta
- refs/tags/v1.4.0
- refs/tags/v2.0.0
- refs/tags/v2.1.0
- refs/tags/v2.10.0
- refs/tags/v2.10.1
- refs/tags/v2.10.2
- refs/tags/v2.10.3
- refs/tags/v2.11.0
- refs/tags/v2.11.1
- refs/tags/v2.11.2
- refs/tags/v2.11.3
- refs/tags/v2.12.0
- refs/tags/v2.2.0
- refs/tags/v2.4.0
- refs/tags/v2.4.1
- refs/tags/v2.4.2
- refs/tags/v2.4.3
- refs/tags/v2.4.4
- refs/tags/v2.4.5
- refs/tags/v2.4.6
- refs/tags/v2.4.7
- refs/tags/v2.4.8
- refs/tags/v2.4.9
- refs/tags/v2.5.0
- refs/tags/v2.5.2
- refs/tags/v2.6.0
- refs/tags/v2.6.1
- refs/tags/v2.6.2
- refs/tags/v2.7.0
- refs/tags/v2.7.1
- refs/tags/v2.7.2
- refs/tags/v2.7.3
- refs/tags/v2.7.4
- refs/tags/v2.7.5
- refs/tags/v2.7.6
- refs/tags/v2.8.0
- refs/tags/v2.8.1
- refs/tags/v2.8.2
- refs/tags/v2.9.0
- refs/tags/v2.9.1
- refs/tags/v2.9.2
Permalinks
To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.
Revision | Author | Date | Message | Commit Date |
---|---|---|---|---|
519c57f | Nikita Manovich | 05 July 2023, 16:39:39 UTC | Release v2.5.0 | 05 July 2023, 16:39:39 UTC |
365bfb1 | Andrey Zhavoronkov | 05 July 2023, 11:19:36 UTC | Merge remote-tracking branch 'origin/master' into release-2.5.0 | 05 July 2023, 11:19:36 UTC |
024ae69 | Andrey Zhavoronkov | 05 July 2023, 11:14:34 UTC | Bump version to 2.5.0 | 05 July 2023, 11:14:34 UTC |
9148234 | Maria Khrustaleva | 04 July 2023, 13:17:17 UTC | Fix task preview styles (#6418) <!-- 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. --> Before ![image](https://github.com/opencv/cvat/assets/49038720/a24dd717-fa8e-4c7f-aa46-02772505d26c) After ![image](https://github.com/opencv/cvat/assets/49038720/983076c7-93f5-47a6-8fe5-45834ad93320) ![image](https://github.com/opencv/cvat/assets/49038720/0c17352e-ecb3-4c83-b8bd-8ecc59edf29b) ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> Manually ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch ~~- [ ] I have 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@cvat.ai> | 04 July 2023, 13:17:17 UTC |
75451df | Mariia Acoca | 04 July 2023, 11:08:45 UTC | Annotators Guides documentation added (#6411) <!-- 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. --------- Co-authored-by: Boris Sekachev <boris@cvat.ai> | 04 July 2023, 11:08:45 UTC |
31f78d5 | Maxim Zhiltsov | 29 June 2023, 16:59:04 UTC | Fix file matching in annotation import for multiple dots in filenames (#6350) <!-- 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. --> Fixes https://github.com/opencv/cvat/issues/6319 - Fixed invalid dataset root search, leading to invalid file matching - Restored detailed dataset import error messages - Added tests ### 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. | 29 June 2023, 16:59:04 UTC |
b3081bf | Roman Donchenko | 29 June 2023, 16:58:21 UTC | CLI: don't set `discard_unknown_keys` (#6402) <!-- 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. --> For unclear reasons, when this setting is enabled, the OpenAPI Generator runtime becomes unable to parse `AnnotationsRead` values from JSON. Specifically, it thinks that the JSON value is ambiguous, because it can be parsed both as `LabeledData` and as `IOBase`. The former makes sense, but the latter does not. I think it's just a bug in the runtime. This line is why the issue only occurs when `discard_unknown_keys` is set: https://github.com/OpenAPITools/openapi-generator/blob/v6.0.1/modules/openapi-generator/src/main/resources/python/model_utils.mustache#L1139 The CLI currently doesn't parse `AnnotationRead` anywhere, so this patch doesn't have any user-visible effects. However, I'm prototyping a new CLI command which will need to parse annotations. Change `tasks_create` so that it routes kwargs to the appropriate destinations instead of passing all of them both to `TaskWriteRequest` and `create_from_data`. I don't think this is _really_ necessary (the extra arguments should just be ignored), but it makes the code more illustrative. ### 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. --> Unit tests. ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - ~~[ ] I have 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. | 29 June 2023, 16:58:21 UTC |
29397b3 | Roman Donchenko | 29 June 2023, 16:41:14 UTC | Fix a bunch of typos (#6405) <!-- 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. | 29 June 2023, 16:41:14 UTC |
3f5eb71 | Andrey Zhavoronkov | 29 June 2023, 12:57:44 UTC | Updated CHANGELOG.md with the version for the next release | 29 June 2023, 12:57:44 UTC |
8f861eb | Nikita Manovich | 29 June 2023, 12:56:33 UTC | Release v2.4.9 | 29 June 2023, 12:56:33 UTC |
16d03aa | Roman Donchenko | 29 June 2023, 11:41:19 UTC | Implement more comprehensive SSRF mitigation (#6362) The current mitigation approach (resolving the IP address and checking if it's in the private range) is insufficient for a few reasons: * It is susceptible to DNS rebinding (an attacker-controlled DNS name resolving to a public IP address when queried during the check, and to a private IP address afterwards). * It is susceptible to redirect-based attacks (a server with a public address redirecting to a server with a private address). * It is only applied when downloading remote files of tasks (and is not easily reusable). Replace it with an approach based on smokescreen, a proxy that blocks connections to private IP addresses. In addition, use this proxy for webhooks, since they also make requests to untrusted URLs. The benefits of smokescreen are as follows: * It's not susceptible to the problems listed above. * It's configurable, so system administrators can allow certain private IP ranges if necessary. This configurability is exposed via the `SMOKESCREEN_OPTS` environment variable. * It doesn't require much code to use. The drawbacks of smokescreen are: * It's not as clear when the request fails due to smokescreen (compared to manual IP validation). To compensate, make the error message in `_download_data` more verbose. * The smokescreen project seems to be in early development (judging by the 0.0.x version numbers). Still, Stripe itself uses it, so it should be good enough. It's also not very convenient to set up (on account of not providing binaries), so disable it in development environments. Keep the scheme check from `_validate_url`. I don't think this check prevents any attacks (as requests only supports http/https to begin with), but it provides a friendly error message in case the user tries to use an unsupported scheme. | 29 June 2023, 11:41:19 UTC |
bbdc4c3 | Andrey Zhavoronkov | 29 June 2023, 11:23:12 UTC | Update CHANGELOG | 29 June 2023, 11:23:12 UTC |
75c1e6f | Andrey Zhavoronkov | 29 June 2023, 11:21:50 UTC | Bump version to 2.4.9 | 29 June 2023, 11:21:50 UTC |
970db99 | Boris Sekachev | 28 June 2023, 07:36:20 UTC | Added test to check exif rotated images width/height (#6384) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [x] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 29 June 2023, 11:20:06 UTC |
d950d24 | Roman Donchenko | 28 June 2023, 20:26:24 UTC | PyTorch adapter: fix loading tasks that have already been cached (#6396) <!-- 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 was broken in 4fc494f4. Add a test to cover this case. Fixes #6047. | 28 June 2023, 20:26:24 UTC |
1b28162 | Roman Donchenko | 28 June 2023, 14:41:52 UTC | Make the PyTorch adapter tests less likely to be disabled by accident (#6386) Currently, any kind of import error will disable the tests. This makes it far too easy to disable the tests accidentally by messing up the imports. Only disable the tests if PyTorch or torchvision are not found. | 28 June 2023, 14:41:52 UTC |
f6420eb | Boris Sekachev | 28 June 2023, 07:36:20 UTC | Added test to check exif rotated images width/height (#6384) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [x] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 28 June 2023, 07:36:20 UTC |
7f6080e | Boris Sekachev | 28 June 2023, 05:10:05 UTC | Added basic pipeline for markdown guide (#6381) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [x] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 28 June 2023, 05:10:05 UTC |
b415fec | Kirill Sizov | 27 June 2023, 11:22:49 UTC | Add Organization model to admin panel (#6366) <!-- 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 Sometimes it's more convenient to search and create an organization via the admin panel than via rest api methods. ### 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. | 27 June 2023, 11:22:49 UTC |
7ec84b8 | Roman Donchenko | 27 June 2023, 11:21:54 UTC | Don't rerun the tests when the PR description is edited (#6373) <!-- 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. --> Most of the time it's useless and just clogs up the build queue. When it's useful (e.g. when removing "[Dependent]" from the title), it's easy enough to retrigger the build manually by updating your branch. Fixes #5921. ### 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. | 27 June 2023, 11:21:54 UTC |
e6a38da | Roman Donchenko | 27 June 2023, 08:09:24 UTC | Re-enable testing for the PyTorch adapter (#6377) It was accidentally disabled in #6173. Also, refactor the build steps to make the log easier to read. | 27 June 2023, 08:09:24 UTC |
bedbd82 | Boris Sekachev | 26 June 2023, 12:43:57 UTC | Added missed auto_add argument (#6364) <!-- 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 #4394 ### 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)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. | 26 June 2023, 12:43:57 UTC |
8590e90 | Kirill Lakhov | 26 June 2023, 09:58:26 UTC | Merge pull request #6039 from opencv/zm/gt-jobs Honey pot UI | 26 June 2023, 09:58:26 UTC |
4775e3f | klakhov | 23 June 2023, 09:52:50 UTC | improved highlight styles | 23 June 2023, 10:12:39 UTC |
33dd488 | klakhov | 23 June 2023, 09:17:53 UTC | fixed styles and report time | 23 June 2023, 09:17:53 UTC |
1f6c63b | Kirill Sizov | 23 June 2023, 08:31:18 UTC | Update gitter link (#6365) <!-- 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. | 23 June 2023, 08:31:18 UTC |
0908914 | klakhov | 23 June 2023, 06:47:44 UTC | fixed eslint | 23 June 2023, 06:47:44 UTC |
7ae3b93 | klakhov | 23 June 2023, 06:36:08 UTC | fixed merge error | 23 June 2023, 06:36:08 UTC |
8c8e2a8 | Kirill Lakhov | 23 June 2023, 06:25:27 UTC | Merge branch 'develop' into zm/gt-jobs | 23 June 2023, 06:25:27 UTC |
ea6c68f | Boris Sekachev | 23 June 2023, 06:14:21 UTC | Fixed: visible 'To background' button in review mode (#6363) <!-- 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 #6297 ### 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. | 23 June 2023, 06:14:21 UTC |
307db39 | Boris Sekachev | 23 June 2023, 06:13:21 UTC | Markdown documentation for tasks/projects (#6191) <!-- 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 <img width="1130" alt="image" src="https://github.com/opencv/cvat/assets/40690378/3c1b767d-2aa2-474b-af1e-1fc02d8c359d"> <img width="1133" alt="image" src="https://github.com/opencv/cvat/assets/40690378/fdf6115a-e88d-4da6-83fb-c9fddd871e49"> <img width="1920" alt="image" src="https://github.com/opencv/cvat/assets/40690378/f6e97db5-84cb-4c1e-9b2a-82eca633a79c"> Resolved #287 Resolved #3680 Resolved #5580 ### 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. | 23 June 2023, 06:13:21 UTC |
ff76c64 | klakhov | 23 June 2023, 05:59:09 UTC | removed outdated code, removed submit and open | 23 June 2023, 05:59:09 UTC |
ec149df | Andrey Zhavoronkov | 22 June 2023, 11:42:37 UTC | Merge pull request #6358 from opencv/az/update_develop Update changelog | 22 June 2023, 11:42:37 UTC |
ab020f5 | Boris Sekachev | 22 June 2023, 11:34:39 UTC | Merge pull request #6356 from opencv/bs/hotfix Release 2.4.8 | 22 June 2023, 11:34:39 UTC |
f853490 | Andrey Zhavoronkov | 22 June 2023, 11:31:56 UTC | Merge remote-tracking branch 'origin/develop' into az/update_develop | 22 June 2023, 11:31:56 UTC |
65d6713 | klakhov | 22 June 2023, 09:45:01 UTC | renamed `ready` variable | 22 June 2023, 09:45:01 UTC |
821c456 | klakhov | 22 June 2023, 09:30:12 UTC | fixed more comments | 22 June 2023, 09:30:12 UTC |
02465c1 | Mariia Acoca | 22 June 2023, 09:23:47 UTC | Organizations documentation updated documentation and images (#6349) <!-- 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. | 22 June 2023, 09:23:47 UTC |
e0ea7f2 | Andrey Zhavoronkov | 22 June 2023, 08:54:16 UTC | Bump schema version | 22 June 2023, 08:54:16 UTC |
27a1861 | klakhov | 22 June 2023, 08:51:13 UTC | applied comments | 22 June 2023, 08:51:13 UTC |
3bf4ccb | Andrey Zhavoronkov | 22 June 2023, 08:39:50 UTC | Bump version to 2.4.8 | 22 June 2023, 08:39:50 UTC |
aea6908 | Boris Sekachev | 22 June 2023, 08:33:48 UTC | Updated changelog | 22 June 2023, 08:33:48 UTC |
d5d121c | Boris Sekachev | 22 June 2023, 07:29:10 UTC | Fixed extension when compute original chunks (#6355) | 22 June 2023, 08:29:29 UTC |
5bc8c7b | Boris Sekachev | 22 June 2023, 07:29:10 UTC | Fixed extension when compute original chunks (#6355) | 22 June 2023, 07:29:10 UTC |
cf91dcb | klakhov | 22 June 2023, 06:20:15 UTC | fixed unit test | 22 June 2023, 06:20:15 UTC |
98cf03b | Kirill Lakhov | 22 June 2023, 06:08:30 UTC | Merge branch 'develop' into zm/gt-jobs | 22 June 2023, 06:08:30 UTC |
4bb0003 | klakhov | 22 June 2023, 06:05:35 UTC | fixed potential performance issue | 22 June 2023, 06:05:35 UTC |
5d36068 | Boris Sekachev | 22 June 2023, 05:55:37 UTC | Updated changelog (#6354) <!-- 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. | 22 June 2023, 05:55:37 UTC |
109cd7a | klakhov | 21 June 2023, 11:55:06 UTC | applied comments | 21 June 2023, 11:55:06 UTC |
bb126d3 | Maxim Zhiltsov | 21 June 2023, 09:39:38 UTC | Enable coverage collection in quality reports worker (#6341) - Added missing coverage collection in quality reports worker - Fixed invalid worker class in webhooks worker | 21 June 2023, 09:39:38 UTC |
614f3c7 | Kirill Lakhov | 21 June 2023, 07:23:45 UTC | Merge branch 'develop' into zm/gt-jobs | 21 June 2023, 07:23:45 UTC |
442050d | klakhov | 21 June 2023, 07:22:41 UTC | updated chanelog | 21 June 2023, 07:22:41 UTC |
39764f8 | klakhov | 21 June 2023, 07:12:01 UTC | removed ablity to delete frame from GT | 21 June 2023, 07:12:01 UTC |
6c3ad26 | klakhov | 21 June 2023, 06:57:35 UTC | fixed intersecting ids in conflicts/server-ids | 21 June 2023, 06:57:35 UTC |
55c535d | klakhov | 21 June 2023, 06:46:48 UTC | removed !important | 21 June 2023, 06:46:48 UTC |
96090f2 | klakhov | 21 June 2023, 06:12:20 UTC | reworked cvat-core classes | 21 June 2023, 06:12:20 UTC |
a136a86 | klakhov | 21 June 2023, 05:32:47 UTC | fixed height on quality page | 21 June 2023, 05:32:47 UTC |
9ba5934 | klakhov | 21 June 2023, 05:21:40 UTC | fixed navigation with deleted frames | 21 June 2023, 05:21:40 UTC |
1a2365c | Maxim Zhiltsov | 20 June 2023, 20:02:57 UTC | Fix API schema for the owner field (#6343) The owner field can be null if the user was removed after the object had been created, but API schema doesn't support this. This PR fixes the schema. | 20 June 2023, 20:02:57 UTC |
d29b84c | Andrey Zhavoronkov | 20 June 2023, 17:17:35 UTC | Hotfix 2.4.7 (#6342) | 20 June 2023, 17:17:35 UTC |
97eb6a9 | Maxim Zhiltsov | 20 June 2023, 11:18:26 UTC | Optimize DB requests (#6340) Optimizes several DB request memory issues, introduced in #6204 - Optimized memory use in job annotation retrieval - Optimized migration | 20 June 2023, 11:18:26 UTC |
9db68a3 | Andrey Zhavoronkov | 20 June 2023, 09:04:11 UTC | Merge pull request #6329 from opencv/az/release-2.5.0 Az/release 2.5.0 | 20 June 2023, 09:04:11 UTC |
0c5c901 | Andrey Zhavoronkov | 20 June 2023, 08:40:59 UTC | Merge remote-tracking branch 'origin/develop' into az/release-2.5.0 | 20 June 2023, 08:40:59 UTC |
38df1cf | Maxim Zhiltsov | 19 June 2023, 08:05:05 UTC | Fix task mode in tasks restored from backup (#6216) - Fixes the problem with the task mode described in the CVAT corrupts annotations when exported with CVAT for video (#5668) - Fixes the problem with failing backup import because of the manifest file existence from Cannot export dataset (KeyError: 'outside') / can't import backup from older version (#5971) - Cleaned test assets (removed extra directories from unexistent tasks and jobs) | 19 June 2023, 08:05:05 UTC |
290634a | klakhov | 19 June 2023, 07:15:50 UTC | Renamed Raw to Serialized | 19 June 2023, 07:15:50 UTC |
01f86fd | klakhov | 19 June 2023, 07:11:26 UTC | fixed array operations | 19 June 2023, 07:11:26 UTC |
24013a6 | Maxim Zhiltsov | 16 June 2023, 15:43:24 UTC | Add job validation stage summary (#5761) - Added info about jobs in validation stage - Jobs are counted completed only at the acceptance stage in task job summaries | 16 June 2023, 15:43:24 UTC |
f8bb591 | Andrey Zhavoronkov | 16 June 2023, 14:32:41 UTC | Release v2.4.7 (#6328) ## \[2.4.7] - 2023-06-16 ### Added - \[API\] API Now supports the creation and removal of Ground Truth jobs. (<https://github.com/opencv/cvat/pull/6204>) - \[API\] We've introduced task quality estimation endpoints. (<https://github.com/opencv/cvat/pull/6204>) - \[CLI\] An option to select the organization. (<https://github.com/opencv/cvat/pull/6317>) ### Fixed - Issues with running serverless models for EXIF-rotated images. (<https://github.com/opencv/cvat/pull/6275/>) - File uploading issues when using https configuration. (<https://github.com/opencv/cvat/pull/6308>) - Dataset export error with `outside` property of tracks. (<https://github.com/opencv/cvat/issues/5971>) - Broken logging in the TransT serverless function. (<https://github.com/opencv/cvat/pull/6290>) --------- Co-authored-by: Anastasia Yasakova <yasakova_anastasiya@mail.ru> Co-authored-by: Mariia Acoca <39969264+mdacoca@users.noreply.github.com> Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> Co-authored-by: klakhov <kirill.9992@gmail.com> Co-authored-by: Roman Donchenko <roman@cvat.ai> Co-authored-by: Kirill Sizov <kirill.sizov@cvat.ai> Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru> Co-authored-by: Paweł Kotiuk <kotiuk@zohomail.eu> Co-authored-by: Nikita Manovich <nikita@cvat.ai> | 16 June 2023, 14:32:41 UTC |
f6b0801 | Maxim Zhiltsov | 16 June 2023, 14:14:25 UTC | Auto-annotation support for jobs (#6276) - Added API support to run auto-annotation on jobs - Added API schema definitions for offline lambda call endpoints | 16 June 2023, 14:14:25 UTC |
b0e32af | Andrey Zhavoronkov | 16 June 2023, 12:21:36 UTC | Update version | 16 June 2023, 12:21:36 UTC |
429bf6e | Andrey Zhavoronkov | 16 June 2023, 12:15:22 UTC | Merge remote-tracking branch 'origin/master' into release-2.4.7 | 16 June 2023, 12:15:22 UTC |
451c539 | Andrey Zhavoronkov | 16 June 2023, 12:08:00 UTC | Bump version to 2.4.7 | 16 June 2023, 12:09:18 UTC |
5c006ea | Mariia Acoca | 16 June 2023, 11:50:16 UTC | Update changelog (#6327) <!-- 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. | 16 June 2023, 11:50:16 UTC |
22a0acb | Andrey Zhavoronkov | 16 June 2023, 08:44:13 UTC | Use unix domain socket instead of tcp for Uvicorn (#6325) Using a unix socket for Uvicorn as recommended in the documentation: https://www.uvicorn.org/deployment/#running-behind-nginx | 16 June 2023, 08:44:13 UTC |
86c5930 | Mariia Acoca | 16 June 2023, 08:37:52 UTC | updated images, wording, added video to analytics documentation (#6315) <!-- 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. | 16 June 2023, 08:37:52 UTC |
3eeaeb2 | Kirill Lakhov | 15 June 2023, 12:14:33 UTC | Added support for react-markown in AI tools errors (#6320) <!-- 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 --> This is quick-fix for errors that occur in AI tools errors. Generally, we need to throw errors via errors-state. ### 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 June 2023, 12:14:33 UTC |
871756d | Roman Donchenko | 15 June 2023, 10:43:12 UTC | Add organization support to the CLI (#6317) This is the CLI equivalent of #5718. | 15 June 2023, 10:43:12 UTC |
a46df53 | klakhov | 15 June 2023, 07:54:00 UTC | fixed issue highlight | 15 June 2023, 07:54:00 UTC |
5faf945 | klakhov | 15 June 2023, 07:48:36 UTC | unified annotation filter | 15 June 2023, 07:48:36 UTC |
fb87d7d | Andrey Zhavoronkov | 14 June 2023, 21:13:38 UTC | Fixed x-forwarded-proto header (No need to set the header explicitly, as it is set by Traefik). (#6308) <!-- 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 docker-compose.https.yml config enabled ### 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: Nikita Manovich <nikita@cvat.ai> | 14 June 2023, 21:13:38 UTC |
fc3af2b | klakhov | 14 June 2023, 16:14:13 UTC | gt tracks shown only on gt job frames | 14 June 2023, 16:19:11 UTC |
e6d3d0d | klakhov | 14 June 2023, 15:18:33 UTC | fixed opening gt job | 14 June 2023, 15:18:33 UTC |
bd84ed6 | klakhov | 14 June 2023, 15:02:57 UTC | removed list from gt anno, fixed higlight | 14 June 2023, 15:02:57 UTC |
b19e925 | Roman Donchenko | 14 June 2023, 11:56:29 UTC | Stop using the production configuration for generating the schema (#6251) Since 6852caef, that's no longer necessary, as the same database is used in production and development. This makes development environments slightly smaller and easier to set up. This (mostly) reverts commit 1ae7a341e8dbe72dfeab89b5808447a668ab6876. | 14 June 2023, 11:56:29 UTC |
c253809 | Roman Donchenko | 14 June 2023, 10:04:34 UTC | Fix logging in the TransT serverless function (#6290) The Docker image for this function includes Conda, and uses `conda run` to run the Nuclio processor. Unfortunately, `conda run` buffers the entire output of the child process until that process exits, and since the processor never exits, its logs are never printed (and slowly consume memory). Conda is actually completely useless here, so just get rid of it, which fixes the problem. In addition, apply a few other improvements: * Synchronize the PyTorch and TransT versions between the CPU and GPU variants. * Replace `opencv-python` with `opencv-python-headless`, which has fewer dependencies. * Use the `ADD` command instead of wget. Altogether, these improvements shave ~780 MB off the size of the CPU image (didn't check for the GPU one). | 14 June 2023, 10:04:34 UTC |
ec933d0 | klakhov | 14 June 2023, 09:10:21 UTC | Merge branch 'zm/gt-jobs' of https://github.com/cvat-ai/cvat into zm/gt-jobs | 14 June 2023, 09:10:21 UTC |
b1a55fd | klakhov | 14 June 2023, 09:08:57 UTC | fixed sorting in quality job list | 14 June 2023, 09:08:57 UTC |
f6183a8 | klakhov | 14 June 2023, 08:16:28 UTC | fixed frame count percent | 14 June 2023, 08:16:28 UTC |
a727cdc | klakhov | 14 June 2023, 08:05:05 UTC | returned copy feature | 14 June 2023, 08:05:05 UTC |
fcae9fa | klakhov | 14 June 2023, 07:53:54 UTC | fixed filtering by updated date | 14 June 2023, 07:53:54 UTC |
e57b409 | klakhov | 14 June 2023, 07:43:12 UTC | fixed job item styles | 14 June 2023, 07:43:12 UTC |
0daced7 | klakhov | 14 June 2023, 07:37:31 UTC | changed aligns on task page | 14 June 2023, 07:37:31 UTC |
f578e47 | Paweł Kotiuk | 13 June 2023, 18:11:17 UTC | docs: Describe changing default OPA permissions (#6294) Follow up to discussion from: https://github.com/opencv/cvat/issues/6224 This issue is linked with: https://github.com/opencv/cvat/pull/3788 which introduced IAM, but not document some aspects. . | 13 June 2023, 18:11:17 UTC |
e95c0a1 | Kirill Sizov | 13 June 2023, 18:08:26 UTC | Remove max file count (#6292) | 13 June 2023, 18:08:26 UTC |
44bf2da | Anastasia Yasakova | 13 June 2023, 18:06:31 UTC | Codecov report after completion of full CI (#6293) - Added upload to Codecov with token - Codecov report after completion of full CI | 13 June 2023, 18:06:31 UTC |
e8a31b8 | Kirill Lakhov | 13 June 2023, 16:40:09 UTC | Test for exporting annotations into CS folder (#6301) <!-- 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 #6265 ### 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. | 13 June 2023, 16:40:09 UTC |
3b3f9ca | Boris Sekachev | 13 June 2023, 10:57:08 UTC | Accelerated SAM decoder, fixed serverless for EXIF rotated images (#6275) <!-- 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 --> Removed extra interpolation layer ### Motivation and context Fixed #6250 ### 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)) - [ ] 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 June 2023, 10:57:08 UTC |
f87cce5 | Anastasia Yasakova | 13 June 2023, 10:06:28 UTC | Disable failed REST API tests (#6302) | 13 June 2023, 10:06:28 UTC |
8a72d2b | Maxim Zhiltsov | 12 June 2023, 15:05:38 UTC | Merge branch 'develop' into zm/gt-jobs | 12 June 2023, 15:05:38 UTC |
9a600f3 | Maxim Zhiltsov | 12 June 2023, 11:57:14 UTC | Honey pot server (#6204) The server part of #6039 - Added support for Ground Truth jobs in a task - Added support for job creation and removal (only Ground Truth jobs can be created or removed in a task) - Added a component to autocompute quality metrics for a task - Added tests - Fixed https://github.com/opencv/cvat/issues/5971 (both parts - the outside problem and the manifest problem, the manifest part fix is also available in #6216) Co-authored-by: klakhov <kirill.9992@gmail.com> Co-authored-by: Roman Donchenko <roman@cvat.ai> Co-authored-by: Kirill Sizov <kirill.sizov@cvat.ai> | 12 June 2023, 11:57:14 UTC |