Skip to main content

Browse the archive

swh:1:snp:973504f75325e1c705c39106a2685791af62e9e3
sort by:
Revision Author Date Message Commit Date
fa4a200 Andrey Zhavoronkov 18 May 2023, 14:26:19 UTC Merge remote-tracking branch 'origin/master' into release-2.4.4 18 May 2023, 14:26:19 UTC
617dc40 Andrey Zhavoronkov 18 May 2023, 14:22:04 UTC update version in CHANGELOG.md 18 May 2023, 14:22:04 UTC
0805a6d Andrey Zhavoronkov 18 May 2023, 13:56:56 UTC update version 18 May 2023, 14:20:02 UTC
7e619b2 Mariia Acoca 18 May 2023, 14:18:58 UTC Changelog update (#6165) 18 May 2023, 14:18:58 UTC
8ae3ac3 Andrey Zhavoronkov 18 May 2023, 10:05:02 UTC Enable gzip compression for UI assets (#6162) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> before: ![f_gzip_before](https://github.com/opencv/cvat/assets/41117609/a6ed0fd5-26d7-469d-904a-b310cd493b14) after: ![f_gzip_after](https://github.com/opencv/cvat/assets/41117609/3487a5c5-fb96-4eeb-acad-d2209e05721b) ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) ~~- [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 18 May 2023, 10:05:02 UTC
7141f3b Andrey Zhavoronkov 16 May 2023, 17:59:12 UTC Revert "Fix version of postgres image (#6136)" (#6151) This reverts commit 2754504bb291a96b0f7c42783bbbff006a2f47d4. <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Resolved in https://github.com/docker-library/postgres/issues/1076 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch ~~- [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file~~ ~~- [ ] I have updated the documentation accordingly~~ ~~- [ ] I have added tests to cover my changes~~ ~~- [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ ~~- [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com> 16 May 2023, 17:59:12 UTC
6a374b4 Boris Sekachev 16 May 2023, 17:31:06 UTC Fixed area checking for skeleton in case with two points (#6156) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 16 May 2023, 17:31:06 UTC
4eb333e Andrey Zhavoronkov 16 May 2023, 11:10:17 UTC Fix array length check condition (#6154) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 16 May 2023, 11:10:17 UTC
fe78da2 Maria Khrustaleva 15 May 2023, 14:52:19 UTC Update license header for new files (#6152) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 15 May 2023, 14:52:19 UTC
7d21a73 Roman Donchenko 15 May 2023, 14:48:26 UTC Add an option to call Nuclio functions via the dashboard (#6146) Currently, this only happens when running in Kubernetes. This option lets CVAT use Nuclio that's deployed to Kubernetes without being deployed to Kubernetes itself, or just to use Nuclio that is deployed on another machine. 15 May 2023, 14:48:26 UTC
c005d6c Roman Donchenko 15 May 2023, 14:17:54 UTC Fix the CPU HRNet Nuclio function (#6150) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> It was broken for two reasons: * Due to some changes on the PyTorch website, the old way of installing the PyTorch packages now installs the ROCm version rather than the CPU version (and it doesn't work doe to a missing dependency). * The newest version of NumPy doesn't work with HRNet due to the latter's usage of `np.int`. Fix these problems, and in addition, rework the build recipe to avoid installing unneeded packages. Altogether, the changes massively shrink the Docker image size (from ~14 GB to ~2 GB). I didn't update the GPU version, because a) the first issue doesn't affect it, b) the second issue is already fixed in it, and c) I don't have a GPU to test it on. ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> Manual testing with CVAT. ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - ~~[ ] I have updated the documentation accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ - ~~[ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru> 15 May 2023, 14:17:54 UTC
98616c7 Roman Donchenko 15 May 2023, 10:17:03 UTC Modernize OpenVINO-based Nuclio functions and allow them to run on Kubernetes (#6129) Currently, OpenVINO-based functions assume that a local directory will be mounted into the container. In Kubernetes, that isn't possible, so implement an alternate approach: create a separate base image and inherit the function image from it. In addition, implement some modernizations: * Upgrade the version of OpenVINO to the latest (2022.3). Make the necessary updates to the code. Note that 2022.1 introduced an entirely new inference API, but I haven't switched to it yet to minimize changes. * Use the runtime version of the Docker image as the base instead of the dev version. This significantly reduces the size of the final image (by ~3GB). * Replace the `faster_rcnn_inception_v2_coco` model with `faster_rcnn_inception_resnet_v2_atrous_coco`, as the former has been removed from OMZ. * Ditto with `person-reidentification-retail-0300` -> `0277`. * The IRs used in the DEXTR function are not supported by OpenVINO anymore (format too old), so rewrite the build process to create them from the original code/weights instead. 15 May 2023, 10:17:03 UTC
2a41d59 Boris Sekachev 12 May 2023, 15:00:08 UTC Correct destructuring plugins array (#6139) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 12 May 2023, 15:00:08 UTC
2754504 Kirill Sizov 12 May 2023, 13:27:14 UTC Fix version of postgres image (#6136) 12 May 2023, 13:27:14 UTC
0712d7d Boris Sekachev 11 May 2023, 11:05:54 UTC Running SAM backbone on frontend (#6019) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Resolved #5984 Resolved #6049 Resolved #6041 - Compatible only with ``sam_vit_h_4b8939.pth`` weights. Need to re-export ONNX mask decoder with some custom model changes (see below) to support other weights (or just download them using links below) - Need to redeploy the serverless function because its interface has been changed. Decoders for other weights: sam_vit_l_0b3195.pth: [Download](https://drive.google.com/file/d/1Nb5CJKQm_6s1n3xLSZYso6VNgljjfR-6/view?usp=sharing) sam_vit_b_01ec64.pth: [Download](https://drive.google.com/file/d/17cZAXBPaOABS170c9bcj9PdQsMziiBHw/view?usp=sharing) Changes done in ONNX part: ``` git diff scripts/export_onnx_model.py diff --git a/scripts/export_onnx_model.py b/scripts/export_onnx_model.py index 8441258..18d5be7 100644 --- a/scripts/export_onnx_model.py +++ b/scripts/export_onnx_model.py @@ -138,7 +138,7 @@ def run_export( _ = onnx_model(**dummy_inputs) - output_names = ["masks", "iou_predictions", "low_res_masks"] + output_names = ["masks", "iou_predictions", "low_res_masks", "xtl", "ytl", "xbr", "ybr"] with warnings.catch_warnings(): warnings.filterwarnings("ignore", category=torch.jit.TracerWarning) bsekachev@DESKTOP-OTBLK26:~/sam$ git diff segment_anything/utils/onnx.py diff --git a/segment_anything/utils/onnx.py b/segment_anything/utils/onnx.py index 3196bdf..85729c1 100644 --- a/segment_anything/utils/onnx.py +++ b/segment_anything/utils/onnx.py @@ -87,7 +87,15 @@ class SamOnnxModel(nn.Module): orig_im_size = orig_im_size.to(torch.int64) h, w = orig_im_size[0], orig_im_size[1] masks = F.interpolate(masks, size=(h, w), mode="bilinear", align_corners=False) - return masks + masks = torch.gt(masks, 0).to(torch.uint8) + nonzero = torch.nonzero(masks) + xindices = nonzero[:, 3:4] + yindices = nonzero[:, 2:3] + ytl = torch.min(yindices).to(torch.int64) + ybr = torch.max(yindices).to(torch.int64) + xtl = torch.min(xindices).to(torch.int64) + xbr = torch.max(xindices).to(torch.int64) + return masks[:, :, ytl:ybr + 1, xtl:xbr + 1], xtl, ytl, xbr, ybr def select_masks( self, masks: torch.Tensor, iou_preds: torch.Tensor, num_points: int @@ -132,7 +140,7 @@ class SamOnnxModel(nn.Module): if self.return_single_mask: masks, scores = self.select_masks(masks, scores, point_coords.shape[1]) - upscaled_masks = self.mask_postprocessing(masks, orig_im_size) + upscaled_masks, xtl, ytl, xbr, ybr = self.mask_postprocessing(masks, orig_im_size) if self.return_extra_metrics: stability_scores = calculate_stability_score( @@ -141,4 +149,4 @@ class SamOnnxModel(nn.Module): areas = (upscaled_masks > self.model.mask_threshold).sum(-1).sum(-1) return upscaled_masks, scores, stability_scores, areas, masks - return upscaled_masks, scores, masks + return upscaled_masks, scores, masks, xtl, ytl, xbr, ybr ``` ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [x] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 11 May 2023, 11:05:54 UTC
df72796 Mariia Acoca 10 May 2023, 13:35:46 UTC Subscription management (#6086) 10 May 2023, 13:35:46 UTC
a490632 Boris Sekachev 10 May 2023, 13:25:11 UTC Fixed headers on prod (#6123) 10 May 2023, 13:25:11 UTC
5f25a09 Andrey Zhavoronkov 09 May 2023, 16:38:29 UTC Increase lambda requests timeout (#6101) 09 May 2023, 16:38:29 UTC
aa25c97 Andrey Zhavoronkov 09 May 2023, 16:37:19 UTC Fix lambda manager requests visibility (#6116) 09 May 2023, 16:37:19 UTC
546bd40 Boris Sekachev 09 May 2023, 09:39:06 UTC Added test for fit issue (#6117) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Before/after fix execution: ![image](https://user-images.githubusercontent.com/40690378/236913420-6165e7aa-8758-4efd-be8b-825304e92c19.png) ![image](https://user-images.githubusercontent.com/40690378/236913439-862d60a7-1d90-463f-8129-acb5f2727eb9.png) ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 09 May 2023, 09:39:06 UTC
255f2d0 Maxim Zhiltsov 05 May 2023, 13:38:23 UTC Fix completed job count reporting (#6106) - Fixed completed task job count reporting in the task summary - Added a test Fixes #6098 Fixes #6034 05 May 2023, 13:38:23 UTC
8f033b3 Roman Donchenko 05 May 2023, 07:52:47 UTC Ensure that Nuclio function names are valid Kubernetes service names (#6100) 05 May 2023, 07:52:47 UTC
5399f6e Boris Sekachev 01 May 2023, 10:23:52 UTC Fixed fit for images with different resolution (#6081) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 01 May 2023, 10:23:52 UTC
d026dbf Maria Khrustaleva 28 April 2023, 05:43:34 UTC Fix issue azure.core.exceptions.ResourceExistsError: The specified blob already exists. (#6082) 28 April 2023, 05:43:34 UTC
091a035 Andrey Zhavoronkov 26 April 2023, 19:24:15 UTC Increase request body size for TransT tracker (#6073) 26 April 2023, 19:24:15 UTC
269545b Andrey Zhavoronkov 25 April 2023, 15:22:17 UTC develop 2.5.0 (#6070) 25 April 2023, 15:22:17 UTC
8a2c23f Nikita Manovich 25 April 2023, 15:20:58 UTC Release v2.4.3 25 April 2023, 15:20:58 UTC
d2ba56d Andrey Zhavoronkov 25 April 2023, 06:40:25 UTC Fix pylint workflow 25 April 2023, 06:40:25 UTC
da0466d Andrey Zhavoronkov 24 April 2023, 17:47:20 UTC Merge remote-tracking branch 'origin/master' into release-2.4.3 24 April 2023, 17:47:20 UTC
eb15937 Andrey Zhavoronkov 24 April 2023, 17:40:15 UTC Update CHANGELOG.md 24 April 2023, 17:40:15 UTC
8fa0956 Andrey Zhavoronkov 24 April 2023, 17:37:11 UTC Update version 24 April 2023, 17:37:54 UTC
d3d5f9b Andrey Zhavoronkov 24 April 2023, 16:48:45 UTC Set default TUS chunk size from 100 to 2 MB (#6058) 24 April 2023, 16:48:45 UTC
c657c82 Roman Donchenko 21 April 2023, 12:03:11 UTC Dockerfile: build PyAV and its dependencies in a separate stage (#6054) This way, it can be done in parallel with pip fetching all other packages in the main build stage. In practice, I find that the build of PyAV finishes before pip is done downloading, so we basically get it done for free (in terms of time). With this change, I measured a build time of 9:09 (starting from scratch). 21 April 2023, 12:03:11 UTC
157f7e3 Roman Donchenko 20 April 2023, 11:27:02 UTC Implement Python dependency pinning via pip-compile-multi (#6048) This improves the reproducibility of the server build process. Now new versions of dependencies can no longer break the server unless we explicitly upgrade to them. To minimize changes, I did not update any of the version constraints we currently have; however, in the future, we should be able to relax a lot of them. Resolves #5310. 20 April 2023, 11:27:02 UTC
a353497 Roman Donchenko 19 April 2023, 08:40:50 UTC Stop adding package source code into the release Docker images (#6040) The policy that mandated this is no longer relevant now that CVAT is no longer developed by Intel. Moreover, the source code included was not even complete (it didn't contain Python or NPM packages). This saves ~1.6 GB in the unpacked image (and probably a bunch of build time too, but I didn't measure it). 19 April 2023, 08:40:50 UTC
b8cdd4e Roman Donchenko 18 April 2023, 18:35:56 UTC Update Redis and Redis accessories (#6016) This originally started as a security update for redis-py (see <https://github.com/redis/redis-py/releases/tag/v4.5.3>, <https://github.com/redis/redis-py/releases/tag/v4.5.4>). However, I also had to update other Redis-related components because of incompatibilities. * The old version of fakeredis is not compatible with the redis-py 4.x, so I bumped it too. This also allowed me to remove the six workaround. * redis-py 4.1.0 and newer don't support Redis < 5, so I bumped Redis itself in `docker-compose.yml`. Note that the Helm chart is already using Redis 7.0.x. Obsoletes #5946. 18 April 2023, 18:35:56 UTC
65d43aa Roman Donchenko 18 April 2023, 18:31:29 UTC Dockerfile: retain the pip download cache between builds (#6035) This speeds up the build when the entire step can't be cached (e.g. the requirements file changed), but the package list remains mostly the same. The savings are... rather underwhelming, actually. I have observed about a minute in savings, although it obviously depends on the network connection speed. I think this is because pip is inefficient at loading from its own cache (I have observed it loading the entire cached file into memory, for example). Still, savings are savings, and we're getting them basically for free, so why not. Note that I only persist the HTTP cache, and not the wheel cache. That's because any wheels that pip builds could depend on the system packages, and I don't want old wheels to be reused if the system packages change. Also, disable the pip autoupdate checks, which isn't much of an optimization, but it gets rid of some pointless warnings. 18 April 2023, 18:31:29 UTC
ad534b2 Maxim Zhiltsov 17 April 2023, 15:26:28 UTC Refactor server api tests and dataset_manifest (#5997) Extracted from #5083 - Fixed test data placement in tests - Fixed cache cleaning in tests - Refactored server API tests and dataset_manifest - Added more tests 17 April 2023, 15:26:28 UTC
31c1ecc Andrey Zhavoronkov 14 April 2023, 15:58:52 UTC Update the changelog for the next version 2.5.0 (#6031) 14 April 2023, 15:58:52 UTC
b4549f4 Nikita Manovich 14 April 2023, 15:56:47 UTC Merge pull request #6030 from opencv/release-2.4.2 Release v2.4.2 14 April 2023, 15:56:47 UTC
a40deb9 Andrey Zhavoronkov 14 April 2023, 14:47:13 UTC update schema version 14 April 2023, 14:47:13 UTC
883bb23 Andrey Zhavoronkov 14 April 2023, 14:36:20 UTC update schema version 14 April 2023, 14:36:20 UTC
de704ff Andrey Zhavoronkov 14 April 2023, 14:12:11 UTC Update vesrion 14 April 2023, 14:12:11 UTC
d764635 Kirill Sizov 14 April 2023, 13:54:33 UTC Add missing line CHANGELOG.md (#6027) 14 April 2023, 13:54:33 UTC
3717060 Andrey Zhavoronkov 14 April 2023, 13:48:16 UTC Added missed line to changelog (#6029) Update CHANGELOG.md 14 April 2023, 13:48:16 UTC
8a14ce8 Andrey Zhavoronkov 14 April 2023, 13:10:18 UTC Update base imege to ubuntu:22.04 (#6021) Update base image ubuntu 20.04 -> 22.04 update python 3.8 -> 3.10 update sqlite3 from 3.31 -> 3.37 14 April 2023, 13:10:18 UTC
d3bc72b Mariia Acoca 14 April 2023, 13:00:15 UTC Update CHANGELOG.md (#6025) Fix typos in CHANGELOG 14 April 2023, 13:00:15 UTC
dfcb154 Mariia Acoca 14 April 2023, 12:48:30 UTC Update CHANGELOG.md (#6024) Update CHANGELOG.md 14 April 2023, 12:48:30 UTC
1c753d5 Andrey Zhavoronkov 13 April 2023, 12:44:43 UTC Fix tus loading if multiple apache processes are used (#6006) 13 April 2023, 12:44:43 UTC
61adec5 Roman Donchenko 12 April 2023, 12:02:31 UTC Make mild improvements to the main Dockerfile (#5994) This applies several minor improvements that together shave off a little bit of build time (on my machine, it goes down from 14:10 to 13:20) and a little bit of size of the final image (likely just a few megabytes, so I didn't measure it exactly). 12 April 2023, 12:02:31 UTC
10fb2b4 Boris Sekachev 12 April 2023, 09:12:02 UTC Plugins updated in core app (#6000) <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 12 April 2023, 09:12:02 UTC
9cbd510 Boris Sekachev 12 April 2023, 08:11:34 UTC Added Segment Anything interactor for GPU/CPU (#6008) Idea of the PR is to finish this one #5990 Deploy for GPU: ``./deploy_gpu.sh pytorch/facebookresearch/sam/nuclio/`` Deploy for CPU: ``./deploy_cpu.sh pytorch/facebookresearch/sam/nuclio/`` If you want to use GPU, be sure you setup docker for this [guide](https://github.com/NVIDIA/nvidia-docker/blob/master/README.md#quickstart). Resolved issue #5984 But the interface probably can be improved Co-authored-by: Alx-Wo <alexander.wolpert@googlemail.com> 12 April 2023, 08:11:34 UTC
6852cae Nikita Manovich 11 April 2023, 20:06:28 UTC Use PostgreSQL in debug mode (#5999) Fix #5996 We have multiple problems with sqlite on different operation systems. The idea here is to use the same DB in debug and in production. sqlite database is locked errors: - https://www2.sqlite.org/cvstrac/wiki?p=DatabaseIsLocked - https://docs.djangoproject.com/en/4.2/ref/databases/#database-is-locked-errors --------- Co-authored-by: kirill-sizov <sizow.k.d@gmail.com> 11 April 2023, 20:06:28 UTC
14dc68e Nikita Manovich 11 April 2023, 05:21:17 UTC Optimized jobs request (#5962) 11 April 2023, 05:21:17 UTC
c5156f4 Kirill Sizov 10 April 2023, 19:07:16 UTC Verifying API schema before running tests (#5998) 10 April 2023, 19:07:16 UTC
2505b31 Roman Donchenko 10 April 2023, 18:26:12 UTC SDK: fix urllib3 deprecation warnings (#6002) `HTTPResponse.getheader` and `getheaders` are slated to be removed in urllib3 2.1.0. 10 April 2023, 18:26:12 UTC
0c853b1 Maxim Zhiltsov 09 April 2023, 05:46:22 UTC Fix version checks in SDK (#5991) - Added missing compatibility with micro- and smaller releases 09 April 2023, 05:46:22 UTC
7a7267d Anastasia Yasakova 07 April 2023, 10:30:27 UTC Update REST API tests documentation (#5993) 07 April 2023, 10:30:27 UTC
7cff867 Kirill Sizov 07 April 2023, 09:20:05 UTC Refactor webhooks (#5916) This PR fixes the following problems: - #5631 - This will allow webhooks to be sent not only when an explicit request has been sent to the server. Co-authored-by: Nikita Manovich <nikita@cvat.ai> Co-authored-by: yasakova-anastasia <anastasia@cvat.ai> Co-authored-by: Roman Donchenko <roman@cvat.ai> 07 April 2023, 09:20:05 UTC
37427bb Nikita Manovich 06 April 2023, 19:00:21 UTC Merge branch 'develop' of https://github.com/opencv/cvat into develop 06 April 2023, 19:00:21 UTC
c04bd1d Maxim Zhiltsov 06 April 2023, 16:39:04 UTC Fix write once fields (#5975) This PR fixes a problem with WriteOnceSerializer that it affected only the fields declared in the `Meta.fields`, while the manually declared fields were left unaffected. This PR also fixes several issues with invalid field declarations. 06 April 2023, 16:39:04 UTC
14fa0c6 Nikita Manovich 06 April 2023, 15:12:25 UTC Merge branch 'master' into develop 06 April 2023, 15:12:25 UTC
7c00f5e Andrey Zhavoronkov 06 April 2023, 14:47:24 UTC Disable OPA container logs (#5988) OPA currently logs every request to the console and this results in huge docker log files. I don't think these logs can be useful for enabling docker-level log size limits. 06 April 2023, 14:47:24 UTC
b55471a Anastasia Yasakova 06 April 2023, 14:27:01 UTC Remove default containers rebuild when running REST API tests (#5989) 06 April 2023, 14:27:01 UTC
57b8766 Roman Donchenko 06 April 2023, 13:28:18 UTC Remove the tus chunk endpoints from the schema (#5961) As explained in the comment in `_tus_chunk_action`, I don't think we need explicit documentation for these endpoints. Hiding them makes the documentation a bit cleaner, especially because these endpoints were indistinguishable from one another. It also removes the corresponding SDK code, which is good, since clients should follow the URL returned by the creation endpoint, not invoke the chunk endpoints directly. 06 April 2023, 13:28:18 UTC
5203119 Roman Donchenko 06 April 2023, 08:46:13 UTC Bump the version of ts-jest to support TypeScript 5 (#5981) <!-- 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. --> After 40232858, the JavaScript tests print a warning about TypeScript 5 not being supported. This fixes it. ### 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. --> Running the JS 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. 06 April 2023, 08:46:13 UTC
c49ca71 Boris Sekachev 05 April 2023, 19:56:29 UTC Fixed rotation is lost during changing a mutable attribute (#5968) <!-- 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 #5966 ### 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 - [x] I have added tests to cover my changes - [x] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: Nikita Manovich <nikita@cvat.ai> 05 April 2023, 19:56:29 UTC
a7f7ff1 Nikita Manovich 05 April 2023, 18:36:22 UTC Merge pull request #5980 from opencv/hotfix-2.4.1 Hotfix for v2.4.0 -> Release v2.4.1 05 April 2023, 18:36:22 UTC
209b5b6 Andrey Zhavoronkov 05 April 2023, 12:50:44 UTC Fix working time calculation (#5973) 05 April 2023, 17:13:13 UTC
8f2de46 Nikita Manovich 05 April 2023, 17:07:18 UTC Updated versions, clenaup the changelog. 05 April 2023, 17:07:18 UTC
3216bd3 Boris Sekachev 05 April 2023, 16:53:44 UTC Tried to optimize annotation fetching (#5974) 05 April 2023, 17:00:41 UTC
791d93f Boris Sekachev 05 April 2023, 16:53:44 UTC Tried to optimize annotation fetching (#5974) 05 April 2023, 16:53:44 UTC
2090a3c Andrey Zhavoronkov 05 April 2023, 12:50:44 UTC Fix working time calculation (#5973) 05 April 2023, 12:50:44 UTC
a7fc12d Andrey Zhavoronkov 05 April 2023, 08:47:10 UTC Added queue for notifications (#5964) 05 April 2023, 08:47:10 UTC
2709802 Maxim Zhiltsov 04 April 2023, 22:59:25 UTC Fix cloud storage permissions (#5956) 04 April 2023, 22:59:25 UTC
a20d631 Maxim Zhiltsov 04 April 2023, 12:37:29 UTC Add descriptions to the tasks data API (#5945) - Added descriptions for the server task data API fields - Fixed docs 04 April 2023, 12:37:29 UTC
8efeac8 Nikita Manovich 04 April 2023, 11:00:47 UTC Updated codeowners for CVAT repository (#5965) 04 April 2023, 11:00:47 UTC
fe1b167 Boris Sekachev 04 April 2023, 11:00:16 UTC Fixed minor exception (#5967) - Pressing "Backward" from the first frame "Forward" from the latest frame causes exception: <img width="398" alt="image" src="https://user-images.githubusercontent.com/40690378/229714029-7978c25f-0ec6-418c-a06b-7ea03541cd25.png"> It does not affect users, but just causes extra exceptions to console. 04 April 2023, 11:00:16 UTC
c4c799b Boris Sekachev 04 April 2023, 10:05:55 UTC Updated cypress command to return created org id (#5969) <!-- 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 Intuitively, it is right that cypress command to create a resource, should return some resource information, like id. We are using it in our production tests. ### How has this been tested? N/A ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 04 April 2023, 10:05:55 UTC
956529c Nikita Manovich 31 March 2023, 19:22:38 UTC Added silk into development configuration by default (#5958) 31 March 2023, 19:22:38 UTC
2f873fa Andrey Zhavoronkov 31 March 2023, 10:40:41 UTC Reduce deletion time of task and projects (#5926) 31 March 2023, 10:40:41 UTC
dca6360 Anastasia Yasakova 31 March 2023, 07:43:11 UTC Add a test for mask conversion in lambda functions (#5950) Added test for #5877 31 March 2023, 07:43:11 UTC
dd10301 Roman Donchenko 31 March 2023, 07:36:37 UTC Synchronize the versions of jest and jest-config (#5957) This gets rid of a whole bunch of duplicate transitive dependencies. 31 March 2023, 07:36:37 UTC
5bd3013 Anastasia Yasakova 30 March 2023, 13:41:02 UTC Fix points missing when exporting tracked skeleton (#5914) Fixed #5497 30 March 2023, 13:41:02 UTC
cbda853 Roman Donchenko 29 March 2023, 17:40:01 UTC URL-escape the filter in the generated URLs (#5941) Or rather, just don't needlessly unescape it. <!-- 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 #5566. ### 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. --> Cypress test. ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [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~~ - [x] I have added tests to cover my changes - [x] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 29 March 2023, 17:40:01 UTC
a9e8225 Maxim Zhiltsov 29 March 2023, 11:20:26 UTC Fix SDK documentation problems (#5903) Resolves #5871 Related: https://github.com/opencv/cvat/issues/5847, https://github.com/opencv/cvat/issues/5814 This PR makes SDK examples valid Python code and adds some missing info. - Fixed incorrect method names in examples - Added missing `api_client.` use in method examples - Fixed invalid return types in examples - Fixed imports in examples - Added notes about binary files in low-level API, extra method args and returned values - Removed html escapes from method and field descriptions - Changed function signatures to be closer to the most popular variants 29 March 2023, 11:20:26 UTC
409fac5 Roman Donchenko 29 March 2023, 09:58:04 UTC Remove support for redundant request media types in the API (#5874) Currently, every API endpoint that takes a request body supports (or at least declares to support) 4 media types: * `application/json` * `application/offset+octet-stream` * `application/x-www-form-urlencoded` * `multipart/form-data` Supporting multiple media types has a cost. We need to test that the various media types actually work, and we need to document their use (e.g., providing examples for each supported type). In practice, we mostly don't... but we still need to. In addition, the user, seeing the list of supported types, has to decide which one to use. Now, the cost could be worthwhile if the multiple type support provided value. However, for the most part, it doesn't: * `application/offset+octet-stream` only makes sense for the TUS endpoints. Moreover, for those endpoints it's the only type that makes sense. * `application/x-www-form-urlencoded` is strictly inferior to JSON. It doesn't support compound values, and it doesn't carry type information, so you can't, for example, distinguish a string from a null. It's potentially susceptible to CSRF attacks (we have protections against those, but we could accidentally disable them and not notice). Its main use is for form submissions, but we don't use HTML-based submissions. * `multipart/form-data` shares the downsides of `application/x-www-form-urlencoded`, however it does have a redeeming quality: it allows to efficiently upload binary files. Therefore, it has legitimate uses in endpoints that accept such files. Therefore, I believe it is justified to reduce the API surface area as follows: * Restrict `application/offset+octet-stream` to TUS endpoints and remove support for other types from those endpoints. * Remove `application/x-www-form-urlencoded` support entirely. * Restrict `multipart/form-data` support to endpoints dealing with file uploads. Note that I had to keep `multipart/form-data` support for `POST /api/cloudstorages` and `PATCH /api/cloudstorages/<id>`. That's because they accept a file-type parameter (`key_file`). I don't especially like this. Key files are not big, so the efficiency benefits of `multipart/form-data` don't matter. Therefore, I don't think we really need to support this type here; it would be more elegant to just use JSON and Base64-encode the key file contents. However, I don't have time to make that change right now, so I'm leaving it for another time. 29 March 2023, 09:58:04 UTC
ce63565 Anastasia Yasakova 28 March 2023, 19:50:14 UTC Fix export of a job from a task with multiple jobs (#5928) Fixed #5927 28 March 2023, 19:50:14 UTC
c988357 Mariia Acoca 28 March 2023, 19:46:58 UTC minor documentation fixes (#5932) 28 March 2023, 19:46:58 UTC
0a9881f Maxim Zhiltsov 28 March 2023, 19:36:36 UTC Fix formatting script (#5944) 28 March 2023, 19:36:36 UTC
8f64f62 Kirill Lakhov 28 March 2023, 12:45:47 UTC Fix empty model list after adding a model (#5947) <!-- 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. 28 March 2023, 12:45:47 UTC
defb86c Maria Khrustaleva 28 March 2023, 10:03:30 UTC Refactor import/export tests (#5782) 28 March 2023, 10:03:30 UTC
0bbf587 Roman Donchenko 28 March 2023, 07:04:34 UTC CI: run ESLint on all files, not just changed ones (#5720) <!-- 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 --> Also, remove a redundant dependency. ### 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 guarantees that no errors can appear in the repository due to non-code changes, such as changes to the ESLint version or configuration. ### 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. --> `yarn run eslint .` ### 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> Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru> 28 March 2023, 07:04:34 UTC
afe931c Bassel Mahmoud 27 March 2023, 13:41:16 UTC Fix Yolov7 nuctl function deploy failure (#5731) - adds wget installation to build directives in yolov7 function-gpu.yaml - the deployment fails because it tries to download the onnx model using wget, but is not installed in the base image ultralytics/yolov5:latest ### Motivation and context Fix issue #5730 27 March 2023, 13:41:16 UTC
79c3fbc Roman Donchenko 27 March 2023, 13:30:42 UTC Resolve migration conflict (#5939) Merging both #4649 and #5855 broke migrations. 27 March 2023, 13:30:42 UTC
c156dc6 Roman Donchenko 27 March 2023, 12:00:09 UTC Bump Python dependency versions (#5938) While testing the development environment setup instructions in #5889, I found that some of the Python packages have problems with installing on newer Linuxes. Fortunately, most such problems can be resolved by bumping the versions: * `psycopg2-binary` to enable support for Python 3.10+ (the current version does work with these Pythons, but it doesn't have prebuilt wheels for them). * `python-ldap` to enable support for OpenLDAP 2.5+ (on systems that don't include a compatibility `libldap_r.so` symlink, like Arch). 27 March 2023, 12:00:09 UTC
a3cda6c PMazarovich 27 March 2023, 09:46:51 UTC Git sync fix (#5776) Currently when user try to open the task with git repository connected he will see this (screenshot) ![2023-02-27_17-01](https://user-images.githubusercontent.com/57707673/221584442-329c8592-6524-4715-9c76-7631553dc135.png) This happens after first synchronization and reloading the page. The cause of this is ssh-agent, that is not running in cvat_server container. This PR will enable ssh-agent on cvat_server so this issue disappears. 27 March 2023, 09:46:51 UTC
c60053d Maria Khrustaleva 27 March 2023, 09:43:19 UTC Fix multiple GCS creation when GOOGLE_APPLICATION_CREDENTIALS is used (#5855) Fix https://github.com/opencv/cvat/issues/5800 Fix https://github.com/opencv/cvat/issues/4533 27 March 2023, 09:43:19 UTC
23f946f Roman Donchenko 27 March 2023, 08:40:48 UTC Update to `actions/setup-python` v4 (#5934) v3 uses the `set-output` command, which will stop working on June 1st. 27 March 2023, 08:40:48 UTC
1ae7a34 Roman Donchenko 27 March 2023, 08:39:53 UTC Fix most discrepancies between the different ways of generating the API schema (#5889) Currently, if you try to generate the API schema with the VS Code launch configuration, it'll remove the `minimum` and `maximum` attributes from the definition of some of the integer fields. This is because those attributes come from the configured database engine in use. The "canonical" version of the schema is generated from the Docker image, which uses the production configuration, and thus PostgreSQL; while using the VS Code launch configuration will default to the development configuration, and thus SQLite. Fix it by aligning the configurations. Since ultimately, the schema is for the production version of the server, override the configuration to production for the VS Code launch configuration. Note that there's one more discrepancy that remains; that of the API version number. I haven't figured out the best way to fix that yet. 27 March 2023, 08:39:53 UTC
back to top