fix(logger): Removed redundant os.Exit call

[softwarespot]

Description

Related Issues (if any)

Type of Changes

Please mark the options that best describe your PR:

• Bug fix
• New feature
• Enhancement
• Refactor
• Documentation update
• CI/CD changes
• Dependencies update
• Other (please specify):

Checklist

• I have read and followed the CONTRIBUTING.md guidelines for this project. (there isn't any!)
• Added unit tests that cover the new/modified code.
• All existing tests pass (``).
• Added or updated documentation if needed (e.g., README.md, code comments).
• Public functions and structs are well-documented using GoDoc conventions.
• If the PR introduces a new feature, it has been documented clearly for users.
• Ensure proper error handling and meaningful error messages.
• Ensure any logging follows best practices (e.g., no excessive or sensitive logging).
• Dependencies added are necessary and minimal.

Additional Notes

This removes a redundant call to os.Exit(), as log.Fatalf() is called before it, which calls os.Exit().

Summary by CodeRabbit

• New Features

  • Enhanced error handling by allowing the program to continue running after logging a fatal error, improving overall stability.

• Bug Fixes

  • Removed unnecessary termination of the application on fatal errors, allowing for better error management.

[coderabbitai]

Walkthrough

The changes involve modifications to the logger/logger.go file, specifically the removal of the os package import and the alteration of the CheckFatalError function. The function no longer terminates the program by calling os.Exit(1) when logging a fatal error, allowing the program to continue running instead of exiting immediately after a fatal error is logged.

Changes

File	Change Summary
logger/logger.go	Removed import "os" and modified CheckFatalError to stop calling os.Exit(1).

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Logger
    User->>Logger: Trigger fatal error
    Logger->>Logger: Log fatal error message
    Logger-->>User: Continue program execution

Loading

🐰 In the land of code, where errors may dwell,
A logger now whispers, "All's fine, do not yell!"
No more abrupt endings, just logs in the night,
With every mishap, the program takes flight!
Hopping along, through errors we glide,
Thanks to the changes, we’ll take them in stride! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4797e8c and 742311b.

📒 Files selected for processing (1)

• logger/logger.go (0 hunks)

💤 Files with no reviewable changes (1)

• logger/logger.go

---

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.

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.