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

[TRA-483] Implement functionality to acquire next perpetual id #1872

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

shrenujb
Copy link
Contributor

@shrenujb shrenujb commented Jul 8, 2024

Changelist

This change adds a new store key to store the next perpetual id to be used and getter/setter functions
Also provides a function to acquire a new perpetual id

Test Plan

Added 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 new functions for managing perpetual IDs, including retrieval, setting, and acquisition.
  • Tests

    • Enhanced tests to verify the correct acquisition and increment of perpetual IDs.

Signed-off-by: Shrenuj Bansal <shrenuj@dydx.exchange>
Copy link

linear bot commented Jul 8, 2024

Copy link
Contributor

coderabbitai bot commented Jul 8, 2024

Walkthrough

The changes introduce functionality to manage perpetual IDs within the perpetuals module of the protocol. This includes new functions to retrieve, set, and acquire the next perpetual ID, ensuring a systematic and consistent way to handle these IDs. Additionally, constants necessary for these changes are added to the module's keys file, and corresponding tests have been updated to verify the new functionality.

Changes

File(s) Summary
protocol/x/perpetuals/... Added GetNextPerpetualID, SetNextPerpetualID, AcquireNextPerpetualID in Keeper
protocol/x/perpetuals/... Updated TestAcquireNextPerpetualID to verify perpetual ID acquisition and increment logic
protocol/x/perpetuals/... Added NextPerpetualIDKey constant to keys file

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Keeper
    participant ModuleStore

    User->>Keeper: Call AcquireNextPerpetualID()
    Keeper->>ModuleStore: Get current NextPerpetualID
    ModuleStore-->>Keeper: Return current NextPerpetualID
    Keeper->>Keeper: Increment NextPerpetualID
    Keeper->>ModuleStore: Set new NextPerpetualID
    Keeper-->>User: Return new PerpetualID
Loading

Poem

🎋 Amid the lines of code we see,
A Keeper and its trusty key.
Perpetual IDs orderly flow,
In the realm where changes grow.
Tests ensure they do their part,
In software, a work of art! 🐇


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>.
    • 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 Configration 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: 2

Outside diff range and nitpick comments (1)
protocol/x/perpetuals/keeper/perpetual_test.go (1)

3124-3154: Add more assertions to ensure robustness.

The test function covers the intended functionality well. However, consider adding assertions to check for edge cases, such as when no perpetuals exist initially or when IDs reach their maximum value.

	// Ensure no perpetuals exist initially
	pc = keepertest.PerpetualsKeepers(t)
	require.Equal(t, uint32(0), pc.PerpetualsKeeper.GetNextPerpetualID(pc.Ctx))

	// Test acquiring the next perpetual ID when no perpetuals exist
	nextPerpetualId = pc.PerpetualsKeeper.AcquireNextPerpetualID(pc.Ctx)
	require.Equal(t, uint32(1), nextPerpetualId)

	// Ensure the next perpetual ID is stored correctly
	nextPerpetualIdFromStore = pc.PerpetualsKeeper.GetNextPerpetualID(pc.Ctx)
	require.Equal(t, nextPerpetualId+1, nextPerpetualIdFromStore)

	// Test edge case for maximum value
	pc.PerpetualsKeeper.SetNextPerpetualID(pc.Ctx, math.MaxUint32)
	require.Panics(t, func() {
		pc.PerpetualsKeeper.AcquireNextPerpetualID(pc.Ctx)
	})
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1f244fe and d66cd90.

Files selected for processing (3)
  • protocol/x/perpetuals/keeper/perpetual.go (2 hunks)
  • protocol/x/perpetuals/keeper/perpetual_test.go (1 hunks)
  • protocol/x/perpetuals/types/keys.go (1 hunks)
Files skipped from review due to trivial changes (1)
  • protocol/x/perpetuals/types/keys.go
Additional comments not posted (1)
protocol/x/perpetuals/keeper/perpetual.go (1)

1529-1534: LGTM!

The function correctly sets the next perpetual ID in the store.

protocol/x/perpetuals/keeper/perpetual.go Show resolved Hide resolved
Comment on lines +1536 to +1550
// AcquireNextPerpetualID returns the next perpetual id to be used and increments the next perpetual id
func (k Keeper) AcquireNextPerpetualID(ctx sdk.Context) uint32 {
nextID := k.GetNextPerpetualID(ctx)
// if perpetual id already exists, increment until we find one that doesn't
for {
_, err := k.GetPerpetual(ctx, nextID)
if err != nil && errorsmod.IsOf(err, types.ErrPerpetualDoesNotExist) {
break
}
nextID++
}

k.SetNextPerpetualID(ctx, nextID+1)
return nextID
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Ensure the loop does not run indefinitely.

Consider adding a maximum limit to the loop to avoid potential infinite loops in case of an unexpected error.

func (k Keeper) AcquireNextPerpetualID(ctx sdk.Context) uint32 {
	nextID := k.GetNextPerpetualID(ctx)
	// if perpetual id already exists, increment until we find one that doesn't
+	maxAttempts := 1000 // or some reasonable limit
+	attempts := 0
	for {
		_, err := k.GetPerpetual(ctx, nextID)
		if err != nil && errorsmod.IsOf(err, types.ErrPerpetualDoesNotExist) {
			break
		}
		nextID++
+		attempts++
+		if attempts >= maxAttempts {
+			panic("Exceeded maximum attempts to acquire a unique perpetual ID")
+		}
	}

	k.SetNextPerpetualID(ctx, nextID+1)
	return nextID
}
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
// AcquireNextPerpetualID returns the next perpetual id to be used and increments the next perpetual id
func (k Keeper) AcquireNextPerpetualID(ctx sdk.Context) uint32 {
nextID := k.GetNextPerpetualID(ctx)
// if perpetual id already exists, increment until we find one that doesn't
for {
_, err := k.GetPerpetual(ctx, nextID)
if err != nil && errorsmod.IsOf(err, types.ErrPerpetualDoesNotExist) {
break
}
nextID++
}
k.SetNextPerpetualID(ctx, nextID+1)
return nextID
}
func (k Keeper) AcquireNextPerpetualID(ctx sdk.Context) uint32 {
nextID := k.GetNextPerpetualID(ctx)
// if perpetual id already exists, increment until we find one that doesn't
maxAttempts := 1000 // or some reasonable limit
attempts := 0
for {
_, err := k.GetPerpetual(ctx, nextID)
if err != nil && errorsmod.IsOf(err, types.ErrPerpetualDoesNotExist) {
break
}
nextID++
attempts++
if attempts >= maxAttempts {
panic("Exceeded maximum attempts to acquire a unique perpetual ID")
}
}
k.SetNextPerpetualID(ctx, nextID+1)
return nextID
}

@shrenujb shrenujb added the pml permissionless market listing label Jul 8, 2024
@shrenujb shrenujb merged commit feb624d into main Jul 8, 2024
18 checks passed
@shrenujb shrenujb deleted the tra483 branch July 8, 2024 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pml permissionless market listing protocol
Development

Successfully merging this pull request may close these issues.

3 participants