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

Fix duplicate changes when syncing and detaching #896

Merged
merged 2 commits into from
Jun 14, 2024

Conversation

hackerwins
Copy link
Member

@hackerwins hackerwins commented Jun 13, 2024

What this PR does / why we need it:

Fix duplicate changes when syncing and detaching

This commit addresses the issue of duplicate changes being inserted
when PushPull and Detach occur simultaneously. Previously, there was
logic to filter out duplicate changes in PushPull, but during Detach,
ClientInfo's Checkpoint was set to 0, preventing the filtering of
duplicates.

This commit adjusts the order of updates to filter out duplicate
changes before updating ClientInfo's Checkpoint, resolving the problem.

Which issue(s) this PR fixes:

Fixes #895

Special notes for your reviewer:

At first, I added a test, but race condition occurred in CI, so it was removed.

14c9b47#diff-ef76b9ab6c8f9f1b972e664343220c8e06db4b6239ce5b22050e6d68ff66e6f5R210-R246

Does this PR introduce a user-facing change?:


Additional documentation:


Checklist:

  • Added relevant tests or not required
  • Didn't break anything

Summary by CodeRabbit

  • New Features

    • Enhanced PushPull functionality to support additional document statuses, improving document synchronization and status handling.
  • Bug Fixes

    • Improved document status management in DetachDocument and other related functions for consistent state updates.
  • Performance Improvements

    • Optimized benchmarking tests to utilize the new PushPullOptions for better performance insights and accuracy.

Copy link

coderabbitai bot commented Jun 13, 2024

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.

Walkthrough

The recent changes centralize around the introduction of the PushPullOptions struct to the PushPull function and adjustments to document handling during the detach process. This facilitates more robust management of document status and synchronizes changes, especially addressing issues with simultaneous sync and detach calls causing duplicate pushes.

Changes

Files/Modules Change Summary
server/packs/packs.go Added PushPullOptions, adjusted PushPull logic, and enhanced document handling during sync and detach.
server/rpc/yorkie_server.go Modified PushPull and DetachDocument functions to utilize PushPullOptions, improving status management.
test/bench/push_pull_bench_test.go Updated benchmarking functions to use PushPullOptions struct for PushPull calls.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant yorkieServer
    participant packs
    participant Database

    Client->>+yorkieServer: PushPull(pack, {Mode, Status})
    yorkieServer->>+packs: PushPull(ctx, backend, project, clientInfo, docInfo, pack, {Mode, Status})
    packs->>+Database: Store pushed changes, update docs and checkpoints
    packs-->+yorkieServer: Response
    yorkieServer-->>Client: Response

    Client->>+yorkieServer: DetachDocument
    yorkieServer->>+packs: PushPull(ctx, backend, project, clientInfo, docInfo, pack, {Mode, Status:Removed})
    packs->>+Database: Update document status
    packs-->+yorkieServer: Response
    yorkieServer-->>Client: Response
Loading

Assessment against linked issues

Objective (Issue #) Addressed Explanation
Prevent duplicate change pushes ( #895 )
Ensure status is correctly managed during PushPull and DetachDocument ( #895 )
Correct client and document status handling during simultaneous sync and detach calls ( #895 )

Poem

In the land where code does thrive,
Yorkie’s changes come alive.
PushPull options clear the way,
So duplicate bugs no longer stay. ✨
Sync and detach with grace,
Our docs now stay in place.📄


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

codecov bot commented Jun 13, 2024

Codecov Report

Attention: Patch coverage is 82.60870% with 4 lines in your changes missing coverage. Please review.

Project coverage is 50.74%. Comparing base (23b3662) to head (b0ca415).

Files Patch % Lines
server/rpc/yorkie_server.go 82.60% 3 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #896      +/-   ##
==========================================
+ Coverage   50.64%   50.74%   +0.09%     
==========================================
  Files          70       70              
  Lines       10466    10473       +7     
==========================================
+ Hits         5301     5315      +14     
+ Misses       4637     4631       -6     
+ Partials      528      527       -1     

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

@hackerwins
Copy link
Member Author

Screenshot 2024-06-13 at 8 24 47 PM

@hackerwins hackerwins marked this pull request as ready for review June 13, 2024 11:27
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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 23b3662 and b0ca415.

Files selected for processing (3)
  • server/packs/packs.go (5 hunks)
  • server/rpc/yorkie_server.go (6 hunks)
  • test/bench/push_pull_bench_test.go (4 hunks)
Additional context used
golangci-lint
server/packs/packs.go

[warning] 501-501: unused-parameter: parameter 'depth' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 632-632: unused-parameter: parameter 'depth' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 785-785: unused-parameter: parameter 'depth' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 94-94: unused-parameter: parameter 'parent' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 118-118: unused-parameter: parameter 'parent' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 187-187: unused-parameter: parameter 'parent' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 30-30: unused-parameter: parameter 'cmd' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 34-34: unused-parameter: parameter 'cmd' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 31-31: unused-parameter: parameter 'cmd' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 332-332: unused-parameter: parameter 'value' seems to be unused, consider removing or renaming it as _ (revive)

test/bench/push_pull_bench_test.go

[warning] 501-501: unused-parameter: parameter 'depth' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 632-632: unused-parameter: parameter 'depth' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 785-785: unused-parameter: parameter 'depth' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 94-94: unused-parameter: parameter 'parent' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 118-118: unused-parameter: parameter 'parent' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 187-187: unused-parameter: parameter 'parent' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 30-30: unused-parameter: parameter 'cmd' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 34-34: unused-parameter: parameter 'cmd' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 31-31: unused-parameter: parameter 'cmd' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 332-332: unused-parameter: parameter 'value' seems to be unused, consider removing or renaming it as _ (revive)

server/rpc/yorkie_server.go

[warning] 501-501: unused-parameter: parameter 'depth' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 632-632: unused-parameter: parameter 'depth' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 785-785: unused-parameter: parameter 'depth' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 94-94: unused-parameter: parameter 'parent' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 118-118: unused-parameter: parameter 'parent' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 187-187: unused-parameter: parameter 'parent' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 30-30: unused-parameter: parameter 'cmd' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 34-34: unused-parameter: parameter 'cmd' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 31-31: unused-parameter: parameter 'cmd' seems to be unused, consider removing or renaming it as _ (revive)


[warning] 332-332: unused-parameter: parameter 'value' seems to be unused, consider removing or renaming it as _ (revive)

Additional comments not posted (5)
server/packs/packs.go (3)

50-57: Introduced PushPullOptions struct to encapsulate Mode and Status for document synchronization.

This struct enhances code readability and maintainability by grouping related parameters together, which is a good practice in software design.


Line range hint 71-88: Refactored PushPull function to use PushPullOptions.

The refactoring centralizes the handling of synchronization modes and document statuses, making the function's signature cleaner and its behavior easier to understand and maintain.

Also applies to: 96-112, 130-158


98-109: Enhanced error handling for document state updates.

The addition of error checks after updating document status (removed, detached, checkpoint update) ensures the function's robustness by handling potential failures gracefully.

test/bench/push_pull_bench_test.go (1)

147-150: Updated benchmark tests to use PushPullOptions struct.

Consistent use of the new struct across all benchmark functions ensures that the tests are aligned with the latest changes in the main codebase, maintaining the relevance and accuracy of the benchmarks.

Also applies to: 177-180, 187-190, 220-223, 259-262, 269-272

server/rpc/yorkie_server.go (1)

164-167: Updated server functions to use PushPullOptions struct.

The changes in PushPull, DetachDocument, PushPullChanges, and RemoveDocument functions to use the new struct are correctly implemented. This ensures that the server's document handling logic is consistent with the updated synchronization logic.

Also applies to: 258-261, 349-352, 541-544

Copy link
Contributor

@chacha912 chacha912 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 the PR 🙏.

@hackerwins hackerwins merged commit db1b28a into main Jun 14, 2024
4 checks passed
@hackerwins hackerwins deleted the concurrent-sync-and-detach branch June 14, 2024 00:50
@coderabbitai coderabbitai bot mentioned this pull request Jun 14, 2024
2 tasks
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.

Duplicate changes pushes during simultaneous sync and detach calls
2 participants