feat: add more logs

[swift1337]

This will help debug potential issues in live networks. Also, host renames to p2p_host to avoid collission with machine's host name

Summary by CodeRabbit

• Bug Fixes
  • Error messages now include timeout durations for improved clarity when operations time out.
• Style
  • Log messages updated for greater detail and consistency, including additional contextual information such as peer IDs and message IDs.
  • Log field names changed from "host" and "leader" to "p2p_host" and "p2p_leader" for improved clarity.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes update error messages and logging across several components to include more contextual information, such as timeout durations and message identifiers. Additionally, the string values of certain logging constants are revised to clarify their association with P2P operations. No modifications to logic, control flow, or public API signatures are introduced.

Changes

File(s)	Change Summary
keysign/signature_notifier.go	Enhanced error message in sendOneMsgToPeer to include the acknowledgment timeout duration in the error context.
logs/fields.go	Updated the values of Host and Leader constants from "host"/"leader" to "p2p_host"/"p2p_leader".
p2p/party_coordinator.go	Modified error wrapping in joinPartyMember to append the timeout duration to the error message for non-success leader responses.
tss/keysign.go	Expanded logging context in generateSignature and KeySign methods to include peer IDs, message IDs, and other relevant details.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server
    participant Peer
    participant Leader

    Client->>Server: Request KeySign
    Server->>Server: generateSignature()
    alt Party formation fails
        Server->>Server: Log error with peer info, leader, online count, block height, blame leader
        Server-->>Client: Return error
    else Party formed
        Server->>Peer: Send signature request
        Peer-->>Server: Respond
        Server->>Server: waitForSignatures()
        alt Signature received
            Server->>Server: Log debug with message ID
            Server-->>Client: Return signature
        else Timeout or error
            Server->>Server: Log error with message ID and error
            Server-->>Client: Return error
        end
    end

Loading

sequenceDiagram
    participant Coordinator
    participant Leader

    Coordinator->>Leader: joinPartyMember request
    Leader-->>Coordinator: Response (success or timeout)
    alt Response not success
        Coordinator->>Coordinator: Wrap timeout error with duration context
        Coordinator-->>Caller: Return wrapped error
    else Success
        Coordinator-->>Caller: Proceed as normal
    end

Loading

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

---

📜 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 940cfad and 88700a4.

📒 Files selected for processing (1)

• tss/keysign.go (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• tss/keysign.go

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: test go 1.22

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.