Remove duplicate error handling in authz_vote.go

[meetrick]

This PR removes a redundant error handling block in the authz_vote.go file to improve code clarity and reduce unnecessary code duplication.

hanges:

• Removed the second if err != nil { panic(err) } block after initializing tmClient as it was duplicated and redundant.

Summary by CodeRabbit

• Bug Fixes

  • Improved error handling logic to prevent application crashes due to unhandled errors.

• Chores

  • Refined error management strategy for better application stability.

[coderabbitai]

Walkthrough

The pull request introduces a modification to the error handling logic in the main function of the auth_vote/authz_vote.go file. The previous error-checking mechanism that triggered a panic upon encountering an error has been removed. This change indicates a shift in the approach to error management within the function.

Changes

File	Change Summary
auth_vote/authz_vote.go	Removed panic on error in the main function, altering error handling logic.

Poem

🐇 In the code where errors lay,
A panic once held sway,
Now softly, they drift away,
A new path found, come what may!
Hopping forward, we embrace,
A gentler way to face the race! 🌟

---

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

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.

[meetrick]

@aarmoa Hey, I’ve rebased to the dev branch and created the PR. Could you review it?