fix(fxevent): slog logger raw errors

[oPOCCOMAXAo]

Related to: #1265

Summary by CodeRabbit

• Refactor
  • Enhanced error logging to capture comprehensive error details, providing richer context and more precise diagnostic information. This update improves how error messages are presented, enabling more accurate troubleshooting and clearer insights when issues arise during use. These improvements are designed to enhance overall system reliability and user experience in error scenarios.

[coderabbitai]

Walkthrough

The changes update the error logging approach in the slog package. In fxevent/slog.go, the function slogErr now returns a logging attribute containing the error object directly via slog.Any instead of converting it to a string with err.Error(). Correspondingly, test cases in fxevent/slog_test.go have been revised to expect errors created using fmt.Errorf, ensuring consistency in error representation.

Changes

File(s)	Change Summary
fxevent/slog.go; fxevent/slog_test.go	Updated error logging: the slogErr function now returns slog.Any with the error object rather than a string, and tests in slog_test.go use fmt.Errorf to create error objects accordingly.

Poem

I'm a little rabbit, hopping through the code,
Where errors once were stringed, now in error mode.
With slog.Any I bound the trouble in a neat ride,
And tests now dance with fmt.Errorf by my side.
Cheers to changes fresh as spring—let the bugs subside!
🐇✨

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 ca61c3d and 1adce26.

📒 Files selected for processing (2)

• fxevent/slog.go (1 hunks)
• fxevent/slog_test.go (11 hunks)

🔇 Additional comments (2)

fxevent/slog.go (1)

271-271: Improved error logging with raw error objects.

This change enhances error logging by passing the raw error object instead of just its string representation. Using slog.Any preserves the complete error structure, including potential wrapped errors and stack traces, which enables better debugging and error analysis in logging systems.

fxevent/slog_test.go (1)

152-152: Tests updated to match new error logging behavior.

The test expectations have been properly updated to verify that raw error objects are being logged instead of error strings. This ensures consistency with the implementation change in slogErr and provides more accurate test coverage for the actual behavior of the logging system.

Also applies to: 180-180, 224-224, 277-277, 308-308, 340-340, 380-380, 397-397, 407-407, 423-423, 431-431, 439-439, 453-453

✨ Finishing Touches

• 📝 Generate Docstrings

---

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