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: backup progress should not add block failed to upload to successful count #209

Merged
merged 1 commit into from
Nov 12, 2024

Conversation

derekbit
Copy link
Member

@derekbit derekbit commented Nov 12, 2024

longhorn/longhorn#9791

Which issue(s) this PR fixes:

Issue #

What this PR does / why we need it:

Special notes for your reviewer:

Additional documentation or context

Summary by CodeRabbit

  • Bug Fixes
    • Enhanced error handling during the block writing and backup mapping processes, allowing for better tracking and logging of issues.
    • Improved clarity of error messages related to backing image size and completion status.
  • Chores
    • Refined the existing backup process without introducing new functionality or altering existing behavior.

Copy link

coderabbitai bot commented Nov 12, 2024

Walkthrough

The changes in this pull request enhance error handling mechanisms in both the backupBlock function of the deltablock.go file and the backupMapping function in backupbackingimage.go. The modifications involve capturing errors immediately from write operations, improving the clarity and reliability of error reporting. Additionally, the RestoreBackingImageBackup function has been updated for better error handling and descriptive messaging. No new functionalities or public entity changes were introduced, maintaining the overall structure and logic of the backup processes.

Changes

File Change Summary
deltablock.go Modified backupBlock function to adjust error handling during block writing; no public entity changes.
backupbackingimage/backupbackingimage.go Updated backupMapping function for improved error handling; enhanced error messages in RestoreBackingImageBackup; no public entity changes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant BackupSystem
    participant BackupStoreDriver

    User->>BackupSystem: Initiate backup
    BackupSystem->>BackupStoreDriver: Write block data
    BackupStoreDriver-->>BackupSystem: Return result (success/error)
    BackupSystem->>User: Report success/error
Loading

🐰 "In the fields where the bunnies play,
We’ve fixed some errors in a clever way.
With each block written, we’ll hop with glee,
For now, our backups are error-free!
So let’s dance and twirl, oh what a sight,
With streamlined processes, everything’s bright!" 🌼


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 70b94cf and 138baaa.

📒 Files selected for processing (2)
  • backupbackingimage/backupbackingimage.go (1 hunks)
  • deltablock.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • deltablock.go
🔇 Additional comments (1)
backupbackingimage/backupbackingimage.go (1)

267-268: LGTM! This change fixes the backup progress counting.

The modification ensures that failed block uploads are not counted towards the successful backup progress by making the error handling more explicit. When a block write fails, the deferred function in backupMapping will properly handle the error and prevent incrementing the progress counter.


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

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b5b0e72 and 70b94cf.

📒 Files selected for processing (1)
  • deltablock.go (1 hunks)

Comment on lines +428 to +429
err = bsDriver.Write(blkFile, rs)
if err != nil {
Copy link

@coderabbitai coderabbitai bot Nov 12, 2024

Choose a reason for hiding this comment

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

💡 Codebase verification

Fix Approved for deltablock.go:428.

However, similar error handling issues were found in backupbackingimage.go:267 where the error from bsDriver.Write is not assigned. Please ensure all bsDriver.Write calls properly handle errors to avoid counting failed uploads as successful.

  • backupbackingimage/backupbackingimage.go:267
🔗 Analysis chain

LGTM! Fix properly captures Write errors.

The change correctly captures and propagates errors from the Write operation, ensuring failed block uploads are not counted as successful.

Let's verify if there are similar patterns in the codebase that might need the same fix:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Look for similar patterns where Write errors might not be captured
# Test: Search for direct Write calls without error assignment
ast-grep --pattern 'bsDriver.Write($_, $_)
if err != nil'

Length of output: 59


Script:

#!/bin/bash
# Description: Look for bsDriver.Write calls without error assignment
# Test: Search for bsDriver.Write calls that do not assign the returned error to a variable
ast-grep --pattern 'bsDriver.Write($_, $_)' --filter '!(parent(expr_stmt) and parent(expr_stmt).expr = "err = bsDriver.Write($_, $_)")'

Length of output: 325


Script:

#!/bin/bash
# Description: Look for bsDriver.Write calls without error assignment
# Test: Search for bsDriver.Write calls not assigned to the err variable
rg -n 'bsDriver\.Write\s*\([^)]*\)\s*(?!\s*err\s*=)'

Length of output: 332


Script:

#!/bin/bash
# Description: Look for bsDriver.Write calls without error assignment
# Test: Search for bsDriver.Write calls not assigned to the err variable using PCRE2
rg -n --pcre2 'bsDriver\.Write\s*\([^)]*\)\s*(?!\s*err\s*=)'

Length of output: 196

Copy link
Member Author

Choose a reason for hiding this comment

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

So clever!

Copy link

Choose a reason for hiding this comment

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

@derekbit, happy to help!

Copy link

codecov bot commented Nov 12, 2024

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 8.08%. Comparing base (b5b0e72) to head (138baaa).
Report is 1 commits behind head on master.

Files with missing lines Patch % Lines
backupbackingimage/backupbackingimage.go 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff            @@
##           master    #209      +/-   ##
=========================================
- Coverage    8.08%   8.08%   -0.01%     
=========================================
  Files          23      23              
  Lines        2535    2536       +1     
=========================================
  Hits          205     205              
- Misses       2303    2304       +1     
  Partials       27      27              
Flag Coverage Δ
unittests 8.08% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Copy link
Member

@innobead innobead left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -264,7 +264,8 @@
return err
}

return bsDriver.Write(blkFile, rs)
err = bsDriver.Write(blkFile, rs)
return err
Copy link
Member

Choose a reason for hiding this comment

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

nit: consider using a returned err variable instead, so updates to the variable won't be missed.

@derekbit derekbit merged commit b405e8f into longhorn:master Nov 12, 2024
7 of 9 checks passed
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