Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SMA calculations for fleet rates in VaultRatesService (#852) #862

Merged
merged 1 commit into from
Mar 14, 2025
Merged

Conversation

halaprix
Copy link
Member

@halaprix halaprix commented Mar 14, 2025

This update introduces the calculation of 24-hour, 7-day, and 30-day simple moving averages (SMA) for fleet interest rates. The new structure includes an 'sma' object in the FleetRateResult interface, which aggregates these values for each fleet address. The implementation fetches hourly and daily rates in parallel and processes them to compute the SMAs, enhancing the data returned by the VaultRatesService.

Description

[Provide a brief description of the changes in this PR]

Changes

  • [List the main changes made in bullet points]

Benefits

  1. [List the benefits of these changes] 2.

Testing

[Describe how these changes were tested or how they can be tested]

Next steps

  • [List any follow-up actions or considerations]

Additional Notes

[Any additional information, context, or notes for reviewers]

Please review and provide any feedback or suggestions for improvement.

Description

[Provide a brief description of the changes in this PR]

Changes

  • [List the main changes made in bullet points]

Benefits

  1. [List the benefits of these changes]

Testing

[Describe how these changes were tested or how they can be tested]

Next steps

  • [List any follow-up actions or considerations]

Additional Notes

[Any additional information, context, or notes for reviewers]

Please review and provide any feedback or suggestions for improvement.

Summary by CodeRabbit

  • New Features
    • Fleet rate responses now include computed simple moving averages (SMAs) for 24-hour, 7-day, and 30-day periods, providing enhanced insights into historical trends.

This update introduces the calculation of 24-hour, 7-day, and 30-day
simple moving averages (SMA) for fleet interest rates. The new structure
includes an 'sma' object in the FleetRateResult interface, which
aggregates these values for each fleet address. The implementation
fetches hourly and daily rates in parallel and processes them to compute
the SMAs, enhancing the data returned by the VaultRatesService.

## Description
[Provide a brief description of the changes in this PR]

## Changes
- [List the main changes made in bullet points]

## Benefits
1. [List the benefits of these changes]
2.
3.

## Testing
[Describe how these changes were tested or how they can be tested]

## Next steps
- [List any follow-up actions or considerations]

## Additional Notes
[Any additional information, context, or notes for reviewers]

Please review and provide any feedback or suggestions for improvement.
Copy link
Contributor

coderabbitai bot commented Mar 14, 2025

Walkthrough

The update extends the getLatestRates method. It now fetches hourly and daily rates in parallel, computes simple moving averages (SMA) for 24h, 7d, and 30d, and adds an sma property to FleetRateResult to store these values.

Changes

File Path Change Summary
summerfi-api/.../src/db-service.ts Added sma field (with sma24h, sma7d, sma30d) to FleetRateResult; Expanded getLatestRates to query multiple tables and compute SMAs.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Service as getLatestRates
    participant DB1 as fleetInterestRate
    participant DB2 as hourlyFleetInterestRate
    participant DB3 as dailyFleetInterestRate

    Client->>Service: Request Latest Rates
    Service->>DB1: Query fleet rates
    Service->>DB2: Query hourly rates
    Service->>DB3: Query daily rates
    DB1-->>Service: Return fleet rates
    DB2-->>Service: Return hourly rates
    DB3-->>Service: Return daily rates
    Service->>Service: Compute SMAs (24h, 7d, 30d)
    Service->>Client: Return aggregated data
Loading

Poem

A new field takes the stage,
Parallel queries engage.
SMAs calculated with care,
Code refined with flair.
Cheers to progress everywhere!

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

Scope: all 3 workspace projects
 ERR_PNPM_OPTIONAL_DEPS_REQUIRE_PROD_DEPS  Optional dependencies cannot be installed without production dependencies

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)
  • We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
    - To enable this feature, set early_access to true under in the settings.

📜 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 40df882 and eaf5c22.

📒 Files selected for processing (1)
  • summerfi-api/get-vault-rates-function/src/db-service.ts (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Build and Integration Test
  • GitHub Check: Build and Unit Test
🔇 Additional comments (11)
summerfi-api/get-vault-rates-function/src/db-service.ts (11)

32-36: No critical issues found.


152-159: No concerns.


161-168: All clear.


169-176: Seems fine.


178-187: No problems here.


189-201: Good to go.


203-207: No issues noted.


208-218: Looks good.


219-229: Works as intended.


231-241: Checks out.


263-274: No high priority findings.

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

@halaprix halaprix merged commit c4b893a into dev Mar 14, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants