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

Update presence_change migration for JSON to Protobuf conversion #1075

Merged
merged 1 commit into from
Nov 21, 2024

Conversation

chacha912
Copy link
Contributor

@chacha912 chacha912 commented Nov 21, 2024

What this PR does / why we need it:

The main codebase has been updated to use Protobuf instead of JSON for encoding presence_change data. This migration script converts existing presence_change data from JSON to Protobuf format to match this change.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


Additional documentation:


Checklist:

  • Added relevant tests or not required
  • Addressed and resolved all CodeRabbit review comments
  • Didn't break anything

Summary by CodeRabbit

  • New Features

    • Enhanced migration process for presence changes, converting from string format to a byte array format.
    • Improved error handling during the migration and validation processes.
  • Bug Fixes

    • Addressed issues with processing presence changes to ensure accurate transformation and validation.

Copy link

coderabbitai bot commented Nov 21, 2024

Walkthrough

The changes in this pull request involve modifications to the migrate-presence-change.go file, focusing on the migration of presence changes from string format to byte array format. Key updates include the integration of the encoding/json, innerpresence, and database packages for handling JSON data. The processMigrationBatchPresence function has been revised to unmarshal string representations into structured data and then encode them back into byte arrays. The migration process maintains its overall structure while enhancing error handling and validation.

Changes

File Path Change Summary
migrations/v0.5.6/migrate-presence-change.go - Updated processMigrationBatchPresence to unmarshal strings into innerpresence.PresenceChange structs and encode them as byte arrays.
- Enhanced error handling for unmarshaling and encoding processes.
- MigratePresenceChange and validatePresenceChangeMigration functions have modified internal logic but unchanged signatures.

Possibly related PRs

Suggested reviewers

  • hackerwins

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 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
migrations/v0.5.6/migrate-presence-change.go (1)

88-88: Rename variable bytes to encodedPresenceChange for clarity

For better readability, consider renaming the variable bytes to encodedPresenceChange to clearly reflect its purpose.

Apply this change:

-    bytes, err := database.EncodePresenceChange(p)
+    encodedPresenceChange, err := database.EncodePresenceChange(p)

And update its usage in the update operation:

 operation = mongo.NewUpdateOneModel().SetFilter(bson.M{
     "_id": doc["_id"],
 }).SetUpdate(bson.M{
     "$set": bson.M{
-        "presence_change": bytes,
+        "presence_change": encodedPresenceChange,
     },
 })
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 082224c and 083ab63.

📒 Files selected for processing (1)
  • migrations/v0.5.6/migrate-presence-change.go (2 hunks)

Comment on lines +82 to +91
p := &innerpresence.PresenceChange{}
err := json.Unmarshal([]byte(presenceChangeStr), p)
if err != nil {
return fmt.Errorf("unmarshal presence change: %w", err)
}

bytes, err := database.EncodePresenceChange(p)
if err != nil {
return fmt.Errorf("encode error: %w", err)
}
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Handle individual document errors to prevent migration interruption

Currently, if an error occurs while unmarshaling or encoding a single document's presence change, the entire migration process stops. To enhance robustness, consider logging the error for that document and continuing with the rest of the batch. This ensures that one malformed document doesn't halt the entire migration.

Apply the following changes to handle errors individually:

 if err != nil {
-    return fmt.Errorf("unmarshal presence change: %w", err)
+    fmt.Printf("Warning: failed to unmarshal presence change for document %v: %v\n", doc["_id"], err)
+    continue
 }
 if err != nil {
-    return fmt.Errorf("encode error: %w", err)
+    fmt.Printf("Warning: failed to encode presence change for document %v: %v\n", doc["_id"], err)
+    continue
 }

Committable suggestion skipped: line range outside the PR's diff.

Copy link

codecov bot commented Nov 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.79%. Comparing base (082224c) to head (083ab63).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1075   +/-   ##
=======================================
  Coverage   46.79%   46.79%           
=======================================
  Files          84       84           
  Lines       12219    12219           
=======================================
  Hits         5718     5718           
  Misses       5928     5928           
  Partials      573      573           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

Copy link
Member

@hackerwins hackerwins left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution.

@hackerwins hackerwins merged commit b03f82e into main Nov 21, 2024
5 checks passed
@hackerwins hackerwins deleted the fix-migrate-presence-change branch November 21, 2024 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants