(OraklNode) log redis latency

[nick-bisonai]

Description

temporary update to log pubsub latency for global aggregate and proof

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]

Walkthrough

Walkthrough

The recent changes enhance the SubmissionData structure by adding a PublishTime field, allowing better tracking of submission times. Modifications to logging in the Collector class improve visibility into data processing delays. Overall, these updates provide additional context for submissions and streamline log outputs, contributing to improved monitoring and functionality within the codebase.

Changes

File	Change Summary
node/pkg/aggregator/types.go	Added PublishTime field to SubmissionData struct to store submission timestamps.
node/pkg/aggregator/utils.go	Initialized PublishTime in PublishGlobalAggregateAndProof function with the current time.
node/pkg/dal/collector/collector.go	Modified logging in processIncomingData: removed value from warnings and added logging for delays exceeding 100 milliseconds.

Poem

In the burrow deep, where code does flow,
A PublishTime added, watch it grow!
With logs now clearer, delays in sight,
Our data dances, oh what a delight!
Hops of joy for each change anew,
Let's celebrate with a carrot or two! 🥕✨

---

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

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

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 64cdb55 and 966b44e.

Files selected for processing (3)

• node/pkg/aggregator/types.go (1 hunks)
• node/pkg/aggregator/utils.go (1 hunks)
• node/pkg/dal/collector/collector.go (1 hunks)

Additional comments not posted (3)

node/pkg/aggregator/types.go (1)

37-37: LGTM! Addition of PublishTime field is appropriate.

The new field PublishTime enhances the SubmissionData struct by providing temporal context for submissions.

node/pkg/aggregator/utils.go (1)

50-50: LGTM! Initialization of PublishTime is appropriate.

The PublishTime field is correctly initialized with the current time using time.Now(), capturing the moment of publication.

node/pkg/dal/collector/collector.go (1)

167-169: LGTM! Addition of logging for Redis delays is appropriate.

The new logging condition to track delays in data publishing enhances visibility into potential performance issues related to data latency.