Skip to content
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

Support redis migrations #8898

Open
wants to merge 32 commits into
base: develop
Choose a base branch
from
Open

Support redis migrations #8898

wants to merge 32 commits into from

Conversation

Marishka17
Copy link
Contributor

@Marishka17 Marishka17 commented Jan 3, 2025

Motivation and context

Sometimes we need to modify the data stored in Redis (for instance, in the near future we will change the identifiers of RQ jobs). This PR introduces a common mechanism for handling Redis migrations.

How has this been tested?

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)
  • I have increased versions of npm packages if it is necessary
    (cvat-canvas,
    cvat-core,
    cvat-data and
    cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

Copy link
Contributor

coderabbitai bot commented Jan 3, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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
🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

cvat/apps/engine/management/commands/migrateredis.py Outdated Show resolved Hide resolved
cvat/apps/engine/management/commands/migrateredis.py Outdated Show resolved Hide resolved
cvat/apps/engine/management/commands/migrateredis.py Outdated Show resolved Hide resolved
cvat/apps/engine/management/commands/migrateredis.py Outdated Show resolved Hide resolved
cvat/apps/engine/models.py Outdated Show resolved Hide resolved
@Marishka17 Marishka17 marked this pull request as ready for review January 16, 2025 10:39
@Marishka17 Marishka17 requested a review from azhavoro as a code owner January 16, 2025 10:39
cvat/apps/redis_handler/apps.py Show resolved Hide resolved
cvat/apps/redis_handler/migration_loader.py Outdated Show resolved Hide resolved
cvat/apps/redis_handler/migration_loader.py Outdated Show resolved Hide resolved
cvat/apps/redis_handler/migration_loader.py Outdated Show resolved Hide resolved
cvat/apps/redis_handler/migration_loader.py Outdated Show resolved Hide resolved
dev/format_python_code.sh Outdated Show resolved Hide resolved
cvat/apps/redis_handler/models.py Outdated Show resolved Hide resolved
@codecov-commenter
Copy link

codecov-commenter commented Jan 16, 2025

Codecov Report

Attention: Patch coverage is 68.57143% with 44 lines in your changes missing coverage. Please review.

Project coverage is 73.41%. Comparing base (30e900b) to head (98d0037).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #8898      +/-   ##
===========================================
- Coverage    73.41%   73.41%   -0.01%     
===========================================
  Files          418      427       +9     
  Lines        44299    44439     +140     
  Branches      3870     3870              
===========================================
+ Hits         32524    32625     +101     
- Misses       11775    11814      +39     
Components Coverage Δ
cvat-ui 77.40% <ø> (+0.02%) ⬆️
cvat-server 70.11% <68.57%> (-0.01%) ⬇️

@Marishka17 Marishka17 changed the title Support redis migrations [WIP] Support redis migrations Jan 16, 2025
@Marishka17 Marishka17 requested a review from nmanovic as a code owner January 17, 2025 16:52
@Marishka17 Marishka17 changed the title Support redis migrations [do not merge] Support redis migrations Jan 17, 2025
@Marishka17
Copy link
Contributor Author

I have no time to investigate what is going on with Helm tests

@Marishka17 Marishka17 requested a review from bsekachev as a code owner January 27, 2025 09:07
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like these changes were made by pre-commit hook
@bsekachev

@Marishka17 Marishka17 changed the title [do not merge] Support redis migrations Support redis migrations Jan 27, 2025
@Marishka17 Marishka17 requested review from SpecLad and removed request for zhiltsov-max, bsekachev, nmanovic and azhavoro January 27, 2025 12:34
backend_entrypoint.sh Outdated Show resolved Hide resolved
cvat/apps/engine/redis_migrations/__init__.py Outdated Show resolved Hide resolved
applied_date: datetime = field(
validator=[validators.instance_of(datetime)], converter=to_datetime
)
identifier: UUID = field(factory=uuid4, converter=to_uuid)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need an extra identifier? Shouldn't <app_label>.<name> already be a unique key?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it should, probably I did so initially because I would not keep only the applied date in a hash item

cvat/apps/redis_handler/migration_loader.py Outdated Show resolved Hide resolved
cvat/apps/redis_handler/migration_loader.py Outdated Show resolved Hide resolved
cvat/apps/redis_handler/migration_loader.py Outdated Show resolved Hide resolved
@Marishka17
Copy link
Contributor Author

It seems that these tests are unstable. I've compared the latest logs with logs where there was a problem with helm tests related to resetting applied migrations from the Redis and waiting in workers for them. Workers are initialized correctly and start running.
https://github.com/cvat-ai/cvat/actions/runs/12833455817
https://github.com/cvat-ai/cvat/actions/runs/13054237659

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants