Skip to main content

Browse the archive

swh:1:snp:973504f75325e1c705c39106a2685791af62e9e3
sort by:
Revision Author Date Message Commit Date
2d2e695 Mariia Acoca 28 July 2023, 13:02:27 UTC Update analytics-cloud.md 28 July 2023, 13:02:27 UTC
d85db57 Mariia Acoca 28 July 2023, 12:56:36 UTC analytics 28 July 2023, 12:56:36 UTC
3e84570 Roman Donchenko 27 July 2023, 10:13:16 UTC Stop creating linter report files in CI (#6560) Currently, when one of the linters reports a problem, if you want to see what that problem is, you have to do the following: 1. Click on the "Details" link in the PR. 2. Click "Summary". 3. Click the artifact (also, depending on the browser, choose where to save it). 4. Open the downloaded file (which is an archive). 5. Open the report file from the archive. 6. Delete the archive after you're done. That is far too much hassle, and all it gives you is a slightly fancier- looking report (and sometimes not even that, like in the case of black). So just remove all the report building and uploading. Now the above procedure is reduced to: 1. Click "Details". 2. Expand the appropriate build step. 27 July 2023, 10:13:16 UTC
5a69e67 Boris Sekachev 25 July 2023, 11:05:25 UTC Fixed cards on project page, updated stylelint & css loader packages (#6551) <!-- 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 #5615 Area is scrollable now. ![image](https://github.com/opencv/cvat/assets/40690378/1f9b4b38-2a00-4632-ada0-3fe9cfbafdc2) ### 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. 25 July 2023, 11:05:25 UTC
2bb87cf Michael Kirpichev 25 July 2023, 09:48:52 UTC multiple fixes to make helm work (#6137) <!-- 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. --> Right now helm chart is broken and not usable at least in my environment, I trying to fix it to make it work content: 1. Moved test-related values to another values.file to separate it from default config 2. fixed issue with multiple caches in same RWX volume, which prevents db migration to start 3. Removed hardcoded mandatory traefik ingress usage 4. Added confugurable default storage option to chart ### 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. --> We test it on our AKS with RWX volume ### 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 - [x] 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. closes #6043 closes #6096 closes #5733 --------- Co-authored-by: Michael Kirpichev <m.kirpichev@haut.ai> Co-authored-by: Nikita Manovich <nikita@cvat.ai> Co-authored-by: Andrey Zhavoronkov <andrey@cvat.ai> 25 July 2023, 09:48:52 UTC
a79052f Kirill Lakhov 25 July 2023, 09:21:55 UTC Project/Task/Job Analytics (#6371) 25 July 2023, 09:21:55 UTC
d72e954 Andrey Zhavoronkov 24 July 2023, 16:17:13 UTC Fix BrowsableAPIRenderer for server viewset (#6553) <!-- 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 #6550 <!-- 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. --> ```python ERROR:django.request:Internal Server Error: /api/server/annotation/formats Traceback (most recent call last): File "/home/andrey/workspace/cvat.ai/cvat/.env/lib/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/home/andrey/workspace/cvat.ai/cvat/.env/lib/python3.10/site-packages/django/core/handlers/base.py", line 220, in _get_response response = response.render() File "/home/andrey/workspace/cvat.ai/cvat/.env/lib/python3.10/site-packages/django/template/response.py", line 114, in render self.content = self.rendered_content File "/home/andrey/workspace/cvat.ai/cvat/.env/lib/python3.10/site-packages/rest_framework/response.py", line 70, in rendered_content ret = renderer.render(self.data, accepted_media_type, context) File "/home/andrey/workspace/cvat.ai/cvat/.env/lib/python3.10/site-packages/rest_framework/renderers.py", line 723, in render context = self.get_context(data, accepted_media_type, renderer_context) File "/home/andrey/workspace/cvat.ai/cvat/.env/lib/python3.10/site-packages/rest_framework/renderers.py", line 697, in get_context 'options_form': self.get_rendered_html_form(data, view, 'OPTIONS', request), File "/home/andrey/workspace/cvat.ai/cvat/.env/lib/python3.10/site-packages/rest_framework/renderers.py", line 475, in get_rendered_html_form if not self.show_form_for_method(view, method, request, instance): File "/home/andrey/workspace/cvat.ai/cvat/.env/lib/python3.10/site-packages/rest_framework/renderers.py", line 432, in show_form_for_method view.check_object_permissions(request, obj) File "/home/andrey/workspace/cvat.ai/cvat/.env/lib/python3.10/site-packages/rest_framework/views.py", line 345, in check_object_permissions if not permission.has_object_permission(request, self, obj): File "/home/andrey/workspace/cvat.ai/cvat/cvat/apps/iam/permissions.py", line 2015, in has_object_permission return self.check_permission(request, view, obj) File "/home/andrey/workspace/cvat.ai/cvat/cvat/apps/iam/permissions.py", line 1990, in check_permission iam_context = get_iam_context(request, obj) File "/home/andrey/workspace/cvat.ai/cvat/cvat/apps/iam/permissions.py", line 88, in get_iam_context organization = get_organization(request, obj) File "/home/andrey/workspace/cvat.ai/cvat/cvat/apps/iam/permissions.py", line 68, in get_organization raise exc File "/home/andrey/workspace/cvat.ai/cvat/cvat/apps/iam/permissions.py", line 61, in get_organization organization_id = getattr(obj, 'organization_id') AttributeError: 'dict' object has no attribute 'organization_id' ```` ### 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. --> ```terminal curl --header "Accept: text/html" --user "user:pass" http://localhost:8080/api/server/annotation/formats ``` ### 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)) - [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. 24 July 2023, 16:17:13 UTC
6e5ac4b Kirill Sizov 24 July 2023, 12:50:24 UTC Fix keyframe removing (#6494) Steps to reproduce this bug: Create a track that starts on the frame i and has keyframe on the frame j (i < j) Save Remove the keyframe for the created track on the frame i Save 24 July 2023, 12:50:24 UTC
2896bec Boris Sekachev 24 July 2023, 06:33:49 UTC Accelerated React rendering of objects list for tracks (#6544) <!-- 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. 24 July 2023, 06:33:49 UTC
1bc7767 Roman Donchenko 23 July 2023, 19:59:28 UTC generate_image_file: don't hardcode the file format (#6538) It doesn't make much sense to encode the image as JPEG if the given file name is "image.png". Instead, let PIL select the format based on the requested file name. 23 July 2023, 19:59:28 UTC
9659f82 Maxim Zhiltsov 21 July 2023, 16:25:49 UTC Extend cleaning for downloaded file names (#6492) Control characters in filenames may conflict with the Content-Disposition header value restrictions, as it needs to include the downloaded file name. The problem is that many tools (including sendfile) just check for ascii/unicode conversion, while there are also ascii chars that can't be used. Ref: RFC 8178 This PR adds extra cleanup for downloaded file names. Added a custom replacement for the sendfile() function 21 July 2023, 16:25:49 UTC
be81d28 Mariia Acoca 21 July 2023, 10:16:27 UTC automatic annotation documentation updated (#6409) 21 July 2023, 10:16:27 UTC
ded24ad Boris Sekachev 21 July 2023, 09:34:49 UTC Added e2e test to check export hash (#6532) <!-- 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 Depends on #6529 ### 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. 21 July 2023, 09:34:49 UTC
fea0dae Boris Sekachev 21 July 2023, 05:11:13 UTC Adjusted plugin registration way (#6533) 21 July 2023, 05:11:13 UTC
1da005c Boris Sekachev 20 July 2023, 16:11:26 UTC Added default value test, refactored tests (#6529) <!-- 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. 20 July 2023, 16:11:26 UTC
791604a Andrey Zhavoronkov 20 July 2023, 12:13:07 UTC Minor CI improvements (#6527) Disable silk profiler for unit tests, adjust disk utilization threshold for rest tests 20 July 2023, 12:13:07 UTC
123a86c Boris Sekachev 20 July 2023, 12:11:34 UTC Fixed hash for shapes, tags and skeletons (#6517) <!-- 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. 20 July 2023, 12:11:34 UTC
e379444 Roman Donchenko 20 July 2023, 11:36:54 UTC Fix validation in `AttributeSerializer` (#6447) The current implementation of `to_internal_value` doesn't call the base class method, which is supposed to carry out generic validation of serializer fields. This means that we essentially don't validate attribute fields beyond what is done incidentally by database contraints. Fix it by removing the overridden method entirely, and adding a special field class for the `values` field. 20 July 2023, 11:36:54 UTC
98adeb8 dependabot[bot] 20 July 2023, 10:03:39 UTC Bump word-wrap from 1.2.3 to 1.2.4 (#6518) Bumps [word-wrap](https://github.com/jonschlinkert/word-wrap) from 1.2.3 to 1.2.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jonschlinkert/word-wrap/releases">word-wrap's releases</a>.</em></p> <blockquote> <h2>1.2.4</h2> <h2>What's Changed</h2> <ul> <li>Remove default indent by <a href="https://github.com/mohd-akram"><code>@​mohd-akram</code></a> in <a href="https://redirect.github.com/jonschlinkert/word-wrap/pull/24">jonschlinkert/word-wrap#24</a></li> <li>🔒fix: CVE 2023 26115 (2) by <a href="https://github.com/OlafConijn"><code>@​OlafConijn</code></a> in <a href="https://redirect.github.com/jonschlinkert/word-wrap/pull/41">jonschlinkert/word-wrap#41</a></li> <li>:lock: fix: CVE-2023-26115 by <a href="https://github.com/aashutoshrathi"><code>@​aashutoshrathi</code></a> in <a href="https://redirect.github.com/jonschlinkert/word-wrap/pull/33">jonschlinkert/word-wrap#33</a></li> <li>chore: publish workflow by <a href="https://github.com/OlafConijn"><code>@​OlafConijn</code></a> in <a href="https://redirect.github.com/jonschlinkert/word-wrap/pull/42">jonschlinkert/word-wrap#42</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/mohd-akram"><code>@​mohd-akram</code></a> made their first contribution in <a href="https://redirect.github.com/jonschlinkert/word-wrap/pull/24">jonschlinkert/word-wrap#24</a></li> <li><a href="https://github.com/OlafConijn"><code>@​OlafConijn</code></a> made their first contribution in <a href="https://redirect.github.com/jonschlinkert/word-wrap/pull/41">jonschlinkert/word-wrap#41</a></li> <li><a href="https://github.com/aashutoshrathi"><code>@​aashutoshrathi</code></a> made their first contribution in <a href="https://redirect.github.com/jonschlinkert/word-wrap/pull/33">jonschlinkert/word-wrap#33</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/jonschlinkert/word-wrap/compare/1.2.3...1.2.4">https://github.com/jonschlinkert/word-wrap/compare/1.2.3...1.2.4</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/f64b188c7261d26b99e1e2075d6b12f21798e83a"><code>f64b188</code></a> run verb to generate README</li> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/03ea08256ba0c8e8b02b1b304f0f5bd2b1863207"><code>03ea082</code></a> Merge pull request <a href="https://redirect.github.com/jonschlinkert/word-wrap/issues/42">#42</a> from jonschlinkert/chore/publish-workflow</li> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/420dce9a2412b21881202b73a3c34f0edc53cb2e"><code>420dce9</code></a> Merge pull request <a href="https://redirect.github.com/jonschlinkert/word-wrap/issues/41">#41</a> from jonschlinkert/fix/CVE-2023-26115-2</li> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/bfa694edf55bb84ff84512f13da6d68bf7593f06"><code>bfa694e</code></a> Update .github/workflows/publish.yml</li> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/ace0b3c78f81aaf43040bab3bc91d3c5546d3fd2"><code>ace0b3c</code></a> chore: bump version to 1.2.4</li> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/6fd727594676f3e1b196b08a320908bec2f4ca02"><code>6fd7275</code></a> chore: add publish workflow</li> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/30d6daf60fce429f5f559252fa86ee78200652c4"><code>30d6daf</code></a> chore: fix test</li> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/655929cabea6299dddf3b4a21fc3713fca701b48"><code>655929c</code></a> chore: remove package-lock</li> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/49e08bbc32a84da5d79e6b7e0fa74ff6217f6d81"><code>49e08bb</code></a> chore: added an additional testcase</li> <li><a href="https://github.com/jonschlinkert/word-wrap/commit/9f626935f3fac6ec0f3c4b26baea4eb9740d9645"><code>9f62693</code></a> fix: cve 2023-26115</li> <li>Additional commits viewable in <a href="https://github.com/jonschlinkert/word-wrap/compare/1.2.3...1.2.4">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=word-wrap&package-manager=npm_and_yarn&previous-version=1.2.3&new-version=1.2.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/opencv/cvat/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 20 July 2023, 10:03:39 UTC
54d2ef3 Andrey Zhavoronkov 20 July 2023, 09:49:31 UTC Update develop (release 2.5.1) (#6521) <!-- 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.sekachev@yandex.ru> Co-authored-by: Nikita Manovich <nikita@cvat.ai> 20 July 2023, 09:49:31 UTC
c230395 Maxim Zhiltsov 20 July 2023, 07:37:56 UTC Fix job minutes in dates (#6519) <!-- 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 #6508 https://momentjscom.readthedocs.io/en/latest/moment/04-displaying/01-format/ - Fixed invalid format token for minutes in job-item dates ### 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. 20 July 2023, 07:37:56 UTC
1ef561a Boris Sekachev 19 July 2023, 12:28:36 UTC Fixed SAM plugin (403 code for workers in organizations) (#6514) <!-- 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 #6221 ### 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. --------- Co-authored-by: Kirill Sizov <kirill.sizov@cvat.ai> 19 July 2023, 12:28:36 UTC
f861aef Boris Sekachev 19 July 2023, 12:25:12 UTC Fixed default value for an attribute (RAW editor), refactored labels editor (#6474) <!-- 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 #6415 Related #3113 (need to fix server part and probably throw code 400, not 500) Related #2927 (need to fix server) ![image](https://github.com/opencv/cvat/assets/40690378/016f9def-bd5f-4dcf-9a00-c6b75b0dd50f) ### 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. 19 July 2023, 12:25:12 UTC
8de7722 Boris Sekachev 19 July 2023, 12:23:21 UTC Fixed using initial frame from query parameter (#6506) <!-- 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 #6505 ### 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. 19 July 2023, 12:23:21 UTC
19fefc5 Boris Sekachev 19 July 2023, 12:22:21 UTC Fixed calculating statistics in case with removed frames (#6493) <!-- 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)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. 19 July 2023, 12:22:21 UTC
783c414 Andrey Zhavoronkov 19 July 2023, 04:06:40 UTC Close av contaner after use (#6501) 19 July 2023, 04:06:40 UTC
bc5036f Roman Donchenko 18 July 2023, 14:58:00 UTC Create cvat_sdk.datasets, a framework-agnostic version of cvat_sdk.pytorch (#6428) The new `TaskDataset` class provides conveniences like per-frame annotations, bulk data downloading, and caching without forcing a dependency on PyTorch (and somewhat awkwardly conforming to the PyTorch dataset interface). It also provides a few extra niceties, like easy access to labels and original frame numbers. Note that it's called `TaskDataset` rather than `TaskVisionDataset`, as my plan is to keep it domain-agnostic. The `MediaElement` class is extensible, and we can add, for example, support for point clouds, by adding another `load_*` method. There is currently no `ProjectDataset` equivalent, although one could (and probably should) be added later. If we add one, we should probably also add a `task_id` field to `Sample`. 18 July 2023, 14:58:00 UTC
9fc6b00 Kirill Sizov 18 July 2023, 13:02:13 UTC No helm tests on edit (#6495) Duplicate https://github.com/opencv/cvat/pull/6373 for Helm tests 18 July 2023, 13:02:13 UTC
60b925a Boris Sekachev 18 July 2023, 12:28:36 UTC Fixed: 3d job can not be opened in validation mode (#6507) <!-- 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 #6383 ### 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. 18 July 2023, 12:28:36 UTC
bf3e31d Kirill Sizov 18 July 2023, 08:19:49 UTC Add error message (#6500) ### Motivation and context When users try to backup a task with cloud storage data they get such error: ![Screenshot from 2023-07-18 09-21-18](https://github.com/opencv/cvat/assets/43179655/a6e4ed09-8fb5-4ebb-a5e3-72b95d9aa195) And after that, they have no idea what's wrong with this task and why they cannot backup 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. --> ### 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. 18 July 2023, 08:19:49 UTC
1531f86 Kirill Sizov 17 July 2023, 11:29:46 UTC Update codeowners (#6489) <!-- 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. 17 July 2023, 11:29:46 UTC
99a6cf9 Roman Donchenko 14 July 2023, 09:16:51 UTC Bump Hadolint version (#6478) 14 July 2023, 09:16:51 UTC
0715ec0 dependabot[bot] 13 July 2023, 05:34:53 UTC Bump semver from 5.7.1 to 5.7.2 (#6453) [//]: # (dependabot-start) ⚠️ **Dependabot is rebasing this PR** ⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps [semver](https://github.com/npm/node-semver) from 5.7.1 to 5.7.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/npm/node-semver/releases">semver's releases</a>.</em></p> <blockquote> <h2>v5.7.2</h2> <h2><a href="https://github.com/npm/node-semver/compare/v5.7.1...v5.7.2">5.7.2</a> (2023-07-10)</h2> <h3>Bug Fixes</h3> <ul> <li><a href="https://github.com/npm/node-semver/commit/2f8fd41487acf380194579ecb6f8b1bbfe116be0"><code>2f8fd41</code></a> <a href="https://redirect.github.com/npm/node-semver/pull/585">#585</a> better handling of whitespace (<a href="https://redirect.github.com/npm/node-semver/issues/585">#585</a>) (<a href="https://github.com/joaomoreno"><code>@​joaomoreno</code></a>, <a href="https://github.com/lukekarrys"><code>@​lukekarrys</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/npm/node-semver/blob/v5.7.2/CHANGELOG.md">semver's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/npm/node-semver/compare/v5.7.1...v5.7.2">5.7.2</a> (2023-07-10)</h2> <h3>Bug Fixes</h3> <ul> <li><a href="https://github.com/npm/node-semver/commit/2f8fd41487acf380194579ecb6f8b1bbfe116be0"><code>2f8fd41</code></a> <a href="https://redirect.github.com/npm/node-semver/pull/585">#585</a> better handling of whitespace (<a href="https://redirect.github.com/npm/node-semver/issues/585">#585</a>) (<a href="https://github.com/joaomoreno"><code>@​joaomoreno</code></a>, <a href="https://github.com/lukekarrys"><code>@​lukekarrys</code></a>)</li> </ul> <h2>5.7</h2> <ul> <li>Add <code>minVersion</code> method</li> </ul> <h2>5.6</h2> <ul> <li>Move boolean <code>loose</code> param to an options object, with backwards-compatibility protection.</li> <li>Add ability to opt out of special prerelease version handling with the <code>includePrerelease</code> option flag.</li> </ul> <h2>5.5</h2> <ul> <li>Add version coercion capabilities</li> </ul> <h2>5.4</h2> <ul> <li>Add intersection checking</li> </ul> <h2>5.3</h2> <ul> <li>Add <code>minSatisfying</code> method</li> </ul> <h2>5.2</h2> <ul> <li>Add <code>prerelease(v)</code> that returns prerelease components</li> </ul> <h2>5.1</h2> <ul> <li>Add Backus-Naur for ranges</li> <li>Remove excessively cute inspection methods</li> </ul> <h2>5.0</h2> <ul> <li>Remove AMD/Browserified build artifacts</li> <li>Fix ltr and gtr when using the <code>*</code> range</li> <li>Fix for range <code>*</code> with a prerelease identifier</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/npm/node-semver/commit/f8cc313550691a50d9662d8c94f0c033717efd7d"><code>f8cc313</code></a> chore: release 5.7.2</li> <li><a href="https://github.com/npm/node-semver/commit/2f8fd41487acf380194579ecb6f8b1bbfe116be0"><code>2f8fd41</code></a> fix: better handling of whitespace (<a href="https://redirect.github.com/npm/node-semver/issues/585">#585</a>)</li> <li><a href="https://github.com/npm/node-semver/commit/deb5ad51bf58868fa243c1683775305fe9e0e365"><code>deb5ad5</code></a> chore: <code>@​npmcli/template-oss</code><a href="https://github.com/4"><code>@​4</code></a>.16.0</li> <li>See full diff in <a href="https://github.com/npm/node-semver/compare/v5.7.1...v5.7.2">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~lukekarrys">lukekarrys</a>, a new releaser for semver since your current version.</p> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=semver&package-manager=npm_and_yarn&previous-version=5.7.1&new-version=5.7.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/opencv/cvat/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 13 July 2023, 05:34:53 UTC
573d57c dependabot[bot] 13 July 2023, 05:34:12 UTC Bump semver from 6.3.0 to 6.3.1 in /tests (#6452) Bumps [semver](https://github.com/npm/node-semver) from 6.3.0 to 6.3.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/npm/node-semver/releases">semver's releases</a>.</em></p> <blockquote> <h2>v6.3.1</h2> <h2><a href="https://github.com/npm/node-semver/compare/v6.3.0...v6.3.1">6.3.1</a> (2023-07-10)</h2> <h3>Bug Fixes</h3> <ul> <li><a href="https://github.com/npm/node-semver/commit/928e56d21150da0413a3333a3148b20e741a920c"><code>928e56d</code></a> <a href="https://redirect.github.com/npm/node-semver/pull/591">#591</a> better handling of whitespace (<a href="https://redirect.github.com/npm/node-semver/issues/591">#591</a>) (<a href="https://github.com/lukekarrys"><code>@​lukekarrys</code></a>, <a href="https://github.com/joaomoreno"><code>@​joaomoreno</code></a>, <a href="https://github.com/nicolo-ribaudo"><code>@​nicolo-ribaudo</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/npm/node-semver/blob/v6.3.1/CHANGELOG.md">semver's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/npm/node-semver/compare/v6.3.0...v6.3.1">6.3.1</a> (2023-07-10)</h2> <h3>Bug Fixes</h3> <ul> <li><a href="https://github.com/npm/node-semver/commit/928e56d21150da0413a3333a3148b20e741a920c"><code>928e56d</code></a> <a href="https://redirect.github.com/npm/node-semver/pull/591">#591</a> better handling of whitespace (<a href="https://redirect.github.com/npm/node-semver/issues/591">#591</a>) (<a href="https://github.com/lukekarrys"><code>@​lukekarrys</code></a>, <a href="https://github.com/joaomoreno"><code>@​joaomoreno</code></a>, <a href="https://github.com/nicolo-ribaudo"><code>@​nicolo-ribaudo</code></a>)</li> </ul> <h2>6.2.0</h2> <ul> <li>Coerce numbers to strings when passed to semver.coerce()</li> <li>Add <code>rtl</code> option to coerce from right to left</li> </ul> <h2>6.1.3</h2> <ul> <li>Handle X-ranges properly in includePrerelease mode</li> </ul> <h2>6.1.2</h2> <ul> <li>Do not throw when testing invalid version strings</li> </ul> <h2>6.1.1</h2> <ul> <li>Add options support for semver.coerce()</li> <li>Handle undefined version passed to Range.test</li> </ul> <h2>6.1.0</h2> <ul> <li>Add semver.compareBuild function</li> <li>Support <code>*</code> in semver.intersects</li> </ul> <h2>6.0</h2> <ul> <li> <p>Fix <code>intersects</code> logic.</p> <p>This is technically a bug fix, but since it is also a change to behavior that may require users updating their code, it is marked as a major version increment.</p> </li> </ul> <h2>5.7</h2> <ul> <li>Add <code>minVersion</code> method</li> </ul> <h2>5.6</h2> <ul> <li>Move boolean <code>loose</code> param to an options object, with backwards-compatibility protection.</li> <li>Add ability to opt out of special prerelease version handling with the <code>includePrerelease</code> option flag.</li> </ul> <h2>5.5</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/npm/node-semver/commit/44d27bc007e4827e9b797d6145f1076c127005f2"><code>44d27bc</code></a> chore: release 6.3.1</li> <li><a href="https://github.com/npm/node-semver/commit/928e56d21150da0413a3333a3148b20e741a920c"><code>928e56d</code></a> fix: better handling of whitespace (<a href="https://redirect.github.com/npm/node-semver/issues/591">#591</a>)</li> <li><a href="https://github.com/npm/node-semver/commit/39f632690ea5b1b0d64fa913aa0f96f42b9bde32"><code>39f6326</code></a> chore: <code>@​npmcli/template-oss</code><a href="https://github.com/4"><code>@​4</code></a>.16.0</li> <li>See full diff in <a href="https://github.com/npm/node-semver/compare/v6.3.0...v6.3.1">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~lukekarrys">lukekarrys</a>, a new releaser for semver since your current version.</p> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=semver&package-manager=npm_and_yarn&previous-version=6.3.0&new-version=6.3.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/opencv/cvat/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 13 July 2023, 05:34:12 UTC
0c8a46e Maxim Zhiltsov 12 July 2023, 15:17:46 UTC Honey Pot fixes (#6456) Fixed: UI: - opening skeleton point RMB menu leads to UI fail - annotation conflicts are accumulated when changing frames, if the annotation has multiple conflicts - improve OKS sigma description Server: - average mean iou can be negative 12 July 2023, 15:17:46 UTC
31b5e25 Maxim Zhiltsov 12 July 2023, 13:27:26 UTC Keep model input data unchanged in SDK (#6455) Nested containers may be modified during the model input data parsing in class constructors. This can lead to subtle memory errors, which are very hard to find. In CVAT, this helps to avoid unexpected problems in tests, such as one test affecting another one by subtly changing test assets. 12 July 2023, 13:27:26 UTC
03975ea Boris Sekachev 12 July 2023, 11:42:05 UTC Supported multi-line input, fixed issue in aam with losing selection (#6458) <!-- 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 - [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)) - [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. 12 July 2023, 11:42:05 UTC
1e18713 Roman Donchenko 12 July 2023, 09:26:27 UTC Allow attribute default/permitted values to be blank (#6454) This is de facto already allowed when CVAT is accessed via the UI/API, even though the model/serializer configuration seem to prohibit it. That's because validation for attribute properties is effectively disabled on the server due to a bug. However, the SDK checks the schema, and thus doesn't allow such values. I think blank default values make sense (particularly for "text" type attributes), so I updated the code to allow them. Blank permitted values don't make quite as much sense, but I had to allow them too, because the UI always submits the default value as the first permitted value (even for freeform text attributes). This will let us fix the broken validation on the server side (which I'm planning to do soon) without removing the ability to set blank default attribute values via the UI. (FWIW, I don't think that the UI should add a `values` property when serializing freeform text attributes at all, but it would take a more substantial change to fix that, which I don't have time for right now.) 12 July 2023, 09:26:27 UTC
a63f0f1 dependabot[bot] 11 July 2023, 08:47:11 UTC Bump stylelint from 13.13.1 to 15.10.1 (#6444) Bumps [stylelint](https://github.com/stylelint/stylelint) from 13.13.1 to 15.10.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/stylelint/stylelint/releases">stylelint's releases</a>.</em></p> <blockquote> <h2>15.10.1</h2> <ul> <li>Security: fix for <code>semver</code> vulnerability (<a href="https://redirect.github.com/stylelint/stylelint/issues/7043">#7043</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: invalid option regression on Windows 10 (<a href="https://redirect.github.com/stylelint/stylelint/issues/7043">#7043</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> </ul> <h2>15.10.0</h2> <ul> <li>Added: <code>media-query-no-invalid</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/6963">#6963</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Added: support for JS objects with <code>extends</code> config option (<a href="https://redirect.github.com/stylelint/stylelint/issues/6998">#6998</a>) (<a href="https://github.com/fpetrakov"><code>@​fpetrakov</code></a>).</li> <li>Fixed: inconsistent <code>errored</code> properties in <code>stylelint.lint()</code> return value (<a href="https://redirect.github.com/stylelint/stylelint/issues/6983">#6983</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>{selector,value}-no-vendor-prefix</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7016">#7016</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>custom-property-pattern</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7009">#7009</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>function-linear-gradient-no-nonstandard-direction</code> false positives for <code>&lt;color-interpolation-method&gt;</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/6987">#6987</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>function-name-case</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7010">#7010</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>function-no-unknown</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7004">#7004</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>function-url-quotes</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7011">#7011</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>hue-degree-notation</code> false negatives for <code>oklch</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/7015">#7015</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>hue-degree-notation</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7012">#7012</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>media-feature-name-no-unknown</code> false positives for <code>environment-blending</code>, <code>nav-controls</code>, <code>prefers-reduced-data</code>, and <code>video-color-gamut</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/6978">#6978</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>media-feature-name-no-vendor-prefix</code> positions for <code>*-device-pixel-ratio</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/6977">#6977</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>no-descending-specificity</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7026">#7026</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>no-duplicate-at-import-rules</code> false negatives for imports with <code>supports</code> and <code>layer</code> conditions (<a href="https://redirect.github.com/stylelint/stylelint/issues/7001">#7001</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>selector-anb-no-unmatchable</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7042">#7042</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>selector-id-pattern</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7013">#7013</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>selector-pseudo-class-no-unknown</code> false negatives for pseudo-elements with matching names (<a href="https://redirect.github.com/stylelint/stylelint/issues/6964">#6964</a>) (<a href="https://github.com/Mouvedia"><code>@​Mouvedia</code></a>).</li> <li>Fixed: <code>selector-pseudo-element-no-unknown</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7007">#7007</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>selector-type-case</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7041">#7041</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>selector-type-no-unknown</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7027">#7027</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>unit-disallowed-list</code> false negatives with percentages (<a href="https://redirect.github.com/stylelint/stylelint/issues/7018">#7018</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> </ul> <h2>15.9.0</h2> <ul> <li>Added: <code>insideFunctions: {&quot;function&quot;: int}</code> to <code>number-max-precision</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/6932">#6932</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>declaration-block-no-redundant-longhand-properties</code> autofix for <code>border-radius</code> shorthand (<a href="https://redirect.github.com/stylelint/stylelint/issues/6958">#6958</a>) (<a href="https://github.com/mattxwang"><code>@​mattxwang</code></a>).</li> <li>Fixed: <code>declaration-block-no-redundant-longhand-properties</code> autofix for <code>border-width</code> shorthand (<a href="https://redirect.github.com/stylelint/stylelint/issues/6956">#6956</a>) (<a href="https://github.com/mattxwang"><code>@​mattxwang</code></a>).</li> <li>Fixed: <code>declaration-block-no-redundant-longhand-properties</code> autofix for <code>grid-column</code> and <code>grid-row</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/6957">#6957</a>) (<a href="https://github.com/mattxwang"><code>@​mattxwang</code></a>).</li> </ul> <h2>15.8.0</h2> <ul> <li>Added: <code>media-feature-name-value-no-unknown</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/6906">#6906</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Added: support for <code>.mjs</code> configuration files (<a href="https://redirect.github.com/stylelint/stylelint/issues/6910">#6910</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>--print-config</code> description in CLI help (<a href="https://redirect.github.com/stylelint/stylelint/issues/6914">#6914</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>allowEmptyInput</code> option in configuration files (<a href="https://redirect.github.com/stylelint/stylelint/issues/6929">#6929</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>custom-property-no-missing-var-function</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/6922">#6922</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>function-calc-no-unspaced-operator</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/6923">#6923</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>function-linear-gradient-no-nonstandard-direction</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/6924">#6924</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>function-no-unknown</code> false positives for SCSS functions with namespace (<a href="https://redirect.github.com/stylelint/stylelint/issues/6921">#6921</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>max-nesting-depth</code> error for at-rules in Sass syntax (<a href="https://redirect.github.com/stylelint/stylelint/issues/6909">#6909</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>selector-anb-no-unmatchable</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/6925">#6925</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: remove <code>v8-compile-cache</code> dependency (<a href="https://redirect.github.com/stylelint/stylelint/issues/6907">#6907</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> </ul> <h2>15.7.0</h2> <ul> <li>Added: <code>splitList: boolean</code> to <code>selector-nested-pattern</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/6896">#6896</a>) (<a href="https://github.com/is2ei"><code>@​is2ei</code></a>).</li> <li>Fixed: <code>unit-no-unknown</code> false positives for <code>unicode-range</code> descriptors (<a href="https://redirect.github.com/stylelint/stylelint/issues/6892">#6892</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/stylelint/stylelint/blob/main/CHANGELOG.md">stylelint's changelog</a>.</em></p> <blockquote> <h2>15.10.1</h2> <ul> <li>Security: fix for <code>semver</code> vulnerability (<a href="https://redirect.github.com/stylelint/stylelint/pull/7043">#7043</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: invalid option regression on Windows 10 (<a href="https://redirect.github.com/stylelint/stylelint/pull/7043">#7043</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> </ul> <h2>15.10.0</h2> <ul> <li>Added: <code>media-query-no-invalid</code> (<a href="https://redirect.github.com/stylelint/stylelint/pull/6963">#6963</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Added: support for JS objects with <code>extends</code> config option (<a href="https://redirect.github.com/stylelint/stylelint/pull/6998">#6998</a>) (<a href="https://github.com/fpetrakov"><code>@​fpetrakov</code></a>).</li> <li>Fixed: inconsistent <code>errored</code> properties in <code>stylelint.lint()</code> return value (<a href="https://redirect.github.com/stylelint/stylelint/pull/6983">#6983</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>{selector,value}-no-vendor-prefix</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7016">#7016</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>custom-property-pattern</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7009">#7009</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>function-linear-gradient-no-nonstandard-direction</code> false positives for <code>&lt;color-interpolation-method&gt;</code> (<a href="https://redirect.github.com/stylelint/stylelint/pull/6987">#6987</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>function-name-case</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7010">#7010</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>function-no-unknown</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7004">#7004</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>function-url-quotes</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7011">#7011</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>hue-degree-notation</code> false negatives for <code>oklch</code> (<a href="https://redirect.github.com/stylelint/stylelint/pull/7015">#7015</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>hue-degree-notation</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7012">#7012</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>media-feature-name-no-unknown</code> false positives for <code>environment-blending</code>, <code>nav-controls</code>, <code>prefers-reduced-data</code>, and <code>video-color-gamut</code> (<a href="https://redirect.github.com/stylelint/stylelint/pull/6978">#6978</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>media-feature-name-no-vendor-prefix</code> positions for <code>*-device-pixel-ratio</code> (<a href="https://redirect.github.com/stylelint/stylelint/pull/6977">#6977</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>no-descending-specificity</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7026">#7026</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>no-duplicate-at-import-rules</code> false negatives for imports with <code>supports</code> and <code>layer</code> conditions (<a href="https://redirect.github.com/stylelint/stylelint/pull/7001">#7001</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>selector-anb-no-unmatchable</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7042">#7042</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>selector-id-pattern</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7013">#7013</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>selector-pseudo-class-no-unknown</code> false negatives for pseudo-elements with matching names (<a href="https://redirect.github.com/stylelint/stylelint/pull/6964">#6964</a>) (<a href="https://github.com/Mouvedia"><code>@​Mouvedia</code></a>).</li> <li>Fixed: <code>selector-pseudo-element-no-unknown</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7007">#7007</a>) (<a href="https://github.com/jeddy3"><code>@​jeddy3</code></a>).</li> <li>Fixed: <code>selector-type-case</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7041">#7041</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>selector-type-no-unknown</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/7027">#7027</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>unit-disallowed-list</code> false negatives with percentages (<a href="https://redirect.github.com/stylelint/stylelint/pull/7018">#7018</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> </ul> <h2>15.9.0</h2> <ul> <li>Added: <code>insideFunctions: {&quot;function&quot;: int}</code> to <code>number-max-precision</code> (<a href="https://redirect.github.com/stylelint/stylelint/pull/6932">#6932</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>declaration-block-no-redundant-longhand-properties</code> autofix for <code>border-radius</code> shorthand (<a href="https://redirect.github.com/stylelint/stylelint/pull/6958">#6958</a>) (<a href="https://github.com/mattxwang"><code>@​mattxwang</code></a>).</li> <li>Fixed: <code>declaration-block-no-redundant-longhand-properties</code> autofix for <code>border-width</code> shorthand (<a href="https://redirect.github.com/stylelint/stylelint/pull/6956">#6956</a>) (<a href="https://github.com/mattxwang"><code>@​mattxwang</code></a>).</li> <li>Fixed: <code>declaration-block-no-redundant-longhand-properties</code> autofix for <code>grid-column</code> and <code>grid-row</code> (<a href="https://redirect.github.com/stylelint/stylelint/pull/6957">#6957</a>) (<a href="https://github.com/mattxwang"><code>@​mattxwang</code></a>).</li> </ul> <h2>15.8.0</h2> <ul> <li>Added: <code>media-feature-name-value-no-unknown</code> (<a href="https://redirect.github.com/stylelint/stylelint/pull/6906">#6906</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Added: support for <code>.mjs</code> configuration files (<a href="https://redirect.github.com/stylelint/stylelint/pull/6910">#6910</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>--print-config</code> description in CLI help (<a href="https://redirect.github.com/stylelint/stylelint/pull/6914">#6914</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>allowEmptyInput</code> option in configuration files (<a href="https://redirect.github.com/stylelint/stylelint/pull/6929">#6929</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>custom-property-no-missing-var-function</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/6922">#6922</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>function-calc-no-unspaced-operator</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/6923">#6923</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>function-linear-gradient-no-nonstandard-direction</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/6924">#6924</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>function-no-unknown</code> false positives for SCSS functions with namespace (<a href="https://redirect.github.com/stylelint/stylelint/pull/6921">#6921</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: <code>max-nesting-depth</code> error for at-rules in Sass syntax (<a href="https://redirect.github.com/stylelint/stylelint/pull/6909">#6909</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> <li>Fixed: <code>selector-anb-no-unmatchable</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/pull/6925">#6925</a>) (<a href="https://github.com/romainmenke"><code>@​romainmenke</code></a>).</li> <li>Fixed: remove <code>v8-compile-cache</code> dependency (<a href="https://redirect.github.com/stylelint/stylelint/pull/6907">#6907</a>) (<a href="https://github.com/ybiquitous"><code>@​ybiquitous</code></a>).</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/stylelint/stylelint/commit/fb8cf35dae79e150ad17c75660bd93c4d4c0c9e0"><code>fb8cf35</code></a> 15.10.1</li> <li><a href="https://github.com/stylelint/stylelint/commit/eeed72bdde9a368df0fa01952a1cfc94364c84ca"><code>eeed72b</code></a> Prepare release (<a href="https://redirect.github.com/stylelint/stylelint/issues/7048">#7048</a>)</li> <li><a href="https://github.com/stylelint/stylelint/commit/80905538500d32a6f716fb1359e59de9fb418d02"><code>8090553</code></a> Document check of configs in release process (<a href="https://redirect.github.com/stylelint/stylelint/issues/7047">#7047</a>)</li> <li><a href="https://github.com/stylelint/stylelint/commit/56a545e116e4f4bd52595a3eb3d131306ce02862"><code>56a545e</code></a> Security fix for <code>semver</code> vulnerability (<a href="https://redirect.github.com/stylelint/stylelint/issues/7043">#7043</a>)</li> <li><a href="https://github.com/stylelint/stylelint/commit/a42f95582c2a928122fc1e59f9f8acc078fb9b91"><code>a42f955</code></a> Fix rules documentation for <code>media-query-no-invalid</code> (<a href="https://redirect.github.com/stylelint/stylelint/issues/7044">#7044</a>)</li> <li><a href="https://github.com/stylelint/stylelint/commit/e56aa3001c3ef0070c6b2713a1554257f37472ab"><code>e56aa30</code></a> 15.10.0</li> <li><a href="https://github.com/stylelint/stylelint/commit/c9e89ebcf6495d3935d8e6ee29eb6607f936caf3"><code>c9e89eb</code></a> Prepare release (<a href="https://redirect.github.com/stylelint/stylelint/issues/6974">#6974</a>)</li> <li><a href="https://github.com/stylelint/stylelint/commit/b8e53176d42b496f84eaa520d9067c87e9080469"><code>b8e5317</code></a> Fix <code>selector-type-case</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7041">#7041</a>)</li> <li><a href="https://github.com/stylelint/stylelint/commit/f82a24a6508f8a3a7d752b828cdb216e103cab63"><code>f82a24a</code></a> Fix <code>selector-anb-no-unmatchable</code> performance (<a href="https://redirect.github.com/stylelint/stylelint/issues/7042">#7042</a>)</li> <li><a href="https://github.com/stylelint/stylelint/commit/16110fdde589caca7fafc0d2a167542bc5080d62"><code>16110fd</code></a> Revert removed changelog entry (<a href="https://redirect.github.com/stylelint/stylelint/issues/7039">#7039</a>)</li> <li>Additional commits viewable in <a href="https://github.com/stylelint/stylelint/compare/13.13.1...15.10.1">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mattxwang">mattxwang</a>, a new releaser for stylelint since your current version.</p> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=stylelint&package-manager=npm_and_yarn&previous-version=13.13.1&new-version=15.10.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/opencv/cvat/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 11 July 2023, 08:47:11 UTC
c15a855 dependabot[bot] 11 July 2023, 08:47:01 UTC Bump tough-cookie from 4.1.2 to 4.1.3 (#6445) Bumps [tough-cookie](https://github.com/salesforce/tough-cookie) from 4.1.2 to 4.1.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/salesforce/tough-cookie/releases">tough-cookie's releases</a>.</em></p> <blockquote> <h2>4.1.3</h2> <p>Security fix for Prototype Pollution discovery in <a href="https://redirect.github.com/salesforce/tough-cookie/issues/282">#282</a>. This is a minor release, although output from the <code>inspect</code> utility is affected by this change, we felt this change was important enough to be pushed into the next patch.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/salesforce/tough-cookie/commit/4ff4d29f6cefd279a412b8d62a21142ebd410b36"><code>4ff4d29</code></a> 4.1.3 release preparation, update the package and lib/version to 4.1.3. (<a href="https://redirect.github.com/salesforce/tough-cookie/issues/284">#284</a>)</li> <li><a href="https://github.com/salesforce/tough-cookie/commit/12d474791bb856004e858fdb1c47b7608d09cf6e"><code>12d4747</code></a> Prevent prototype pollution in cookie memstore (<a href="https://redirect.github.com/salesforce/tough-cookie/issues/283">#283</a>)</li> <li><a href="https://github.com/salesforce/tough-cookie/commit/f06b72d1d447f33dfa6222c0a3c0c5e063558248"><code>f06b72d</code></a> Fix documentation for store.findCookies, missing allowSpecialUseDomain proper...</li> <li>See full diff in <a href="https://github.com/salesforce/tough-cookie/compare/v4.1.2...v4.1.3">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tough-cookie&package-manager=npm_and_yarn&previous-version=4.1.2&new-version=4.1.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/opencv/cvat/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 11 July 2023, 08:47:01 UTC
44382be Roman Donchenko 10 July 2023, 12:55:00 UTC Fix overly broad exception conversion in `LambdaFunction.invoke` (#6394) The intent of the `try`/`except` statement is to catch accesses to missing members of the `data` dictionary, but due to the large amount of code in the `try` block, it may end up catching entirely unrelated `KeyError`s. Those unrelated `KeyError`s should not be converted to `ValidationError`s, since they might not have anything to do with input validation, and the conversion will make it harder to debug these exceptions. An example of these misapplied conversions is a recent bug where a `KeyError` was coming from inside `_get_image` (fixed by f6420eb7). To fix this, make sure to only catch `KeyError`s emitted by accesses to `data`. 10 July 2023, 12:55:00 UTC
c31fbeb Anastasia Yasakova 10 July 2023, 09:43:13 UTC Code coverage fixes (#6420) <!-- 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. --> - Removed code coverage from full and schedule workflows - Updated codecov.yml - Fixed coverage saving in rqworker.py - Now one code coverage report is sent to codecov after passing all 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! --> - [ ] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. --------- Co-authored-by: yasakova-anastasia <anastasia@cvat.ai> 10 July 2023, 09:43:13 UTC
4b179be Andrey Zhavoronkov 05 July 2023, 16:42:17 UTC Updated CHANGELOG.md, bump version (#6426) 05 July 2023, 16:42:17 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
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
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
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
back to top