Update develop after v2.16.3

[cvat-bot]

Summary by CodeRabbit

• New Features

  • Enhanced UI labels mapper for skeleton points, improving usability.
  • Upgraded "Segment Anything" feature to support bounding box input.

• Improvements

  • Adjusted player navigation for smoother transitions during frame loading.
  • Accelerated implementation of the IntelligentScissors tool for better performance.

• Bug Fixes

  • Resolved issue where the issue tool was not resetting after creating new issues.
  • Fixed slice handling in the LazyList, ensuring proper mask exports for CVAT format.

[coderabbitai]

Walkthrough

Version 2.16.3 introduces significant enhancements to user interaction and functionality. The UI's labels mapper now supports attributes for skeleton points, while the "Segment Anything" feature gains bounding box input capabilities. Player navigation is smoother with uninterrupted loading, and the IntelligentScissors tool is faster for image segmentation. Several bugs have been resolved, ensuring a more seamless experience for users working with issues and exported data.

Changes

Files	Change Summary
UI components	Enhanced labels mapper to support skeleton point attributes; improved usability
SegmentAnything feature	Upgraded to support bounding box input, increasing versatility
Navigation functionality	Adjusted player navigation behavior for uninterrupted transitions during frame loading
OpenCV integration	Accelerated implementation of the IntelligentScissors tool for better performance
Issue management	Fixed bug where issue tool was not reset after creating a new issue
LazyList class	Resolved slice handling issues affecting mask exporting in CVAT for images 1.1

Poem

🐰 In fields of code where rabbits play,
New features hop in bright array.
With smoother paths and tools that glide,
We celebrate the changes wide!
So gather 'round, let joy take flight,
For updates bring us sheer delight! 🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (3)

CHANGELOG.md (3)

22-28: Clarify the context of added features.

The descriptions in the "Added" section are clear, but it might be helpful to provide more context or examples of how these features enhance the user experience.

Consider adding brief examples or scenarios where these features would be particularly beneficial.

---

30-36: Provide more detail on the impact of changes.

The "Changed" section mentions improvements but could benefit from additional details on how these changes impact performance or user experience.

Consider elaborating on the specific benefits users might experience due to these changes, such as reduced wait times or enhanced tool responsiveness.

---

38-45: Ensure clarity and completeness of fixed issues.

The "Fixed" section provides a concise list of resolved issues. Ensure that each fix is described clearly, and consider adding more context if necessary to highlight the significance of these fixes.

Consider providing a brief explanation of the impact of these fixes on user workflows or data integrity.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5314bda and d8d9b92.

Files selected for processing (1)

• CHANGELOG.md (1 hunks)