add data delay logs to node and dal

[Intizar-T]

Description

Please include a summary of the changes and the related issue.
Please also include relevant motivation and context.
List any dependencies that are required for this change.

Fixes # (issue)

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 updates introduce a new PublishTime field to the SubmissionData struct, enhancing its ability to track publication timestamps. Changes across various files improve logging and monitoring capabilities, particularly for timing discrepancies in data processing. These enhancements facilitate better management and debugging of submission data, ensuring more efficient operations within the application.

Changes

File	Change Summary
node/pkg/aggregator/types.go	Added PublishTime field of type time.Time to SubmissionData, enhancing its functionality for tracking publication timestamps.
node/pkg/aggregator/utils.go	Introduced PublishTime in the PublishGlobalAggregateAndProof function, capturing the current time and adding conditional logging for processing duration.
node/pkg/dal/collector/collector.go	Enhanced processIncomingData method to log warnings based on timing differences related to incoming data, improving monitoring of data processing delays.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Collector
    participant Aggregator
    participant Logger

    Client->>Collector: Send Data
    Collector->>Aggregator: Process SubmissionData
    Aggregator->>Logger: Log PublishTime and Duration
    Logger-->>Aggregator: Log Confirmation
    Aggregator-->>Collector: Acknowledge Processing
    Collector-->>Client: Response

Loading

🐰 In fields of code, I hop with glee,
New timestamps added, so fresh and free!
With logs in tow, we track the time,
Data dances smoothly, oh, how sublime!
For every change, a joyful cheer,
Improvements bloom, the future is clear! 🌼

---

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 89541c1 and c3f816d.

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 (2 hunks)

Additional comments not posted (4)

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

38-39: Addition of PublishTime field is approved.

The PublishTime field enhances the SubmissionData struct by providing a timestamp for when the data is published, which can be useful for tracking and debugging.

---

41-44: Logging statement is approved.

The logging statement improves the function's ability to monitor and log the timing of published data, which may assist in debugging and performance analysis.

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

39-39: Addition of PublishTime field is approved.

The PublishTime field enhances the SubmissionData struct by providing a timestamp for when the data is published, which can be useful for tracking and debugging.

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

161-166: Logging functionality is approved.

The logging functionality enhances the monitoring capabilities by allowing the tracking and logging of potential delays in data handling.