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 current equity as a pnl tick. #2335

Merged
merged 1 commit into from
Sep 25, 2024
Merged

Conversation

vincentwschau
Copy link
Contributor

@vincentwschau vincentwschau commented Sep 24, 2024

Changelist

Get current equity of vaults for megavault PnL.

Test Plan

Unit tests.

Author/Reviewer Checklist

  • If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
  • If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
  • If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
  • If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
  • If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
  • Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

  • New Features

    • Introduced a utility function to retrieve and organize vault positions for subaccounts, improving data handling.
    • Enhanced historical PnL retrieval to include current equity and additional data points.
  • Bug Fixes

    • Updated test cases to improve accuracy and coverage for vault controller functionalities.
  • Documentation

    • Improved clarity and structure of test cases to reflect comprehensive system states.

@vincentwschau vincentwschau requested a review from a team as a code owner September 24, 2024 19:32
Copy link
Contributor

coderabbitai bot commented Sep 24, 2024

Walkthrough

The changes introduce a new utility function for retrieving vault positions in the vault-controller.ts, enhancing code modularity. The test cases in vault-controller.test.ts are updated to reflect improved accuracy in historical PnL retrieval, incorporating new constants and ensuring comprehensive database entries. The modifications enhance both the functionality and testing coverage related to vault positions and PnL data.

Changes

File Change Summary
indexer/services/comlink/__tests__/controllers/api/v4/vault-controller.test.ts Updated test cases with new constants for improved accuracy, added database entries for comprehensive testing, and modified assertions for historical PnL retrieval.
indexer/services/comlink/src/controllers/api/v4/vault-controller.ts Introduced getVaultPositions utility function, refactored existing methods to use this function, and added getPnlTicksWithCurrentTick for enhanced PnL tick handling.

Possibly related PRs

Suggested labels

indexer, protocol

Suggested reviewers

  • shrenujb

Poem

In the vaults where numbers play,
New functions hop and dance today.
With tests that gleam like morning dew,
Precision shines in all we do.
A rabbit's cheer for code so bright,
May it leap to new heights of delight! 🐇✨


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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

Outside diff range and nitpick comments (1)
indexer/services/comlink/src/controllers/api/v4/vault-controller.ts (1)

90-95: Simplify the calculation of currentEquity

You can streamline the calculation of currentEquity by directly reducing the vaultPositions without the intermediate mapping to strings.

Here's a suggested refactor:

-const currentEquity: string = Array.from(vaultPositions.values())
-  .map((position: VaultPosition): string => {
-    return position.equity;
-  }).reduce((acc: string, curr: string): string => {
-    return (Big(acc).add(Big(curr))).toFixed();
-  }, '0');
+const currentEquity: string = Array.from(vaultPositions.values())
+  .reduce((acc: Big, position: VaultPosition) => acc.add(Big(position.equity)), Big(0))
+  .toFixed();

This makes the code more concise and removes the unnecessary .map() step.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1a33334 and 3f3057d.

Files selected for processing (2)
  • indexer/services/comlink/tests/controllers/api/v4/vault-controller.test.ts (8 hunks)
  • indexer/services/comlink/src/controllers/api/v4/vault-controller.ts (6 hunks)
Additional comments not posted (6)
indexer/services/comlink/src/controllers/api/v4/vault-controller.ts (2)

26-26: Importing 'big.js' for precise decimal arithmetic

The import of big.js is appropriate and necessary for accurate calculation of large decimal numbers when summing equities.


72-85: Concurrent data fetching optimizes performance

Using Promise.all to fetch vaultPnlTicks, vaultPositions, and latestBlock concurrently improves performance by initiating multiple asynchronous operations simultaneously.

indexer/services/comlink/__tests__/controllers/api/v4/vault-controller.test.ts (4)

21-21: Proper import of Big.js for precise calculations

The import of Big from 'big.js' is necessary for accurate decimal arithmetic in financial computations within the tests.


26-36: Initialization of test constants enhances readability

The constants for block heights, times, and vault equities are clearly defined and appropriately typed, improving the readability and maintainability of the test setup.


69-73: Adding the latest block to BlockTable

The inclusion of the latest block with correct time and block height ensures that the test cases consider the most recent state of the blockchain.


76-95: Seeding multiple tables with test data

The batch seeding of PerpetualPositionTable, AssetPositionTable, and FundingIndexUpdatesTable is correctly implemented, setting up comprehensive test data for various scenarios.

Comment on lines +326 to +333
]: [
SubaccountFromDatabase[],
AssetFromDatabase[],
PerpetualPositionFromDatabase[],
AssetPositionFromDatabase[],
MarketFromDatabase[],
BlockFromDatabase | undefined,
] = await Promise.all([
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Potential null reference on latestBlock

getVaultPositions obtains latestBlock which may be undefined. Accessing latestBlock.blockHeight without checking if latestBlock is defined can lead to a runtime error.

Add a null check for latestBlock before using it:

if (!latestBlock) {
  throw new Error('Failed to retrieve the latest block.');
}

Alternatively, handle the case where latestBlock is undefined appropriately.

Comment on lines +365 to +410
const latestFundingIndexMap: FundingIndexMap = await FundingIndexUpdatesTable
.findFundingIndexMap(
latestBlock.blockHeight,
);
const assetPositionsBySubaccount:
{ [subaccountId: string]: AssetPositionFromDatabase[] } = _.groupBy(
assetPositions,
'subaccountId',
);
const openPerpetualPositionsBySubaccount:
{ [subaccountId: string]: PerpetualPositionFromDatabase[] } = _.groupBy(
openPerpetualPositions,
'subaccountId',
);
const assetIdToAsset: AssetById = _.keyBy(
assets,
AssetColumns.id,
);

const vaultPositionsAndSubaccountId: {
position: VaultPosition,
subaccountId: string,
}[] = await Promise.all(
subaccounts.map(async (subaccount: SubaccountFromDatabase) => {
const perpetualMarket: PerpetualMarketFromDatabase | undefined = perpetualMarketRefresher
.getPerpetualMarketFromClobPairId(vaultSubaccounts[subaccount.id]);
if (perpetualMarket === undefined) {
throw new Error(
`Vault clob pair id ${vaultSubaccounts[subaccount.id]} does not correspond to a ` +
'perpetual market.');
}
const lastUpdatedFundingIndexMap: FundingIndexMap = await FundingIndexUpdatesTable
.findFundingIndexMap(
subaccount.updatedAtHeight,
);

const subaccountResponse: SubaccountResponseObject = getSubaccountResponse(
subaccount,
openPerpetualPositionsBySubaccount[subaccount.id] || [],
assetPositionsBySubaccount[subaccount.id] || [],
assets,
markets,
perpetualMarketRefresher.getPerpetualMarketsMap(),
latestBlock.blockHeight,
latestFundingIndexMap,
lastUpdatedFundingIndexMap,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Ensure latestBlock is defined before accessing its properties

In the getVaultPositions function, you are accessing latestBlock.blockHeight and passing latestBlock.blockHeight and latestBlock.time to other functions without verifying that latestBlock is not undefined.

Before using latestBlock, add a check to confirm it is defined:

if (!latestBlock) {
  throw new Error('Failed to retrieve the latest block.');
}

This will prevent potential runtime errors due to null or undefined reference.

Comment on lines +126 to +132
const finalTick: PnlTicksFromDatabase = {
...createdPnlTicks[expectedTicksIndex[expectedTicksIndex.length - 1]],
equity: Big(vault1Equity).toFixed(),
blockHeight: latestBlockHeight,
blockTime: latestTime.toISO(),
createdAt: latestTime.toISO(),
};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Refactor repetitive finalTick object construction

The construction of finalTick objects is repeated across multiple test cases with similar logic. Consider refactoring this code into a helper function to reduce duplication and improve maintainability.

For example, you could create a helper function like:

function createFinalTick(
  baseTick: PnlTicksFromDatabase,
  equity: Big,
  blockHeight: string,
  blockTime: DateTime,
): PnlTicksFromDatabase {
  return {
    ...baseTick,
    equity: equity.toFixed(),
    blockHeight,
    blockTime: blockTime.toISO(),
    createdAt: blockTime.toISO(),
  };
}

Then use it in your tests to create finalTick instances:

const finalTick = createFinalTick(
  createdPnlTicks[expectedIndex],
  Big(vault1Equity),
  latestBlockHeight,
  latestTime,
);

This refactoring will make your tests cleaner and more maintainable.

Also applies to: 178-184, 223-229, 268-281

@vincentwschau vincentwschau merged commit 78de680 into main Sep 25, 2024
16 checks passed
@vincentwschau vincentwschau deleted the vincentc/add-current-equity branch September 25, 2024 15:49
@vincentwschau
Copy link
Contributor Author

@Mergifyio backport release/indexer/v7.x

Copy link
Contributor

mergify bot commented Sep 26, 2024

backport release/indexer/v7.x

✅ Backports have been created

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants