- 10 5月, 2023 3 次提交
-
-
由 Boris Sekachev 提交于
-
由 Andrey Zhavoronkov 提交于
-
由 Andrey Zhavoronkov 提交于
-
- 09 5月, 2023 1 次提交
-
-
由 Boris Sekachev 提交于
<!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context Before/after fix execution: ![image](https://user-images.githubusercontent.com/40690378/236913420-6165e7aa-8758-4efd-be8b-825304e92c19.png) ![image](https://user-images.githubusercontent.com/40690378/236913439-862d60a7-1d90-463f-8129-acb5f2727eb9.png) ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern.
-
- 05 5月, 2023 2 次提交
-
-
由 Maxim Zhiltsov 提交于
- Fixed completed task job count reporting in the task summary - Added a test Fixes #6098 Fixes #6034
-
由 Roman Donchenko 提交于
-
- 01 5月, 2023 1 次提交
-
-
由 Boris Sekachev 提交于
<!-- 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.
-
- 28 4月, 2023 1 次提交
-
-
由 Maria Khrustaleva 提交于
-
- 27 4月, 2023 1 次提交
-
-
由 Andrey Zhavoronkov 提交于
-
- 25 4月, 2023 2 次提交
-
-
由 Andrey Zhavoronkov 提交于
-
由 Andrey Zhavoronkov 提交于
-
- 21 4月, 2023 1 次提交
-
-
由 Roman Donchenko 提交于
This way, it can be done in parallel with pip fetching all other packages in the main build stage. In practice, I find that the build of PyAV finishes before pip is done downloading, so we basically get it done for free (in terms of time). With this change, I measured a build time of 9:09 (starting from scratch).
-
- 20 4月, 2023 1 次提交
-
-
由 Roman Donchenko 提交于
This improves the reproducibility of the server build process. Now new versions of dependencies can no longer break the server unless we explicitly upgrade to them. To minimize changes, I did not update any of the version constraints we currently have; however, in the future, we should be able to relax a lot of them. Resolves #5310.
-
- 19 4月, 2023 3 次提交
-
-
由 Roman Donchenko 提交于
The policy that mandated this is no longer relevant now that CVAT is no longer developed by Intel. Moreover, the source code included was not even complete (it didn't contain Python or NPM packages). This saves ~1.6 GB in the unpacked image (and probably a bunch of build time too, but I didn't measure it).
-
由 Roman Donchenko 提交于
This originally started as a security update for redis-py (see <https://github.com/redis/redis-py/releases/tag/v4.5.3>, <https://github.com/redis/redis-py/releases/tag/v4.5.4>). However, I also had to update other Redis-related components because of incompatibilities. * The old version of fakeredis is not compatible with the redis-py 4.x, so I bumped it too. This also allowed me to remove the six workaround. * redis-py 4.1.0 and newer don't support Redis < 5, so I bumped Redis itself in `docker-compose.yml`. Note that the Helm chart is already using Redis 7.0.x. Obsoletes #5946.
-
由 Roman Donchenko 提交于
This speeds up the build when the entire step can't be cached (e.g. the requirements file changed), but the package list remains mostly the same. The savings are... rather underwhelming, actually. I have observed about a minute in savings, although it obviously depends on the network connection speed. I think this is because pip is inefficient at loading from its own cache (I have observed it loading the entire cached file into memory, for example). Still, savings are savings, and we're getting them basically for free, so why not. Note that I only persist the HTTP cache, and not the wheel cache. That's because any wheels that pip builds could depend on the system packages, and I don't want old wheels to be reused if the system packages change. Also, disable the pip autoupdate checks, which isn't much of an optimization, but it gets rid of some pointless warnings.
-
- 17 4月, 2023 1 次提交
-
-
由 Maxim Zhiltsov 提交于
Extracted from #5083 - Fixed test data placement in tests - Fixed cache cleaning in tests - Refactored server API tests and dataset_manifest - Added more tests
-
- 14 4月, 2023 6 次提交
-
-
由 Andrey Zhavoronkov 提交于
-
由 Kirill Sizov 提交于
-
由 Andrey Zhavoronkov 提交于
Update CHANGELOG.md
-
由 Andrey Zhavoronkov 提交于
Update base image ubuntu 20.04 -> 22.04 update python 3.8 -> 3.10 update sqlite3 from 3.31 -> 3.37
-
由 Mariia Acoca 提交于
Fix typos in CHANGELOG
-
由 Mariia Acoca 提交于
Update CHANGELOG.md
-
- 13 4月, 2023 1 次提交
-
-
由 Andrey Zhavoronkov 提交于
-
- 12 4月, 2023 4 次提交
-
-
由 Roman Donchenko 提交于
This applies several minor improvements that together shave off a little bit of build time (on my machine, it goes down from 14:10 to 13:20) and a little bit of size of the final image (likely just a few megabytes, so I didn't measure it exactly).
-
由 Boris Sekachev 提交于
<!-- 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.
-
由 Boris Sekachev 提交于
Idea of the PR is to finish this one #5990 Deploy for GPU: ``./deploy_gpu.sh pytorch/facebookresearch/sam/nuclio/`` Deploy for CPU: ``./deploy_cpu.sh pytorch/facebookresearch/sam/nuclio/`` If you want to use GPU, be sure you setup docker for this [guide](https://github.com/NVIDIA/nvidia-docker/blob/master/README.md#quickstart). Resolved issue #5984 But the interface probably can be improved Co-authored-by: NAlx-Wo <alexander.wolpert@googlemail.com>
-
由 Nikita Manovich 提交于
Fix #5996 We have multiple problems with sqlite on different operation systems. The idea here is to use the same DB in debug and in production. sqlite database is locked errors: - https://www2.sqlite.org/cvstrac/wiki?p=DatabaseIsLocked - https://docs.djangoproject.com/en/4.2/ref/databases/#database-is-locked-errors --------- Co-authored-by: Nkirill-sizov <sizow.k.d@gmail.com>
-
- 11 4月, 2023 3 次提交
-
-
由 Nikita Manovich 提交于
-
由 Kirill Sizov 提交于
-
由 Roman Donchenko 提交于
`HTTPResponse.getheader` and `getheaders` are slated to be removed in urllib3 2.1.0.
-
- 09 4月, 2023 1 次提交
-
-
由 Maxim Zhiltsov 提交于
- Added missing compatibility with micro- and smaller releases
-
- 07 4月, 2023 4 次提交
-
-
由 Anastasia Yasakova 提交于
-
由 Kirill Sizov 提交于
This PR fixes the following problems: - #5631 - This will allow webhooks to be sent not only when an explicit request has been sent to the server. Co-authored-by: NNikita Manovich <nikita@cvat.ai> Co-authored-by: Nyasakova-anastasia <anastasia@cvat.ai> Co-authored-by: NRoman Donchenko <roman@cvat.ai>
-
-
由 Maxim Zhiltsov 提交于
This PR fixes a problem with WriteOnceSerializer that it affected only the fields declared in the `Meta.fields`, while the manually declared fields were left unaffected. This PR also fixes several issues with invalid field declarations.
-
- 06 4月, 2023 4 次提交
-
-
由 Nikita Manovich 提交于
-
由 Andrey Zhavoronkov 提交于
OPA currently logs every request to the console and this results in huge docker log files. I don't think these logs can be useful for enabling docker-level log size limits.
-
由 Anastasia Yasakova 提交于
-
由 Roman Donchenko 提交于
As explained in the comment in `_tus_chunk_action`, I don't think we need explicit documentation for these endpoints. Hiding them makes the documentation a bit cleaner, especially because these endpoints were indistinguishable from one another. It also removes the corresponding SDK code, which is good, since clients should follow the URL returned by the creation endpoint, not invoke the chunk endpoints directly.
-