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

chore: remove context.TODO() #64

Merged
merged 1 commit into from
Feb 21, 2025
Merged

chore: remove context.TODO() #64

merged 1 commit into from
Feb 21, 2025

Conversation

tac0turtle
Copy link
Contributor

@tac0turtle tac0turtle commented Feb 20, 2025

closes #33

Summary by CodeRabbit

  • Tests
    • Enhanced test reliability by enforcing controlled execution times for critical operations to prevent indefinite waits and improve overall test robustness.

Copy link
Contributor

coderabbitai bot commented Feb 20, 2025

Walkthrough

This PR updates the context management in several test files by replacing context.TODO() with context.WithTimeout() set to a 3-second timeout. In each modified test case, the newly created context is properly canceled using defer cancel(), ensuring that methods such as InitChain, GetTxs, ExecuteTxs, and SetFinal do not run indefinitely.

Changes

Files Change Summary
proxy/grpc/client_server_test.go, proxy/grpc/proxy_test.go Replaced context.TODO() with context.WithTimeout() (3s) for the InitChain and GetTxs calls. Added defer cancel() to ensure resources are released after method calls.
test/suite.go Updated context management by replacing multiple context.TODO() calls with context.WithTimeout() (3s) across methods (InitChain, GetTxs, ExecuteTxs, and SetFinal). Introduced additional timeout contexts in TestSetFinal for sequential calls.

Sequence Diagram(s)

sequenceDiagram
    participant Test as Test Code
    participant Ctx as Context (3s Timeout)
    participant Client as Client Method

    Test->>Ctx: Create context with 3s timeout
    Test->>Client: Call method using context
    alt Operation completes in time
        Client-->>Test: Return successful response
    else Operation exceeds timeout
        Client-->>Test: Return timeout error
    end
    Test->>Ctx: Cancel context with defer cancel()
Loading

Possibly related PRs

Suggested reviewers

  • tuxcanfly
  • yarikbratashchuk
  • Manav-Aggarwal
  • gupadhyaya

Poem

I hopped through tests with a keen, swift pace,
Leaving TODO() behind in a faster race.
With a 3-sec timeout in each playful call,
I cancel with a flourish, no task will stall.
In code fields I scamper, with a bunny's delight,
Celebrating these changes in the moonlit night!
🐇💻

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

@RollkitBot RollkitBot requested review from a team, tuxcanfly, MSevey and Manav-Aggarwal and removed request for a team February 20, 2025 15:48
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: 0

🧹 Nitpick comments (3)
proxy/grpc/proxy_test.go (1)

68-74: LGTM! Good improvement in context management.

The changes properly handle context lifecycle with timeout and cancellation. The 3-second timeout per attempt with 100ms sleep between retries provides good balance between responsiveness and reliability.

Consider extracting the timeout duration to a constant for better maintainability:

+const defaultTestTimeout = 3 * time.Second
+
 for i := 0; i < 10; i++ {
-    ctx, cancel := context.WithTimeout(context.Background(), 3*time.Second)
+    ctx, cancel := context.WithTimeout(context.Background(), defaultTestTimeout)
     if _, err := client.GetTxs(ctx); err == nil {
         cancel()
         break
     }
     cancel()
     time.Sleep(100 * time.Millisecond)
 }
proxy/grpc/client_server_test.go (1)

73-75: LGTM! Consider aligning timeout with config.

The changes properly handle context lifecycle. However, the 3-second timeout is different from the config's DefaultTimeout of 5 seconds.

Consider using the config's timeout for consistency:

-    ctx, cancel := context.WithTimeout(context.Background(), 3*time.Second)
+    ctx, cancel := context.WithTimeout(context.Background(), config.DefaultTimeout)
     defer cancel()
     stateRoot, maxBytes, err := client.InitChain(ctx, genesisTime, initialHeight, chainID)
test/suite.go (1)

84-98: LGTM! Good context management in TestSetFinal.

The changes properly handle context lifecycle with separate timeouts for each operation.

Consider extracting the timeout duration to a constant for better maintainability:

+const defaultTestTimeout = 3 * time.Second
+
-    ctx, cancel := context.WithTimeout(context.Background(), 3*time.Second)
+    ctx, cancel := context.WithTimeout(context.Background(), defaultTestTimeout)
     defer cancel()
     err := s.Exec.SetFinal(ctx, 1)
     s.Require().Error(err)

-    ctx2, cancel2 := context.WithTimeout(context.Background(), 3*time.Second)
+    ctx2, cancel2 := context.WithTimeout(context.Background(), defaultTestTimeout)
     defer cancel2()
     _, _, err = s.Exec.ExecuteTxs(ctx2, nil, 2, time.Now(), types.Hash("test state"))
     s.Require().NoError(err)

-    ctx3, cancel3 := context.WithTimeout(context.Background(), 3*time.Second)
+    ctx3, cancel3 := context.WithTimeout(context.Background(), defaultTestTimeout)
     defer cancel3()
     err = s.Exec.SetFinal(ctx3, 2)
     s.Require().NoError(err)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c1157f4 and 57ef771.

📒 Files selected for processing (3)
  • proxy/grpc/client_server_test.go (1 hunks)
  • proxy/grpc/proxy_test.go (1 hunks)
  • test/suite.go (3 hunks)
🔇 Additional comments (3)
test/suite.go (3)

31-34: LGTM! Good context management in TestInitChain.

The changes properly handle context lifecycle with timeout and cancellation.


50-53: LGTM! Good context management in TestGetTxs.

The changes properly handle context lifecycle with timeout and cancellation.


73-76: LGTM! Good context management in TestExecuteTxs.

The changes properly handle context lifecycle with timeout and cancellation.

@gupadhyaya gupadhyaya self-requested a review February 21, 2025 07:17
@gupadhyaya gupadhyaya added this pull request to the merge queue Feb 21, 2025
Merged via the queue into main with commit bdae150 Feb 21, 2025
19 checks passed
@gupadhyaya gupadhyaya deleted the marko/33 branch February 21, 2025 07:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Use contexts with timeouts in tests
3 participants