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 execute_command in SSH context #475

Merged
merged 58 commits into from
Jul 27, 2024
Merged

Conversation

thangckt
Copy link
Contributor

@thangckt thangckt commented Jul 27, 2024

solve issue #474

Summary by CodeRabbit

  • New Features

    • Introduced an optional parameter execute_command for executing a command immediately after establishing an SSH connection.
  • Documentation

    • Updated the documentation for the arginfo function to include details about the new execute_command parameter and its usage.

thangckt and others added 30 commits March 26, 2024 16:25
- add option: "strategy": {"customized_script_header_template_file": ""},

- add option: `sge_pe_name`
Copy link
Contributor

coderabbitai bot commented Jul 27, 2024

Walkthrough

Walkthrough

The recent changes introduce an optional execute_command parameter to the SSHContext class, allowing users to specify a command for execution immediately after establishing an SSH connection. This enhancement improves the usability and functionality of the class, making it easier for users to automate tasks during the connection process. Additionally, the documentation for the arginfo function has been updated to reflect this new parameter, ensuring clarity in its usage.

Changes

Files Change Summary
dpdispatcher/contexts/ssh_context.py Added execute_command parameter to __init__ method of SSHContext class and updated _setup_ssh method to execute it post-connection. Updated arginfo documentation for clarity.

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 723f0b9 and a9fbadf.

Files selected for processing (1)
  • dpdispatcher/contexts/ssh_context.py (5 hunks)
Additional context used
GitHub Check: codecov/patch
dpdispatcher/contexts/ssh_context.py

[warning] 242-243: dpdispatcher/contexts/ssh_context.py#L242-L243
Added lines #L242 - L243 were not covered by tests

Additional comments not posted (3)
dpdispatcher/contexts/ssh_context.py (3)

47-47: LGTM! Ensure documentation is updated.

The new parameter execute_command has been correctly added to the method signature and stored as an instance variable.


Line range hint 345-393:
LGTM!

The new argument descriptor for execute_command is correctly added to the arginfo method.


47-47: LGTM!

The execute_command parameter is correctly included in the remote_profile argument.


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

codecov bot commented Jul 27, 2024

Codecov Report

Attention: Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 56.12%. Comparing base (723f0b9) to head (a9fbadf).
Report is 18 commits behind head on master.

Files with missing lines Patch % Lines
dpdispatcher/contexts/ssh_context.py 75.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #475      +/-   ##
==========================================
- Coverage   59.92%   56.12%   -3.80%     
==========================================
  Files          39       40       +1     
  Lines        3845     3859      +14     
==========================================
- Hits         2304     2166     -138     
- Misses       1541     1693     +152     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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: 1

Comment on lines +242 to +243
if self.execute_command is not None:
self.exec_command(self.execute_command)
Copy link
Contributor

Choose a reason for hiding this comment

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

LGTM! Add tests for the new functionality.

The new logic to execute the command if execute_command is not None is correctly implemented.

Do you want me to generate the unit testing code or open a GitHub issue to track this task?

Tools
GitHub Check: codecov/patch

[warning] 242-243: dpdispatcher/contexts/ssh_context.py#L242-L243
Added lines #L242 - L243 were not covered by tests

@njzjz njzjz merged commit 1f1bacf into deepmodeling:master Jul 27, 2024
26 checks passed
@njzjz njzjz linked an issue Jul 27, 2024 that may be closed by this pull request
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.

How to execute ssh command in machine.json
2 participants