(Node) Reduce logs

[nick-bisonai]

Description

Reduce log level that has been spamming logscribe.
these are wrapped in retrial logic and should be okay with lowered log level

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests.

Deployment

• Should publish npm package
• Should publish Docker image

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The pull request introduces a systematic change in logging severity across multiple files within the websocket-related components. The modifications primarily involve downgrading error-level log messages to warning-level messages in websocket connection handling methods, specifically in bingx.go, coinex.go, and utils.go. These changes adjust how certain websocket-related errors are categorized and reported, without altering the underlying error handling logic or method implementations.

Changes

File	Change Summary
node/pkg/websocketfetcher/providers/bingx/bingx.go	Changed websocket read error logging from log.Error() to log.Warn() in customReadFunc
node/pkg/websocketfetcher/providers/coinex/coinex.go	Changed websocket read error logging from log.Error() to log.Warn() in customReadFunc
node/pkg/wss/utils.go	Downgraded logging level from log.Error() to log.Warn() for websocket methods: Dial, Run, Read, Close, and IsAlive

Sequence Diagram

sequenceDiagram
    participant Client
    participant WebsocketUtils
    participant Logger
    
    Client->>WebsocketUtils: Initiate Websocket Connection
    WebsocketUtils->>WebsocketUtils: Attempt Connection
    alt Connection Failure
        WebsocketUtils->>Logger: Log Warning Instead of Error
        WebsocketUtils-->>Client: Return Error
    end

Loading

Possibly related PRs

• (DAL) Remove lint & vet from dal test #1783: Similar logging level modification in CoinexFetcher struct
• (Sentinel) Change unnecessary error log level #2202: Logging level change from Error to Info in app.go
• (Node) Reduce ping error loggings #2295: Logging level adjustment for ping error messages

Suggested reviewers

• Intizar-T

Poem

🐰 Websocket whispers, log levels dance light,
From errors to warnings, a gentler insight.
Bits and bytes flow, with warnings so mild,
No panic, just caution, connection compiled!
A rabbit's soft touch on the logging terrain. 🌐

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 8bfa0b1 and a45fb6b.

📒 Files selected for processing (3)

• node/pkg/websocketfetcher/providers/bingx/bingx.go (1 hunks)
• node/pkg/websocketfetcher/providers/coinex/coinex.go (1 hunks)
• node/pkg/wss/utils.go (4 hunks)

---

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.