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

Add snapshot-disable-gc flag #874

Merged
merged 1 commit into from
May 24, 2024
Merged

Add snapshot-disable-gc flag #874

merged 1 commit into from
May 24, 2024

Conversation

hackerwins
Copy link
Member

@hackerwins hackerwins commented May 24, 2024

What this PR does / why we need it:

Add snapshot-disable-gc flag

GC defects are found for sequence data types such as Array, Text, and
Tree. This commit provides the option to temporarily turn off GC on
the server.

Which issue(s) this PR fixes:

Related to #723

Special notes for your reviewer:

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

    • Introduced a new configuration option to disable garbage collection for snapshots.
  • Improvements

    • Enhanced document creation with customizable options including the ability to disable garbage collection.
    • Improved server configuration to control snapshot garbage collection behavior.
  • Tests

    • Added new test cases to ensure the correct behavior when garbage collection is disabled.

Copy link

coderabbitai bot commented May 24, 2024

Walkthrough

The recent updates introduce a new boolean flag, SnapshotDisableGC, to control the garbage collection (GC) of snapshots across various components of the system. This flag is propagated through the configuration, document creation, and change application processes, allowing for the selective disabling of GC. Additionally, integration tests have been updated to validate this new functionality.

Changes

Files Change Summary
cmd/yorkie/server.go Added a new boolean flag SnapshotDisableGC to control snapshot garbage collection.
pkg/document/document.go Introduced Options struct and WithDisableGC function to configure document setup with DisableGC option.
pkg/document/internal_document.go Updated ApplyChangePack method to accept disableGC parameter.
server/backend/config.go Added SnapshotDisableGC field to Config struct.
server/config.go Added DefaultSnapshotDisableGC constant with value false.
server/packs/packs.go, server/packs/pushpull.go, server/packs/snapshots.go Modified function calls to include SnapshotDisableGC parameter.
test/integration/gc_test.go Added imports and test case for disabling garbage collection based on server configuration.

🐰
In code we trust, we tweak and mend,
With flags to guide, and bugs to end.
A toggle here, a switch to see,
Disabling GC, our docs run free.
Through tests we march, with code so bright,
Embracing change, we code the night. 🌙

Tip

New Features and Improvements

Review Settings

Introduced new personality profiles for code reviews. Users can now select between "Chill" and "Assertive" review tones to tailor feedback styles according to their preferences. The "Assertive" profile posts more comments and nitpicks the code more aggressively, while the "Chill" profile is more relaxed and posts fewer comments.

AST-based Instructions

CodeRabbit offers customizing reviews based on the Abstract Syntax Tree (AST) pattern matching. Read more about AST-based instructions in the documentation.

Community-driven AST-based Rules

We are kicking off a community-driven initiative to create and share AST-based rules. Users can now contribute their AST-based rules to detect security vulnerabilities, code smells, and anti-patterns. Please see the ast-grep-essentials repository for more information.

New Static Analysis Tools

We are continually expanding our support for static analysis tools. We have added support for biome, hadolint, and ast-grep. Update the settings in your .coderabbit.yaml file or head over to the settings page to enable or disable the tools you want to use.

Tone Settings

Users can now customize CodeRabbit to review code in the style of their favorite characters or personalities. Here are some of our favorite examples:

  • Mr. T: "You must talk like Mr. T in all your code reviews. I pity the fool who doesn't!"
  • Pirate: "Arr, matey! Ye must talk like a pirate in all yer code reviews. Yarrr!"
  • Snarky: "You must be snarky in all your code reviews. Snark, snark, snark!"

Revamped Settings Page

We have redesigned the settings page for a more intuitive layout, enabling users to find and adjust settings quickly. This change was long overdue; it not only improves the user experience but also allows our development team to add more settings in the future with ease. Going forward, the changes to .coderabbit.yaml will be reflected in the settings page, and vice versa.

Miscellaneous

  • Turn off free summarization: You can switch off free summarization of PRs opened by users not on a paid plan using the enable_free_tier setting.
  • Knowledge-base scope: You can now set the scope of the knowledge base to either the repository (local) or the organization (global) level using the knowledge_base setting. In addition, you can specify Jira project keys and Linear team keys to limit the knowledge base scope for those integrations.
  • High-level summary placement: You can now customize the location of the high-level summary in the PR description using the high_level_summary_placeholder setting (default @coderabbitai summary).
  • Revamped request changes workflow: You can now configure CodeRabbit to auto-approve or request changes on PRs based on the review feedback using the request_changes_workflow setting.

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

@hackerwins hackerwins marked this pull request as ready for review May 24, 2024 02:41
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 77e7d16 and 660d521.
Files selected for processing (9)
  • cmd/yorkie/server.go (1 hunks)
  • pkg/document/document.go (4 hunks)
  • pkg/document/internal_document.go (2 hunks)
  • server/backend/config.go (1 hunks)
  • server/config.go (1 hunks)
  • server/packs/packs.go (1 hunks)
  • server/packs/pushpull.go (1 hunks)
  • server/packs/snapshots.go (1 hunks)
  • test/integration/gc_test.go (2 hunks)
Files skipped from review due to trivial changes (1)
  • server/config.go
Additional comments not posted (11)
server/packs/snapshots.go (1)

94-94: Ensure the SnapshotDisableGC flag is correctly propagated through the system.

Verification successful

The SnapshotDisableGC flag is correctly propagated and used throughout the system.

  • server/backend/config.go: Defines the flag.
  • cmd/yorkie/server.go: Sets the flag.
  • server/packs/snapshots.go, server/packs/pushpull.go, server/packs/packs.go: Uses the flag.
  • test/integration/gc_test.go: References the flag in tests.
Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that the SnapshotDisableGC flag is correctly set and used in the system.

# Test: Search for the flag usage in the backend configuration and its propagation.
rg --type go 'SnapshotDisableGC'

Length of output: 763

server/backend/config.go (1)

58-60: The addition of SnapshotDisableGC to the Config struct is correctly implemented.

server/packs/pushpull.go (1)

154-154: Ensure the SnapshotDisableGC flag is correctly propagated through the system.

Verification successful

The SnapshotDisableGC flag is correctly set and propagated through the system. It is defined in the configuration, has a default value, and is used in the relevant parts of the codebase.

  • server/backend/config.go: Definition of the flag.
  • server/config.go: Default value.
  • server/packs/pushpull.go: Usage in the pullSnapshot function.
  • server/packs/snapshots.go: Usage in the ApplyChangePack method.
  • server/packs/packs.go: Usage in another context.
  • test/integration/gc_test.go: Test case setting the flag.
Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that the SnapshotDisableGC flag is correctly set and used in the system.

# Test: Search for the flag usage in the backend configuration and its propagation.
rg --type go 'SnapshotDisableGC'

Length of output: 763

server/packs/packs.go (1)

239-239: Ensure the SnapshotDisableGC flag is correctly propagated through the system.

Verification successful

The SnapshotDisableGC flag is correctly propagated and used throughout the system.

  • server/backend/config.go: Defines the SnapshotDisableGC flag.
  • cmd/yorkie/server.go: Sets the SnapshotDisableGC flag.
  • server/packs/packs.go, server/packs/snapshots.go, server/packs/pushpull.go: Uses the SnapshotDisableGC flag.
  • test/integration/gc_test.go: Contains a test case that sets the SnapshotDisableGC flag.
Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that the SnapshotDisableGC flag is correctly set and used in the system.

# Test: Search for the flag usage in the backend configuration and its propagation.
rg --type go 'SnapshotDisableGC'

Length of output: 763

cmd/yorkie/server.go (1)

294-299: The addition of the backend-snapshot-disable-gc command-line flag is correctly implemented.

pkg/document/internal_document.go (1)

Line range hint 145-169: Ensure the disableGC parameter is correctly used to control garbage collection.

pkg/document/document.go (3)

68-82: Introduced Option type and Options struct to configure document behavior.

This approach using functional options is flexible and allows for future extensions without breaking existing function signatures.


122-130: Updated New function to accept variadic Option parameters.

This change effectively utilizes the functional options pattern, enhancing the configurability of the Document struct without impacting existing code that does not use these new options.


225-227: Added conditional garbage collection based on DisableGC option in ApplyChangePack.

This is a clean implementation that respects the new DisableGC setting, preventing garbage collection when it is set to true.

test/integration/gc_test.go (2)

23-23: Added necessary imports to support new garbage collection tests.

The imports are correctly added to enable the use of necessary functionalities from the client, server, and strconv packages in the tests.

Also applies to: 28-28, 33-33


609-666: Added a new test case to verify that garbage is not collected when DisableGC is true.

This test case is well-structured and effectively checks the functionality of disabling garbage collection through both document-level and server-level configurations.

@hackerwins hackerwins merged commit 3540e8b into main May 24, 2024
4 checks passed
@hackerwins hackerwins deleted the disable-gc branch May 24, 2024 02:58
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.

1 participant