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

longer timeout to read wsh version (2FA prompts) #1776

Merged
merged 1 commit into from
Jan 20, 2025

Conversation

sawka
Copy link
Member

@sawka sawka commented Jan 20, 2025

No description provided.

Copy link
Contributor

coderabbitai bot commented Jan 20, 2025

Walkthrough

The pull request introduces modifications across multiple files in the remote connection and utility packages. The primary focus is on enhancing timeout handling mechanisms for reading version lines and improving context-based timeout management. A new utility function TimeoutFromContext is added to the utilfn package, which dynamically determines timeout durations based on context deadlines.

The changes affect connection-related methods in both SSH and WSL connection implementations, adjusting timeout durations for reading version lines. In the SSH connection controller, the timeout is now dynamically derived from the context, with a maximum of 30 seconds. The WSL connection implementation extends its version line reading timeout from 2 to 5 seconds. Additionally, a logging enhancement is introduced in the CpWshToRemote function to provide more visibility into context deadline information.

These modifications aim to improve timeout handling and provide more flexible connection management across different remote connection scenarios.

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

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 (1)
pkg/wslconn/wslconn.go (1)

289-289: Consider using TimeoutFromContext for consistency.

While increasing the timeout from 2s to 5s helps with 2FA prompts, consider using the new TimeoutFromContext function for consistent timeout handling across the codebase, similar to the implementation in conncontroller.go.

-	versionLine, err := utilfn.ReadLineWithTimeout(linesChan, 5*time.Second)
+	versionLine, err := utilfn.ReadLineWithTimeout(linesChan, utilfn.TimeoutFromContext(ctx, 5*time.Second))
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bcd0ec8 and a7d18f5.

📒 Files selected for processing (4)
  • pkg/remote/conncontroller/conncontroller.go (1 hunks)
  • pkg/remote/connutil.go (2 hunks)
  • pkg/util/utilfn/utilfn.go (2 hunks)
  • pkg/wslconn/wslconn.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Analyze (go)
  • GitHub Check: Build for TestDriver.ai
🔇 Additional comments (5)
pkg/remote/connutil.go (2)

18-18: LGTM!

The time package is required for the new timeout logging functionality.


99-102: LGTM! Enhanced logging for timeout debugging.

The added logging helps in debugging timeout-related issues during WSH binary transfer, particularly useful when 2FA prompts are involved.

pkg/util/utilfn/utilfn.go (2)

8-8: LGTM!

The context package is required for the new TimeoutFromContext function.


1017-1023: LGTM! Well-designed timeout utility function.

The TimeoutFromContext function provides a clean abstraction for handling context-based timeouts with a fallback to default timeout. This promotes consistent timeout handling across the codebase.

pkg/remote/conncontroller/conncontroller.go (1)

312-312: LGTM! Improved timeout handling for 2FA scenarios.

The change from a fixed 2s timeout to a dynamic context-based timeout with a 30s default is a good improvement that should better handle 2FA prompts. Using TimeoutFromContext allows for flexible timeout management based on the parent context.

Let's verify the impact of this timeout change on the codebase:

✅ Verification successful

Different timeouts are justified for WSL vs SSH connections

The different timeout values are intentional and correct:

  • WSL connections (wslconn.go) use shorter timeouts (5s/3s) as they are local connections
  • SSH connections (conncontroller.go) use longer timeouts (30s) to handle remote authentication including 2FA
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for other fixed timeouts in version line reading
echo "Checking for other fixed timeouts in version line reading..."
rg -A 2 "ReadLineWithTimeout.*time\." --glob '!pkg/remote/conncontroller/conncontroller.go'

Length of output: 789


Script:

#!/bin/bash
# Check for 2FA related code in wslconn.go
echo "Checking for 2FA related code in wslconn.go..."
rg -B 2 -A 2 "2[Ff][Aa]|[Tt]wo.?[Ff]actor" pkg/wslconn/wslconn.go

# Check for authentication related imports and functions
echo "Checking for auth related code in wslconn.go..."
ast-grep --pattern 'func $$$Auth$$$($$$) $$$'

Length of output: 323


Script:

#!/bin/bash
# Check how wslconn is used
echo "Checking wslconn usage..."
rg -B 2 -A 2 "wslconn" --type go --glob '!pkg/wslconn/**'

# Check the relationship between conncontroller and wslconn
echo "Checking imports..."
rg -l "wslconn|conncontroller" --type go | xargs rg "import \("

Length of output: 8207

@sawka sawka merged commit d81b6b8 into main Jan 20, 2025
8 of 9 checks passed
@sawka sawka deleted the sawka/fix-wshversion-timeout branch January 20, 2025 22:06
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.

1 participant