fix: Replace panic with proper error handling in RollbackToHeight

[CreeptoGengar]

Description:

This PR improves error handling in the RollbackToHeight function by replacing panic(err) with a proper error return.

This change:

• Follows Go best practices for error handling
• Adds better error context with fmt.Errorf
• Makes the function more predictable and safer to use
• Allows callers to handle errors appropriately

The change is minimal but important for code reliability and maintainability.

Summary by CodeRabbit

• Bug Fixes
  • Improved error handling in the transaction rollback process.
  • Corrected a comment for clarity in the rollback functionality.

[coderabbitai]

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 golangci-lint (1.62.2)

level=warning msg="The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter is no longer relevant. Replaced by copyloopvar."

Walkthrough

The changes focus on improving error handling in the RollbackToHeight method of the transaction store. The modification replaces a panic with an error return statement, enhancing the method's robustness by allowing more graceful error management during the batch writing process. A minor typo correction in a comment was also made, fixing "iterarte" to "iterate" for improved code clarity.

Changes

File	Change Summary
app/peptide/txstore/txstore.go	- Updated RollbackToHeight method to return an error instead of panicking - Corrected typo in comment from "iterarte" to "iterate"

Poem

🐰 A Rollback's Tale of Grace

In code where errors once would leap,
Now gentle returns softly creep
No panic, just a calm descent
With errors neatly, wisely sent
A rabbit's touch of coding might! 🔧

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 06cb9c7 and c51a330.

📒 Files selected for processing (1)

• app/peptide/txstore/txstore.go (2 hunks)

🔇 Additional comments (2)

app/peptide/txstore/txstore.go (2)

72-72: Spelling correction in comment.

The fix from "iterarte" to "iterate" improves clarity, ensuring the comment is easier to read and more accurately conveys the intended meaning.

---

113-113: Improved error handling.

Replacing the panic(...) call with return fmt.Errorf(...) strengthens the function's reliability by allowing callers to handle errors gracefully. This aligns with Go best practices for error handling, preventing abrupt program termination.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.