fix rfq error marshalling

[trajan0x]

Description

Fix error marshalling in rfq rebalancer

Summary by CodeRabbit

• Bug Fixes
  • Improved error logging messages in the inventory management system to include more detailed error information.

[coderabbitai]

Walkthrough

The update focuses on refining error logging within a specific method of the rebalanceManagerSynapseCCTP structure. The core adjustment involves the enhancement of error message details by switching the format specifier from %w to %v, ensuring more comprehensive error logging.

Changes

File Path	Change Summary
.../rfq/relayer/inventory/synapse.go	Updated error logging to use %v for error values in listen method

🐇🌟
In the code's woven tapestry, a change so small,
Yet through the logs, clarity does call.
Where errors once hid, shy and demure,
Now stand bold, in detail pure.
A rabbit's touch, light and fine,
Brings forth a change, by design.
🌈🐾

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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/coderabbit-overrides.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.

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 672ba6b and 6aadd6d.

Files selected for processing (1)

• services/rfq/relayer/inventory/synapse.go (3 hunks)

Additional comments not posted (4)

services/rfq/relayer/inventory/synapse.go (4)

209-209: The use of %v for logging errors, as mentioned in the PR summary, is correctly implemented here. However, it's important to ensure that logger.Warnf is properly defined and imported in this file, as it's not visible in the provided context. This is crucial for the logging statement to function as expected.

---

230-230: Similar to the previous comment, ensure that logger.Warnf is correctly defined and imported. Additionally, consider enhancing the error message by including more context about the failure, such as the request ID or chain ID, to aid in debugging.

---

236-236: Again, verify the definition and import of logger.Warnf. For consistency and improved error handling, it might be beneficial to include additional context in the log message, similar to the previous suggestion.

---

256-256: As with the previous instances, ensure logger.Warnf is properly defined and imported. Including more context in the log message could significantly aid in troubleshooting and understanding the nature of the error.