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

feat(storage): throw error when file(s) are to large for a configMap) #587

Merged
merged 2 commits into from
Dec 6, 2024

Conversation

smuu
Copy link
Member

@smuu smuu commented Dec 4, 2024

Overview

Summary by CodeRabbit

  • New Features

    • Enhanced error handling for file size limitations, including specific error messages for file size issues.
    • Improved clarity in error reporting for persistent volume claim operations.
  • Bug Fixes

    • Added checks to ensure file sizes do not exceed the 1 MB limit during file addition and management.
    • Introduced new error messages for failed operations related to persistent volume claims and file size issues.
  • Documentation

    • Updated error messages to provide more context and clarity for users encountering issues.

Copy link
Contributor

coderabbitai bot commented Dec 4, 2024

Walkthrough

The changes introduced in this pull request enhance error handling in the instance management functionality. New error variables have been added to the pkg/instance/errors.go file to provide more specific error messages. Additionally, modifications to the pkg/instance/storage.go file include updates to the AddFile and addFileToInstance methods for improved file size checks, as well as error wrapping in the deployVolume and destroyVolume methods for better clarity in error reporting.

Changes

File Change Summary
pkg/instance/errors.go Added new error variables: ErrFailedToCreatePersistentVolumeClaim, ErrFailedToGetFileSize, ErrFileTooLargeCommitted, ErrTotalFilesSizeTooLarge.
pkg/instance/storage.go Updated method signatures for AddFile, addFileToInstance, deployVolume, and destroyVolume to include additional error handling and checks for file sizes.

Poem

In the land of bytes and bits,
New errors join the list,
With files that grow too grand,
Clear messages at hand.
A hop, a skip, through code we prance,
Error handling takes a chance! 🐇✨


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.

tty47
tty47 previously approved these changes Dec 4, 2024
Copy link
Contributor

@tty47 tty47 left a comment

Choose a reason for hiding this comment

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

smart!

Copy link
Contributor

@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)
pkg/instance/storage.go (1)

54-60: Consider making the file size limit configurable

The 1MB size limit is currently hardcoded. Consider making this configurable through a constant or configuration parameter for better flexibility.

+const maxCommittedFileSize = 1024 * 1024 // 1MB
+
 func (s *storage) AddFile(src string, dest string, chown string) error {
   // ...
   if srcInfo.Size() > maxCommittedFileSize {
     return ErrFileTooLargeCommitted.WithParams(src)
   }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ad86999 and 1e686e4.

📒 Files selected for processing (2)
  • pkg/instance/errors.go (2 hunks)
  • pkg/instance/storage.go (3 hunks)
🔇 Additional comments (2)
pkg/instance/errors.go (1)

Line range hint 218-230: LGTM: Well-defined error types for file size limits

The new error types are well-structured and provide clear messages for:

  • PersistentVolumeClaim operations
  • File size checks
  • Total files size limit
pkg/instance/storage.go (1)

334-337: LGTM: Proper error handling for volume claim creation

The error wrapping is well-implemented and follows the established pattern in the codebase.

pkg/instance/storage.go Outdated Show resolved Hide resolved
Copy link
Contributor

@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

🧹 Outside diff range and nitpick comments (1)
pkg/instance/storage.go (1)

60-61: Enhance error messages with file size details

Including the actual file size and the maximum allowed size in the error messages for ErrFileTooLargeCommitted and ErrTotalFilesSizeTooLarge would provide clearer feedback to users and aid in debugging.

For example:

- return ErrFileTooLargeCommitted.WithParams(src)
+ return ErrFileTooLargeCommitted.WithParams(src, srcInfo.Size(), maxTotalFilesBytes)

- return ErrTotalFilesSizeTooLarge.WithParams(dstPath)
+ return ErrTotalFilesSizeTooLarge.WithParams(dstPath, size, maxTotalFilesBytes)

Ensure the error constructors are updated to accept and display these additional parameters.

Also applies to: 299-300

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 1e686e4 and 136aa79.

📒 Files selected for processing (1)
  • pkg/instance/storage.go (4 hunks)
🔇 Additional comments (4)
pkg/instance/storage.go (4)

19-19: Defining a constant for maximum total file size

Defining maxTotalFilesBytes as a constant improves maintainability and makes it easier to adjust the limit in the future if needed.


56-62: Enforce individual file size limit in AddFile method

Adding a check to ensure that each source file does not exceed maxTotalFilesBytes enhances error handling by preventing oversized files from being added.


286-301: Implement cumulative file size check in addFileToInstance method

Calculating the total size of all files and enforcing a cumulative size limit ensures that the aggregate size stays within the allowed threshold, which improves stability.


336-339: Improved error wrapping in deployVolume method

Wrapping the error when creating persistent volume claims provides more context and improves error reporting, aiding in troubleshooting.

Copy link
Member

@mojtaba-esk mojtaba-esk left a comment

Choose a reason for hiding this comment

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

Nice one, thanks!

@smuu smuu merged commit c435ce0 into main Dec 6, 2024
12 of 13 checks passed
@smuu smuu deleted the smuu/20241204-check-file-size branch December 6, 2024 10:17
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