-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v2.21.3 #8621
Release v2.21.3 #8621
Conversation
Update develop after v2.21.2
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Rather than retag the Docker images, it seems like we can just build them with correct tags to start with.
<!-- Raise 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 guide](https://docs.cvat.ai/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> It currently uses an auxiliary Docker Hub account to temporarily store the images, but all other workflows have long ago switched to using workflow artifacts. Switch this workflow too, by replacing all image-handling code with the equivalents from `main.yml`. The main reason to do this is to fix a bug in the workflow: the `unit_testing` job tags the `cvat/*` images as `:latest`, but the Compose file wants the `:dev` tag. So the images end up being redownloaded from Docker Hub. There are also a few other reasons why the new version is better: * It avoids unnecessary complexity, viz. the usage of Docker Hub, an external service. * It's consistent with the other pipelines, which should make future changes easier. * It's much less code. ### 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. --> Test run: <https://github.com/cvat-ai/cvat/actions/runs/11504222821>. You can see that at no point it pulls the `cvat/server` or `cvat/ui` images from GitHub. ### 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 created a changelog fragment~~ <!-- see top comment in CHANGELOG.md --> - ~~[ ] 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/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. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Chores** - Updated workflow configuration to streamline artifact management for image builds. - Removed Docker Hub interactions for building and testing images. - Introduced a new environment variable `CVAT_VERSION` for tagging images. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- Raise 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 guide](https://docs.cvat.ai/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. --> When a status check for `request` is failing for any reason, eg something happened on the server and the request failed with 50X error. The requests page crushes with an error: `Cannot read property 'target' of undefined` : ![image](https://github.com/user-attachments/assets/e41ea391-c03e-47cd-9ab0-1e06583d366c) Now the error message is shown: ![image](https://github.com/user-attachments/assets/e9976657-2fc8-4be8-94b4-1d5453b9d9ab) ### 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 created a changelog fragment <!-- see top comment in CHANGELOG.md --> - ~~[ ] 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/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. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes - **New Features** - Enhanced request handling with improved initialization and error management for tasks and jobs. - Added `listenToCreate` method in the Task class for better task creation management. - Introduced `generateInitialRequest` function to standardize request initialization across imports and exports. - **Bug Fixes** - Improved clarity of status messages for failed requests in the RequestCard component. - **Documentation** - Updated method signatures across various action files for better clarity and consistency. - **Chores** - Refined import statements and type exports in the core wrapper to streamline functionality. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- Raise 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 guide](https://docs.cvat.ai/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. --> Fixed several issues: - GT tags are rendered with `(GT)` mark inside of GT job which is not correct - GT tags can not be deleted via `x` button inside the GT job Other improvements: - Refactored `frame-tags` component code - Improved styles for gt/non-gt tags, as they are too close: ![image](https://github.com/user-attachments/assets/a5b1c055-4ee0-4469-ada2-21a6a70146ee) -> ![image](https://github.com/user-attachments/assets/49eb4625-1690-4865-b94f-973cee351183) Related #8547 ### 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 created a changelog fragment <!-- see top comment in CHANGELOG.md --> - [ ] 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/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. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced state management in the FrameTags component for improved performance and readability. - Introduced a new CSS class to manage spacing in the tag annotation workspace. - **Bug Fixes** - Updated tag filtering logic to improve accuracy in displaying tags. - **Refactor** - Simplified component structure by utilizing hooks for state management. - Optimized rendering logic and performance with memoization. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Test it by starting an HTTPS server (that forwards all requests to CVAT) and attempting to access that server via the CLI. This allows us to test that the option actually works end-to-end, and avoids dependencies on CLI internals. The new test requires `main` to catch the exception that is raised in the case of a certificate error, so implement that.
…8617) Some of them are annotated with an `Iterator` return type. However... It just occurred to me that `@contextmanager` cannot work with a function that returns a plain iterator, since it relies on the generator class's `throw` method. `contextmanager` is defined in typeshed as accepting an iterator-returning function, but that appears to be a bug: <python/typeshed#2772>. Change all such annotations to a `Generator` type instead. Some annotations are also broken in other ways; fix them too.
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Quality Gate passedIssues Measures |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #8621 +/- ##
==========================================
+ Coverage 74.24% 74.32% +0.08%
==========================================
Files 403 401 -2
Lines 43315 43319 +4
Branches 3914 3925 +11
==========================================
+ Hits 32159 32197 +38
+ Misses 11156 11122 -34
|
Changed
--insecure
CLI option test less hacky #8601)Removed
Fixed
Requests page crush with
Cannot read property 'target' of undefined
error (Fix UI crush on failed request status check #8575)Tags in ground truth job were displayed as
tag (GT)
(Improved Ground truth tags #8586)Tags in ground truth job couldn't be deleted via
x
button (Improved Ground truth tags #8586)Exception 'Canvas is busy' when change frame during drag/resize a track (Exception 'Canvas is busy' when change frame during drag/resize a track #8598)
A shape gets shifted if auto save triggered during dragging (Exception 'Canvas is busy' when change frame during drag/resize a track #8598)