chore; use debug for pending tx log

[Larkooo]

Summary by CodeRabbit

• Chores
  • Adjusted logging level for transaction processing messages to improve debugging granularity.

[coderabbitai]

Walkthrough

Ohayo, sensei! The change involves modifying the logging level of a transaction processing message in the Engine implementation from info to debug. This adjustment affects the visibility of the log output without altering the underlying transaction processing logic.

Changes

Files	Change Summary
crates/torii/core/src/engine.rs	Changed logging level from info to debug for a specific transaction message.

Sequence Diagram(s)

sequenceDiagram
    participant Engine
    participant Logger

    Engine->>Logger: Log transaction processing message (info)
    Logger-->>Engine: Log output displayed

    Note over Engine: After change

    Engine->>Logger: Log transaction processing message (debug)
    Logger-->>Engine: Log output displayed

Loading

Tip

We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1d95782 and e19fedc.

Files selected for processing (1)

• crates/torii/core/src/engine.rs (1 hunks)

Additional comments not posted (1)

crates/torii/core/src/engine.rs (1)

206-206: Ohayo sensei! The log level change looks good to me.

Reducing the verbosity of this log statement from info to debug is a sensible adjustment. It aligns with the purpose of providing more granular visibility for debugging without cluttering the general log output.

---

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

[glihm]

@Larkooo this is the only one annoying the logs, or we may have a quick pass on them?

[Larkooo]

@Larkooo this is the only one annoying the logs, or we may have a quick pass on them?

This should be main reason the logs fill up quick. As issue with logs only started happening when we enabled index pending to true by default. This is the one that gets spammed on networks like sepolia or mainnet

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 67.86%. Comparing base (1d95782) to head (e19fedc).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
crates/torii/core/src/engine.rs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2383   +/-   ##
=======================================
  Coverage   67.86%   67.86%           
=======================================
  Files         359      359           
  Lines       46959    46959           
=======================================
  Hits        31869    31869           
  Misses      15090    15090           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.