- 14 12月, 2022 1 次提交
-
-
由 Boris Sekachev 提交于
<!-- Raised an issue to propose your change (https://github.com/cvat-ai/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](https://github.com/cvat-ai/cvat/blob/develop/CONTRIBUTING.md) guide. --> <!-- 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 by a reason then ~~explicitly strikethrough~~ the whole line. If you don't do that github will show an incorrect process 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 [CHANGELOG](https://github.com/cvat-ai/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the [documentation]( https://github.com/cvat-ai/cvat/blob/develop/README.md#documentation) accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues ([read 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/cvat-ai/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/cvat-ai/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/cvat-ai/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/cvat-ai/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern.
-
- 13 12月, 2022 1 次提交
-
-
由 Andrey Zhavoronkov 提交于
-
- 11 12月, 2022 1 次提交
-
-
由 Maria Khrustaleva 提交于
-
- 10 12月, 2022 6 次提交
-
-
由 Andrey Zhavoronkov 提交于
-
由 Maxim Zhiltsov 提交于
Ported from https://github.com/opencv/cvat/pull/4819 - Fixed project APIs in SDK core - Added tests for projects
-
由 Mariia Acoca 提交于
-
由 Maxim Zhiltsov 提交于
Closes https://github.com/opencv/cvat/issues/5327 - Added a way to debug the server in Docker-based deployments - Added docs
-
由 Maxim Zhiltsov 提交于
- Reduced request status checks period to 2 sec. - Fixed parameter help message
-
由 Maxim Zhiltsov 提交于
Extracted from #5083 Related #5096 - Improved dataset manifest docs - Dataset manifest requirements are now installed in the server image - Package dependencies are aligned with the server
-
- 09 12月, 2022 1 次提交
-
-
由 Maria Khrustaleva 提交于
Added a general solution for checking bucket and file status instead of checking in all places. Exception information has become more user-friendly.
-
- 08 12月, 2022 5 次提交
-
-
由 Roman Donchenko 提交于
-
由 Maxim Zhiltsov 提交于
Extracted some enhancements from https://github.com/opencv/cvat/pull/4819 - Extracted common s3 manipulations in tests - Refactored import/export tests to be more clear
-
由 Roman Donchenko 提交于
For user-facing functions, keep accepting `str` paths to maintain compatibility and flexibility, but add support for arbitrary path-like objects. For internal functions (in `downloading.py` and `uploading.py`), don't bother and require `pathlib.Path`. The only code that isn't converted is build-time code (e.g. `setup.py`) and code that came from openapi-generator.
-
由 Roman Donchenko 提交于
`isort --version` prints a large banner, which, after shell processing, is collapsed into one line, and the result is an unreadable mess. Use `--version-number` instead, which prints just the number.
-
由 Maxim Zhiltsov 提交于
- OPA tests are now autogenerated - Updated invocation docs
-
- 06 12月, 2022 3 次提交
-
-
由 Nikita Manovich 提交于
-
由 Mariia Acoca 提交于
User authorization documentation updated: - Screenshots - Procedure descriptions - Links
-
由 Roman Donchenko 提交于
`pathlib` improves code readability and type safety. It is already used in some of the tests; convert all remaining `os.path` usage to `pathlib` equivalents.
-
- 05 12月, 2022 5 次提交
-
-
-
由 Maxim Zhiltsov 提交于
Fixes #4996 - Added job access checks for model launches in the interactive mode
-
由 Roman Donchenko 提交于
Fixes #4365
-
由 Boris Sekachev 提交于
Related #3438
-
由 Roman Donchenko 提交于
The cause of the warning is explained here: https://devblogs.microsoft.com/typescript/announcing-typescript-3-8-beta/#type-only-imports-exports Add a webpack configuration option to treat such warnings as errors, to prevent any more of them from appearing in the future. <!-- Raised an issue to propose your change (https://github.com/cvat-ai/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](https://github.com/cvat-ai/cvat/blob/develop/CONTRIBUTING.md) guide. --> <!-- 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. --> Warnings are annoying. ### 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 by a reason then ~~explicitly strikethrough~~ the whole line. If you don't do that github will show an incorrect process 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 [CHANGELOG](https://github.com/cvat-ai/cvat/blob/develop/CHANGELOG.md) file~~ - ~~[ ] I have updated the [documentation]( https://github.com/cvat-ai/cvat/blob/develop/README.md#documentation) accordingly~~ - ~~[ ] I have added tests to cover my changes~~ - ~~[ ] I have linked related issues ([read 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/cvat-ai/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/cvat-ai/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/cvat-ai/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/cvat-ai/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern.
-
- 03 12月, 2022 4 次提交
-
-
由 dependabot[bot] 提交于
-
由 Maxim Zhiltsov 提交于
Fixes #5215 It's not really clear how the error can be obtained, but this PR adds a workaround for the problem. There are 2 possible ways to get the `message` parameter - from an error and from the operation status. - Our status messages are always represented by a string, no any other values is assigned. - rq is trickier here - it receives rq data and [decodes it](https://github.com/rq/rq/blob/master/rq/job.py#L603-L609) if there is an error, but the operations can leave None as the `exc_info` value. Maybe [this issue](https://github.com/rq/rq/issues/1633) is relevant here.
-
由 Boris Sekachev 提交于
### Motivation and context Related #3438 - When dblclick one of sideviews during drawing - UI is broken - When mouseleave sideviews during drawing - bbox disappears, need to draw again - Sometimes multiple draw boxes exist on view Example: ![bug_1](https://user-images.githubusercontent.com/40690378/205139685-2c348b4f-30c0-4bcc-a101-e07c880ff358.gif)
-
由 Maria Khrustaleva 提交于
Fixed REST API tests after merging #5408 and #5396 to develop Co-authored-by: NBoris Sekachev <sekachev.bs@gmail.com> Co-authored-by: NNikita Manovich <nikita@cvat.ai>
-
- 02 12月, 2022 9 次提交
-
-
由 Andrey Zhavoronkov 提交于
-
由 Maxim Zhiltsov 提交于
-
由 Nikita Manovich 提交于
Fix https://github.com/opencv/cvat/issues/5245 The PR contains a simple fix. Just return BAD REQUEST if somebody tries to export a task without data. It doesn't make sense. But a more complex fix will require changing a massive amount of code. It doesn't make any sense to support such a weird scenario.
-
由 Mariia Acoca 提交于
-
由 Boris Sekachev 提交于
-
由 Andrey Zhavoronkov 提交于
-
由 Andrey Zhavoronkov 提交于
-
由 Maxim Zhiltsov 提交于
Follow up for #5394 The existing text wont work in a clean repo. This PR adds missing info.
-
由 Maria Khrustaleva 提交于
-
- 01 12月, 2022 4 次提交
-
-
由 Boris Sekachev 提交于
-
由 Nikita Manovich 提交于
Fix https://github.com/opencv/cvat/issues/5214 1. Stable names for containers (_ vs -) 2. Improve documentation
-
由 Kirill Lakhov 提交于
<!-- Raised an issue to propose your change (https://github.com/cvat-ai/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](https://github.com/cvat-ai/cvat/blob/develop/CONTRIBUTING.md) guide. --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Resolved #5274 + Fixed typo in 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 by a reason then ~~explicitly strikethrough~~ the whole line. If you don't do that github will show an incorrect process 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 [CHANGELOG](https://github.com/cvat-ai/cvat/blob/develop/CHANGELOG.md) file - [ ] I have updated the [documentation]( https://github.com/cvat-ai/cvat/blob/develop/README.md#documentation) accordingly - [x] I have added tests to cover my changes - [x] I have linked related issues ([read 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/cvat-ai/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/cvat-ai/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/cvat-ai/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/cvat-ai/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/cvat-ai/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern.
-
由 Maria Khrustaleva 提交于
-