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: potential inconsistent ledger creation #699

Merged
merged 1 commit into from
Feb 20, 2025

Conversation

gfyrag
Copy link
Contributor

@gfyrag gfyrag commented Feb 20, 2025

No description provided.

@gfyrag gfyrag requested a review from a team as a code owner February 20, 2025 14:33
Copy link

coderabbitai bot commented Feb 20, 2025

Walkthrough

The changes update the ledger creation process in the storage driver. The CreateLedger method now performs a preliminary check for ledger creation in the system store and distinguishes constraint errors by returning a specific error. It then handles bucket initialization by checking if the bucket is already initialized and up to date, adding the ledger if so; otherwise, it performs a migration before adding the ledger. Correspondingly, the related test has been modified by removing the expectation for a bucket addition call.

Changes

File Summary of Changes
internal/.../driver.go Updated CreateLedger with refined error handling for constraint violations, added logic to check bucket initialization/up-to-dateness, and perform migration only if the bucket is not initialized.
internal/.../driver_test.go Removed the expectation for the AddLedger method in TestLedgersCreate to reflect the updated flow in ledger creation.

Sequence Diagram(s)

sequenceDiagram
    actor Client as Client
    participant Driver as CreateLedger
    participant Store as SystemStore
    participant Bucket as Bucket

    Client->>Driver: CreateLedger(ctx, ledger)
    Driver->>Store: Attempt ledger creation
    alt Error occurs
        Driver->>Driver: Check error type
        alt Constraint violation
            Driver->>Client: Return "LedgerAlreadyExists" error
        else Other error
            Driver->>Client: Return resolved error
        end
    else Creation successful
        Driver->>Bucket: Check initialization status
        alt Bucket initialized
            Driver->>Bucket: Verify up-to-date status
            alt Bucket outdated
                Driver->>Client: Return "Bucket outdated" error
            else Bucket up-to-date
                Driver->>Bucket: Add ledger to bucket
                Driver->>Client: Return success
            end
        else Bucket not initialized
            Driver->>Bucket: Migrate bucket
            Driver->>Bucket: Add ledger to bucket
            Driver->>Client: Return success
        end
    end
Loading

Poem

I'm a rabbit with a hop so light,
In code I dance through day and night.
Ledgers now with errors clear,
Buckets migrate, the path is dear.
With logic crisp and flow so neat,
I celebrate these changes with a joyful beat!
🐰🌟

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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.

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

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9a6633c and 5556050.

📒 Files selected for processing (2)
  • internal/storage/driver/driver.go (2 hunks)
  • internal/storage/driver/driver_test.go (0 hunks)
💤 Files with no reviewable changes (1)
  • internal/storage/driver/driver_test.go
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Tests
🔇 Additional comments (2)
internal/storage/driver/driver.go (2)

42-47: LGTM! Improved error handling for ledger creation.

The enhanced error handling now properly distinguishes between constraint violations (duplicate ledgers) and other database errors, helping prevent inconsistent ledger states.


64-66: LGTM! Added proper error handling for ledger addition to bucket.

The error handling ensures that any failures during ledger addition are properly caught and reported, preventing potential inconsistencies.

Comment on lines +67 to 73
} else {
if err := b.Migrate(
ctx,
migrations.WithLockRetryInterval(d.migratorLockRetryInterval),
); err != nil {
return nil, fmt.Errorf("migrating bucket: %w", err)
}
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add ledger to bucket after migration.

When the bucket is not initialized, the code performs migration but doesn't add the ledger to the bucket afterward. This could lead to an inconsistent state where the ledger exists in the system store but not in the bucket.

Apply this diff to fix the issue:

 } else {
   if err := b.Migrate(
     ctx,
     migrations.WithLockRetryInterval(d.migratorLockRetryInterval),
   ); err != nil {
     return nil, fmt.Errorf("migrating bucket: %w", err)
   }
+  if err := b.AddLedger(ctx, *l); err != nil {
+    return nil, fmt.Errorf("adding ledger to bucket after migration: %w", err)
+  }
 }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
} else {
if err := b.Migrate(
ctx,
migrations.WithLockRetryInterval(d.migratorLockRetryInterval),
); err != nil {
return nil, fmt.Errorf("migrating bucket: %w", err)
}
} else {
if err := b.Migrate(
ctx,
migrations.WithLockRetryInterval(d.migratorLockRetryInterval),
); err != nil {
return nil, fmt.Errorf("migrating bucket: %w", err)
}
if err := b.AddLedger(ctx, *l); err != nil {
return nil, fmt.Errorf("adding ledger to bucket after migration: %w", err)
}

Copy link

codecov bot commented Feb 20, 2025

Codecov Report

Attention: Patch coverage is 42.85714% with 8 lines in your changes missing coverage. Please review.

Project coverage is 81.61%. Comparing base (9a6633c) to head (5556050).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
internal/storage/driver/driver.go 42.85% 5 Missing and 3 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #699      +/-   ##
==========================================
- Coverage   81.63%   81.61%   -0.03%     
==========================================
  Files         131      131              
  Lines        7085     7086       +1     
==========================================
- Hits         5784     5783       -1     
- Misses       1000     1002       +2     
  Partials      301      301              

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

@gfyrag gfyrag added this pull request to the merge queue Feb 20, 2025
Merged via the queue into main with commit bf5b817 Feb 20, 2025
8 of 10 checks passed
@gfyrag gfyrag deleted the fix/inconsistent-ledger-creation branch February 20, 2025 14:54
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.

3 participants