[feature] Add option to specify number of nodes - #565

Merged
jan-janssen merged 6 commits into
mainfrom
num_nodes
Feb 11, 2025
Merged

[feature] Add option to specify number of nodes#565
jan-janssen merged 6 commits into
mainfrom
num_nodes

Conversation

@jan-janssen

@jan-janssenjan-janssen commented Feb 10, 2025

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Enhanced job submission flexibility by introducing new options to specify the number of nodes and enable exclusive execution. These updates allow users to tailor job allocation and resource management more precisely for varying workload requirements.
    • Updated SLURM command generation to include new parameters for improved resource management.
  • Documentation

    • Updated documentation for executors to reflect the new parameters and their usage.

@coderabbitai

coderabbitaiBot commented Feb 10, 2025

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces two optional parameters, num_nodes and exclusive, into the job spawner classes. In the Flux implementation, the FluxPythonSpawner constructor now assigns these parameters to instance variables and utilizes them in the bootup method for job specification creation. Similarly, for SLURM, the SrunSpawner constructor and the generate_slurm_command function are enhanced to accept these parameters, enabling the dynamic construction of SLURM commands with new flags for node count and exclusivity.

Changes

File(s)Change Summary
executorlib/.../flux.pyAdded optional parameters num_nodes and exclusive to FluxPythonSpawner.__init__; created _num_nodes and _exclusive variables; updated bootup to use them.
executorlib/.../slurm.pyAdded optional parameters num_nodes and exclusive to SrunSpawner.__init__ and generate_slurm_command; updated command generation to include -N and --exact flags.
executorlib/.../interfaces/flux.pyRemoved openmpi_oversubscribe and slurm_cmd_args from resource_dict; added num_nodes and exclusive to FluxJobExecutor, FluxClusterExecutor, and create_flux_executor.
executorlib/.../interfaces/slurm.pyAdded num_nodes and exclusive parameters to SlurmJobExecutor and create_slurm_executor, enhancing resource management.
tests/.../test_pysqa_subprocess.pyUpdated generate_slurm_command to include new parameters; modified expected command list length and content to reflect changes.

Sequence Diagram(s)

sequenceDiagram
participant U as User
participant F as FluxPythonSpawner
participant J as JobspecV1
U->>F: Call bootup(command_lst)
F->>J: Create job spec using _num_nodes & _exclusive via from_command
F->>J: Create job spec using _num_nodes & _exclusive via from_nest_command
J-->>F: Return job specs
Loading
sequenceDiagram
participant U as User
participant S as SrunSpawner
participant G as generate_slurm_command
U->>S: Call generate_command()
S->>G: Invoke with _num_nodes & _exclusive
G-->>S: Return command list with flags (-N, --exact)
S-->>U: Return complete SLURM command
Loading

Possibly related PRs

  • [bug] SLURM: Fix CPUs per task #569: The changes in the main PR and the retrieved PR are related as both involve modifications to the generate_slurm_command function in executorlib/interactive/slurm.py, with the main PR adding new parameters while the retrieved PR fixes the formatting of an existing parameter.

Poem

I hop through the code with joyous flair,
New options added with a gentle air.
Nodes and flags in a rhythmic dance,
Commanding jobs with every chance.
With whiskers twitching, I celebrate the change—
A bunny’s delight in a code rearranged!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 68f1e4c and d599a76.

📒 Files selected for processing (5)
  • executorlib/interactive/flux.py (4 hunks)
  • executorlib/interactive/slurm.py (7 hunks)
  • executorlib/interfaces/flux.py (3 hunks)
  • executorlib/interfaces/slurm.py (3 hunks)
  • tests/test_pysqa_subprocess.py (1 hunks)
✨ 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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (3)
executorlib/interactive/slurm.py (2)

35-45: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.

93-105: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.
executorlib/interactive/flux.py (1)

24-37: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per base. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe. Defaults to False.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7de7f7 and 68f1e4c.

📒 Files selected for processing (2)
  • executorlib/interactive/flux.py (3 hunks)
  • executorlib/interactive/slurm.py (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.10)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
  • GitHub Check: unittest_win
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.13)
  • GitHub Check: unittest_openmpi (macos-latest, 3.13)
  • GitHub Check: unittest_old
  • GitHub Check: unittest_mpich (macos-latest, 3.13)
  • GitHub Check: unittest_flux_openmpi
  • GitHub Check: unittest_flux_mpich
  • GitHub Check: notebooks
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)
🔇 Additional comments (1)
executorlib/interactive/flux.py (1)

87-103: LGTM!

The implementation correctly passes the node count and exclusivity parameters to both job specification methods, maintaining consistency with the SLURM implementation.

Comment threadexecutorlib/interactive/slurm.py Outdated
if num_nodes is not None:
command_prepend_lst += ["-N", str(num_nodes)]
if threads_per_core > 1:
command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix missing = in --cpus-per-task flag.

The --cpus-per-task flag is missing the = separator, which will cause the command to fail.

- command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]+ command_prepend_lst += ["--cpus-per-task=" + str(threads_per_core)]
📝 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
command_prepend_lst+= ["--cpus-per-task"+str(threads_per_core)]
command_prepend_lst+= ["--cpus-per-task="+str(threads_per_core)]

@jan-janssen
jan-janssen marked this pull request as draft February 10, 2025 19:01
@codecov

codecovBot commented Feb 11, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.91%. Comparing base (ca707f9) to head (d599a76).
Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #565 +/- ##
==========================================
+ Coverage 95.89% 95.91% +0.02% 
==========================================
Files 26 26 Lines 1168 1176 +8 ==========================================
+ Hits 1120 1128 +8 
Misses 48 48 

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

@jan-janssenjan-janssen mentioned this pull request Feb 11, 2025
@jan-janssen

Copy link
Copy Markdown
MemberAuthor

Documentation is still missing.

Sign up for freeto 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

@jan-janssen
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

[feature] Add option to specify number of nodes - #565

Merged
jan-janssen merged 6 commits into
mainfrom
num_nodes
Feb 11, 2025
Merged

[feature] Add option to specify number of nodes#565
jan-janssen merged 6 commits into
mainfrom
num_nodes

Conversation

@jan-janssen

@jan-janssenjan-janssen commented Feb 10, 2025

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Enhanced job submission flexibility by introducing new options to specify the number of nodes and enable exclusive execution. These updates allow users to tailor job allocation and resource management more precisely for varying workload requirements.
    • Updated SLURM command generation to include new parameters for improved resource management.
  • Documentation

    • Updated documentation for executors to reflect the new parameters and their usage.

@coderabbitai

coderabbitaiBot commented Feb 10, 2025

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces two optional parameters, num_nodes and exclusive, into the job spawner classes. In the Flux implementation, the FluxPythonSpawner constructor now assigns these parameters to instance variables and utilizes them in the bootup method for job specification creation. Similarly, for SLURM, the SrunSpawner constructor and the generate_slurm_command function are enhanced to accept these parameters, enabling the dynamic construction of SLURM commands with new flags for node count and exclusivity.

Changes

File(s)Change Summary
executorlib/.../flux.pyAdded optional parameters num_nodes and exclusive to FluxPythonSpawner.__init__; created _num_nodes and _exclusive variables; updated bootup to use them.
executorlib/.../slurm.pyAdded optional parameters num_nodes and exclusive to SrunSpawner.__init__ and generate_slurm_command; updated command generation to include -N and --exact flags.
executorlib/.../interfaces/flux.pyRemoved openmpi_oversubscribe and slurm_cmd_args from resource_dict; added num_nodes and exclusive to FluxJobExecutor, FluxClusterExecutor, and create_flux_executor.
executorlib/.../interfaces/slurm.pyAdded num_nodes and exclusive parameters to SlurmJobExecutor and create_slurm_executor, enhancing resource management.
tests/.../test_pysqa_subprocess.pyUpdated generate_slurm_command to include new parameters; modified expected command list length and content to reflect changes.

Sequence Diagram(s)

sequenceDiagram
participant U as User
participant F as FluxPythonSpawner
participant J as JobspecV1
U->>F: Call bootup(command_lst)
F->>J: Create job spec using _num_nodes & _exclusive via from_command
F->>J: Create job spec using _num_nodes & _exclusive via from_nest_command
J-->>F: Return job specs
Loading
sequenceDiagram
participant U as User
participant S as SrunSpawner
participant G as generate_slurm_command
U->>S: Call generate_command()
S->>G: Invoke with _num_nodes & _exclusive
G-->>S: Return command list with flags (-N, --exact)
S-->>U: Return complete SLURM command
Loading

Possibly related PRs

  • [bug] SLURM: Fix CPUs per task #569: The changes in the main PR and the retrieved PR are related as both involve modifications to the generate_slurm_command function in executorlib/interactive/slurm.py, with the main PR adding new parameters while the retrieved PR fixes the formatting of an existing parameter.

Poem

I hop through the code with joyous flair,
New options added with a gentle air.
Nodes and flags in a rhythmic dance,
Commanding jobs with every chance.
With whiskers twitching, I celebrate the change—
A bunny’s delight in a code rearranged!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 68f1e4c and d599a76.

📒 Files selected for processing (5)
  • executorlib/interactive/flux.py (4 hunks)
  • executorlib/interactive/slurm.py (7 hunks)
  • executorlib/interfaces/flux.py (3 hunks)
  • executorlib/interfaces/slurm.py (3 hunks)
  • tests/test_pysqa_subprocess.py (1 hunks)
✨ 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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (3)
executorlib/interactive/slurm.py (2)

35-45: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.

93-105: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.
executorlib/interactive/flux.py (1)

24-37: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per base. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe. Defaults to False.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7de7f7 and 68f1e4c.

📒 Files selected for processing (2)
  • executorlib/interactive/flux.py (3 hunks)
  • executorlib/interactive/slurm.py (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.10)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
  • GitHub Check: unittest_win
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.13)
  • GitHub Check: unittest_openmpi (macos-latest, 3.13)
  • GitHub Check: unittest_old
  • GitHub Check: unittest_mpich (macos-latest, 3.13)
  • GitHub Check: unittest_flux_openmpi
  • GitHub Check: unittest_flux_mpich
  • GitHub Check: notebooks
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)
🔇 Additional comments (1)
executorlib/interactive/flux.py (1)

87-103: LGTM!

The implementation correctly passes the node count and exclusivity parameters to both job specification methods, maintaining consistency with the SLURM implementation.

Comment threadexecutorlib/interactive/slurm.py Outdated
if num_nodes is not None:
command_prepend_lst += ["-N", str(num_nodes)]
if threads_per_core > 1:
command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix missing = in --cpus-per-task flag.

The --cpus-per-task flag is missing the = separator, which will cause the command to fail.

- command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]+ command_prepend_lst += ["--cpus-per-task=" + str(threads_per_core)]
📝 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
command_prepend_lst+= ["--cpus-per-task"+str(threads_per_core)]
command_prepend_lst+= ["--cpus-per-task="+str(threads_per_core)]

@jan-janssen
jan-janssen marked this pull request as draft February 10, 2025 19:01
@codecov

codecovBot commented Feb 11, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.91%. Comparing base (ca707f9) to head (d599a76).
Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #565 +/- ##
==========================================
+ Coverage 95.89% 95.91% +0.02% 
==========================================
Files 26 26 Lines 1168 1176 +8 ==========================================
+ Hits 1120 1128 +8 
Misses 48 48 

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

@jan-janssenjan-janssen mentioned this pull request Feb 11, 2025
@jan-janssen

Copy link
Copy Markdown
MemberAuthor

Documentation is still missing.

Sign up for freeto 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

@jan-janssen
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[feature] Add option to specify number of nodes - #565

Merged
jan-janssen merged 6 commits into
mainfrom
num_nodes
Feb 11, 2025
Merged

[feature] Add option to specify number of nodes#565
jan-janssen merged 6 commits into
mainfrom
num_nodes

Conversation

@jan-janssen

@jan-janssenjan-janssen commented Feb 10, 2025

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Enhanced job submission flexibility by introducing new options to specify the number of nodes and enable exclusive execution. These updates allow users to tailor job allocation and resource management more precisely for varying workload requirements.
    • Updated SLURM command generation to include new parameters for improved resource management.
  • Documentation

    • Updated documentation for executors to reflect the new parameters and their usage.

@coderabbitai

coderabbitaiBot commented Feb 10, 2025

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces two optional parameters, num_nodes and exclusive, into the job spawner classes. In the Flux implementation, the FluxPythonSpawner constructor now assigns these parameters to instance variables and utilizes them in the bootup method for job specification creation. Similarly, for SLURM, the SrunSpawner constructor and the generate_slurm_command function are enhanced to accept these parameters, enabling the dynamic construction of SLURM commands with new flags for node count and exclusivity.

Changes

File(s)Change Summary
executorlib/.../flux.pyAdded optional parameters num_nodes and exclusive to FluxPythonSpawner.__init__; created _num_nodes and _exclusive variables; updated bootup to use them.
executorlib/.../slurm.pyAdded optional parameters num_nodes and exclusive to SrunSpawner.__init__ and generate_slurm_command; updated command generation to include -N and --exact flags.
executorlib/.../interfaces/flux.pyRemoved openmpi_oversubscribe and slurm_cmd_args from resource_dict; added num_nodes and exclusive to FluxJobExecutor, FluxClusterExecutor, and create_flux_executor.
executorlib/.../interfaces/slurm.pyAdded num_nodes and exclusive parameters to SlurmJobExecutor and create_slurm_executor, enhancing resource management.
tests/.../test_pysqa_subprocess.pyUpdated generate_slurm_command to include new parameters; modified expected command list length and content to reflect changes.

Sequence Diagram(s)

sequenceDiagram
participant U as User
participant F as FluxPythonSpawner
participant J as JobspecV1
U->>F: Call bootup(command_lst)
F->>J: Create job spec using _num_nodes & _exclusive via from_command
F->>J: Create job spec using _num_nodes & _exclusive via from_nest_command
J-->>F: Return job specs
Loading
sequenceDiagram
participant U as User
participant S as SrunSpawner
participant G as generate_slurm_command
U->>S: Call generate_command()
S->>G: Invoke with _num_nodes & _exclusive
G-->>S: Return command list with flags (-N, --exact)
S-->>U: Return complete SLURM command
Loading

Possibly related PRs

  • [bug] SLURM: Fix CPUs per task #569: The changes in the main PR and the retrieved PR are related as both involve modifications to the generate_slurm_command function in executorlib/interactive/slurm.py, with the main PR adding new parameters while the retrieved PR fixes the formatting of an existing parameter.

Poem

I hop through the code with joyous flair,
New options added with a gentle air.
Nodes and flags in a rhythmic dance,
Commanding jobs with every chance.
With whiskers twitching, I celebrate the change—
A bunny’s delight in a code rearranged!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 68f1e4c and d599a76.

📒 Files selected for processing (5)
  • executorlib/interactive/flux.py (4 hunks)
  • executorlib/interactive/slurm.py (7 hunks)
  • executorlib/interfaces/flux.py (3 hunks)
  • executorlib/interfaces/slurm.py (3 hunks)
  • tests/test_pysqa_subprocess.py (1 hunks)
✨ 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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (3)
executorlib/interactive/slurm.py (2)

35-45: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.

93-105: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.
executorlib/interactive/flux.py (1)

24-37: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per base. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe. Defaults to False.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7de7f7 and 68f1e4c.

📒 Files selected for processing (2)
  • executorlib/interactive/flux.py (3 hunks)
  • executorlib/interactive/slurm.py (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.10)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
  • GitHub Check: unittest_win
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.13)
  • GitHub Check: unittest_openmpi (macos-latest, 3.13)
  • GitHub Check: unittest_old
  • GitHub Check: unittest_mpich (macos-latest, 3.13)
  • GitHub Check: unittest_flux_openmpi
  • GitHub Check: unittest_flux_mpich
  • GitHub Check: notebooks
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)
🔇 Additional comments (1)
executorlib/interactive/flux.py (1)

87-103: LGTM!

The implementation correctly passes the node count and exclusivity parameters to both job specification methods, maintaining consistency with the SLURM implementation.

Comment threadexecutorlib/interactive/slurm.py Outdated
if num_nodes is not None:
command_prepend_lst += ["-N", str(num_nodes)]
if threads_per_core > 1:
command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix missing = in --cpus-per-task flag.

The --cpus-per-task flag is missing the = separator, which will cause the command to fail.

- command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]+ command_prepend_lst += ["--cpus-per-task=" + str(threads_per_core)]
📝 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
command_prepend_lst+= ["--cpus-per-task"+str(threads_per_core)]
command_prepend_lst+= ["--cpus-per-task="+str(threads_per_core)]

@jan-janssen
jan-janssen marked this pull request as draft February 10, 2025 19:01
@codecov

codecovBot commented Feb 11, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.91%. Comparing base (ca707f9) to head (d599a76).
Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #565 +/- ##
==========================================
+ Coverage 95.89% 95.91% +0.02% 
==========================================
Files 26 26 Lines 1168 1176 +8 ==========================================
+ Hits 1120 1128 +8 
Misses 48 48 

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

@jan-janssenjan-janssen mentioned this pull request Feb 11, 2025
@jan-janssen

Copy link
Copy Markdown
MemberAuthor

Documentation is still missing.

Sign up for freeto 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

@jan-janssen
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[feature] Add option to specify number of nodes - #565

Merged
jan-janssen merged 6 commits into
mainfrom
num_nodes
Feb 11, 2025
Merged

[feature] Add option to specify number of nodes#565
jan-janssen merged 6 commits into
mainfrom
num_nodes

Conversation

@jan-janssen

@jan-janssenjan-janssen commented Feb 10, 2025

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Enhanced job submission flexibility by introducing new options to specify the number of nodes and enable exclusive execution. These updates allow users to tailor job allocation and resource management more precisely for varying workload requirements.
    • Updated SLURM command generation to include new parameters for improved resource management.
  • Documentation

    • Updated documentation for executors to reflect the new parameters and their usage.

@coderabbitai

coderabbitaiBot commented Feb 10, 2025

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces two optional parameters, num_nodes and exclusive, into the job spawner classes. In the Flux implementation, the FluxPythonSpawner constructor now assigns these parameters to instance variables and utilizes them in the bootup method for job specification creation. Similarly, for SLURM, the SrunSpawner constructor and the generate_slurm_command function are enhanced to accept these parameters, enabling the dynamic construction of SLURM commands with new flags for node count and exclusivity.

Changes

File(s)Change Summary
executorlib/.../flux.pyAdded optional parameters num_nodes and exclusive to FluxPythonSpawner.__init__; created _num_nodes and _exclusive variables; updated bootup to use them.
executorlib/.../slurm.pyAdded optional parameters num_nodes and exclusive to SrunSpawner.__init__ and generate_slurm_command; updated command generation to include -N and --exact flags.
executorlib/.../interfaces/flux.pyRemoved openmpi_oversubscribe and slurm_cmd_args from resource_dict; added num_nodes and exclusive to FluxJobExecutor, FluxClusterExecutor, and create_flux_executor.
executorlib/.../interfaces/slurm.pyAdded num_nodes and exclusive parameters to SlurmJobExecutor and create_slurm_executor, enhancing resource management.
tests/.../test_pysqa_subprocess.pyUpdated generate_slurm_command to include new parameters; modified expected command list length and content to reflect changes.

Sequence Diagram(s)

sequenceDiagram
participant U as User
participant F as FluxPythonSpawner
participant J as JobspecV1
U->>F: Call bootup(command_lst)
F->>J: Create job spec using _num_nodes & _exclusive via from_command
F->>J: Create job spec using _num_nodes & _exclusive via from_nest_command
J-->>F: Return job specs
Loading
sequenceDiagram
participant U as User
participant S as SrunSpawner
participant G as generate_slurm_command
U->>S: Call generate_command()
S->>G: Invoke with _num_nodes & _exclusive
G-->>S: Return command list with flags (-N, --exact)
S-->>U: Return complete SLURM command
Loading

Possibly related PRs

  • [bug] SLURM: Fix CPUs per task #569: The changes in the main PR and the retrieved PR are related as both involve modifications to the generate_slurm_command function in executorlib/interactive/slurm.py, with the main PR adding new parameters while the retrieved PR fixes the formatting of an existing parameter.

Poem

I hop through the code with joyous flair,
New options added with a gentle air.
Nodes and flags in a rhythmic dance,
Commanding jobs with every chance.
With whiskers twitching, I celebrate the change—
A bunny’s delight in a code rearranged!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 68f1e4c and d599a76.

📒 Files selected for processing (5)
  • executorlib/interactive/flux.py (4 hunks)
  • executorlib/interactive/slurm.py (7 hunks)
  • executorlib/interfaces/flux.py (3 hunks)
  • executorlib/interfaces/slurm.py (3 hunks)
  • tests/test_pysqa_subprocess.py (1 hunks)
✨ 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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (3)
executorlib/interactive/slurm.py (2)

35-45: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.

93-105: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.
executorlib/interactive/flux.py (1)

24-37: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per base. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe. Defaults to False.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7de7f7 and 68f1e4c.

📒 Files selected for processing (2)
  • executorlib/interactive/flux.py (3 hunks)
  • executorlib/interactive/slurm.py (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.10)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
  • GitHub Check: unittest_win
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.13)
  • GitHub Check: unittest_openmpi (macos-latest, 3.13)
  • GitHub Check: unittest_old
  • GitHub Check: unittest_mpich (macos-latest, 3.13)
  • GitHub Check: unittest_flux_openmpi
  • GitHub Check: unittest_flux_mpich
  • GitHub Check: notebooks
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)
🔇 Additional comments (1)
executorlib/interactive/flux.py (1)

87-103: LGTM!

The implementation correctly passes the node count and exclusivity parameters to both job specification methods, maintaining consistency with the SLURM implementation.

Comment threadexecutorlib/interactive/slurm.py Outdated
if num_nodes is not None:
command_prepend_lst += ["-N", str(num_nodes)]
if threads_per_core > 1:
command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix missing = in --cpus-per-task flag.

The --cpus-per-task flag is missing the = separator, which will cause the command to fail.

- command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]+ command_prepend_lst += ["--cpus-per-task=" + str(threads_per_core)]
📝 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
command_prepend_lst+= ["--cpus-per-task"+str(threads_per_core)]
command_prepend_lst+= ["--cpus-per-task="+str(threads_per_core)]

@jan-janssen
jan-janssen marked this pull request as draft February 10, 2025 19:01
@codecov

codecovBot commented Feb 11, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.91%. Comparing base (ca707f9) to head (d599a76).
Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #565 +/- ##
==========================================
+ Coverage 95.89% 95.91% +0.02% 
==========================================
Files 26 26 Lines 1168 1176 +8 ==========================================
+ Hits 1120 1128 +8 
Misses 48 48 

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

@jan-janssenjan-janssen mentioned this pull request Feb 11, 2025
@jan-janssen

Copy link
Copy Markdown
MemberAuthor

Documentation is still missing.

Sign up for freeto 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

@jan-janssen
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

[feature] Add option to specify number of nodes - #565

Merged
jan-janssen merged 6 commits into
mainfrom
num_nodes
Feb 11, 2025
Merged

[feature] Add option to specify number of nodes#565
jan-janssen merged 6 commits into
mainfrom
num_nodes

Conversation

@jan-janssen

@jan-janssenjan-janssen commented Feb 10, 2025

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Enhanced job submission flexibility by introducing new options to specify the number of nodes and enable exclusive execution. These updates allow users to tailor job allocation and resource management more precisely for varying workload requirements.
    • Updated SLURM command generation to include new parameters for improved resource management.
  • Documentation

    • Updated documentation for executors to reflect the new parameters and their usage.

@coderabbitai

coderabbitaiBot commented Feb 10, 2025

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces two optional parameters, num_nodes and exclusive, into the job spawner classes. In the Flux implementation, the FluxPythonSpawner constructor now assigns these parameters to instance variables and utilizes them in the bootup method for job specification creation. Similarly, for SLURM, the SrunSpawner constructor and the generate_slurm_command function are enhanced to accept these parameters, enabling the dynamic construction of SLURM commands with new flags for node count and exclusivity.

Changes

File(s)Change Summary
executorlib/.../flux.pyAdded optional parameters num_nodes and exclusive to FluxPythonSpawner.__init__; created _num_nodes and _exclusive variables; updated bootup to use them.
executorlib/.../slurm.pyAdded optional parameters num_nodes and exclusive to SrunSpawner.__init__ and generate_slurm_command; updated command generation to include -N and --exact flags.
executorlib/.../interfaces/flux.pyRemoved openmpi_oversubscribe and slurm_cmd_args from resource_dict; added num_nodes and exclusive to FluxJobExecutor, FluxClusterExecutor, and create_flux_executor.
executorlib/.../interfaces/slurm.pyAdded num_nodes and exclusive parameters to SlurmJobExecutor and create_slurm_executor, enhancing resource management.
tests/.../test_pysqa_subprocess.pyUpdated generate_slurm_command to include new parameters; modified expected command list length and content to reflect changes.

Sequence Diagram(s)

sequenceDiagram
participant U as User
participant F as FluxPythonSpawner
participant J as JobspecV1
U->>F: Call bootup(command_lst)
F->>J: Create job spec using _num_nodes & _exclusive via from_command
F->>J: Create job spec using _num_nodes & _exclusive via from_nest_command
J-->>F: Return job specs
Loading
sequenceDiagram
participant U as User
participant S as SrunSpawner
participant G as generate_slurm_command
U->>S: Call generate_command()
S->>G: Invoke with _num_nodes & _exclusive
G-->>S: Return command list with flags (-N, --exact)
S-->>U: Return complete SLURM command
Loading

Possibly related PRs

  • [bug] SLURM: Fix CPUs per task #569: The changes in the main PR and the retrieved PR are related as both involve modifications to the generate_slurm_command function in executorlib/interactive/slurm.py, with the main PR adding new parameters while the retrieved PR fixes the formatting of an existing parameter.

Poem

I hop through the code with joyous flair,
New options added with a gentle air.
Nodes and flags in a rhythmic dance,
Commanding jobs with every chance.
With whiskers twitching, I celebrate the change—
A bunny’s delight in a code rearranged!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 68f1e4c and d599a76.

📒 Files selected for processing (5)
  • executorlib/interactive/flux.py (4 hunks)
  • executorlib/interactive/slurm.py (7 hunks)
  • executorlib/interfaces/flux.py (3 hunks)
  • executorlib/interfaces/slurm.py (3 hunks)
  • tests/test_pysqa_subprocess.py (1 hunks)
✨ 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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (3)
executorlib/interactive/slurm.py (2)

35-45: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.

93-105: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.
executorlib/interactive/flux.py (1)

24-37: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per base. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe. Defaults to False.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7de7f7 and 68f1e4c.

📒 Files selected for processing (2)
  • executorlib/interactive/flux.py (3 hunks)
  • executorlib/interactive/slurm.py (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.10)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
  • GitHub Check: unittest_win
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.13)
  • GitHub Check: unittest_openmpi (macos-latest, 3.13)
  • GitHub Check: unittest_old
  • GitHub Check: unittest_mpich (macos-latest, 3.13)
  • GitHub Check: unittest_flux_openmpi
  • GitHub Check: unittest_flux_mpich
  • GitHub Check: notebooks
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)
🔇 Additional comments (1)
executorlib/interactive/flux.py (1)

87-103: LGTM!

The implementation correctly passes the node count and exclusivity parameters to both job specification methods, maintaining consistency with the SLURM implementation.

Comment threadexecutorlib/interactive/slurm.py Outdated
if num_nodes is not None:
command_prepend_lst += ["-N", str(num_nodes)]
if threads_per_core > 1:
command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix missing = in --cpus-per-task flag.

The --cpus-per-task flag is missing the = separator, which will cause the command to fail.

- command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]+ command_prepend_lst += ["--cpus-per-task=" + str(threads_per_core)]
📝 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
command_prepend_lst+= ["--cpus-per-task"+str(threads_per_core)]
command_prepend_lst+= ["--cpus-per-task="+str(threads_per_core)]

@jan-janssen
jan-janssen marked this pull request as draft February 10, 2025 19:01
@codecov

codecovBot commented Feb 11, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.91%. Comparing base (ca707f9) to head (d599a76).
Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #565 +/- ##
==========================================
+ Coverage 95.89% 95.91% +0.02% 
==========================================
Files 26 26 Lines 1168 1176 +8 ==========================================
+ Hits 1120 1128 +8 
Misses 48 48 

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

@jan-janssenjan-janssen mentioned this pull request Feb 11, 2025
@jan-janssen

Copy link
Copy Markdown
MemberAuthor

Documentation is still missing.

Sign up for freeto 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

@jan-janssen
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[feature] Add option to specify number of nodes - #565

Merged
jan-janssen merged 6 commits into
mainfrom
num_nodes
Feb 11, 2025
Merged

[feature] Add option to specify number of nodes#565
jan-janssen merged 6 commits into
mainfrom
num_nodes

Conversation

@jan-janssen

@jan-janssenjan-janssen commented Feb 10, 2025

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Enhanced job submission flexibility by introducing new options to specify the number of nodes and enable exclusive execution. These updates allow users to tailor job allocation and resource management more precisely for varying workload requirements.
    • Updated SLURM command generation to include new parameters for improved resource management.
  • Documentation

    • Updated documentation for executors to reflect the new parameters and their usage.

@coderabbitai

coderabbitaiBot commented Feb 10, 2025

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces two optional parameters, num_nodes and exclusive, into the job spawner classes. In the Flux implementation, the FluxPythonSpawner constructor now assigns these parameters to instance variables and utilizes them in the bootup method for job specification creation. Similarly, for SLURM, the SrunSpawner constructor and the generate_slurm_command function are enhanced to accept these parameters, enabling the dynamic construction of SLURM commands with new flags for node count and exclusivity.

Changes

File(s)Change Summary
executorlib/.../flux.pyAdded optional parameters num_nodes and exclusive to FluxPythonSpawner.__init__; created _num_nodes and _exclusive variables; updated bootup to use them.
executorlib/.../slurm.pyAdded optional parameters num_nodes and exclusive to SrunSpawner.__init__ and generate_slurm_command; updated command generation to include -N and --exact flags.
executorlib/.../interfaces/flux.pyRemoved openmpi_oversubscribe and slurm_cmd_args from resource_dict; added num_nodes and exclusive to FluxJobExecutor, FluxClusterExecutor, and create_flux_executor.
executorlib/.../interfaces/slurm.pyAdded num_nodes and exclusive parameters to SlurmJobExecutor and create_slurm_executor, enhancing resource management.
tests/.../test_pysqa_subprocess.pyUpdated generate_slurm_command to include new parameters; modified expected command list length and content to reflect changes.

Sequence Diagram(s)

sequenceDiagram
participant U as User
participant F as FluxPythonSpawner
participant J as JobspecV1
U->>F: Call bootup(command_lst)
F->>J: Create job spec using _num_nodes & _exclusive via from_command
F->>J: Create job spec using _num_nodes & _exclusive via from_nest_command
J-->>F: Return job specs
Loading
sequenceDiagram
participant U as User
participant S as SrunSpawner
participant G as generate_slurm_command
U->>S: Call generate_command()
S->>G: Invoke with _num_nodes & _exclusive
G-->>S: Return command list with flags (-N, --exact)
S-->>U: Return complete SLURM command
Loading

Possibly related PRs

  • [bug] SLURM: Fix CPUs per task #569: The changes in the main PR and the retrieved PR are related as both involve modifications to the generate_slurm_command function in executorlib/interactive/slurm.py, with the main PR adding new parameters while the retrieved PR fixes the formatting of an existing parameter.

Poem

I hop through the code with joyous flair,
New options added with a gentle air.
Nodes and flags in a rhythmic dance,
Commanding jobs with every chance.
With whiskers twitching, I celebrate the change—
A bunny’s delight in a code rearranged!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 68f1e4c and d599a76.

📒 Files selected for processing (5)
  • executorlib/interactive/flux.py (4 hunks)
  • executorlib/interactive/slurm.py (7 hunks)
  • executorlib/interfaces/flux.py (3 hunks)
  • executorlib/interfaces/slurm.py (3 hunks)
  • tests/test_pysqa_subprocess.py (1 hunks)
✨ 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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (3)
executorlib/interactive/slurm.py (2)

35-45: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.

93-105: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.
executorlib/interactive/flux.py (1)

24-37: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per base. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe. Defaults to False.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7de7f7 and 68f1e4c.

📒 Files selected for processing (2)
  • executorlib/interactive/flux.py (3 hunks)
  • executorlib/interactive/slurm.py (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.10)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
  • GitHub Check: unittest_win
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.13)
  • GitHub Check: unittest_openmpi (macos-latest, 3.13)
  • GitHub Check: unittest_old
  • GitHub Check: unittest_mpich (macos-latest, 3.13)
  • GitHub Check: unittest_flux_openmpi
  • GitHub Check: unittest_flux_mpich
  • GitHub Check: notebooks
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)
🔇 Additional comments (1)
executorlib/interactive/flux.py (1)

87-103: LGTM!

The implementation correctly passes the node count and exclusivity parameters to both job specification methods, maintaining consistency with the SLURM implementation.

Comment threadexecutorlib/interactive/slurm.py Outdated
if num_nodes is not None:
command_prepend_lst += ["-N", str(num_nodes)]
if threads_per_core > 1:
command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix missing = in --cpus-per-task flag.

The --cpus-per-task flag is missing the = separator, which will cause the command to fail.

- command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]+ command_prepend_lst += ["--cpus-per-task=" + str(threads_per_core)]
📝 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
command_prepend_lst+= ["--cpus-per-task"+str(threads_per_core)]
command_prepend_lst+= ["--cpus-per-task="+str(threads_per_core)]

@jan-janssen
jan-janssen marked this pull request as draft February 10, 2025 19:01
@codecov

codecovBot commented Feb 11, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.91%. Comparing base (ca707f9) to head (d599a76).
Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #565 +/- ##
==========================================
+ Coverage 95.89% 95.91% +0.02% 
==========================================
Files 26 26 Lines 1168 1176 +8 ==========================================
+ Hits 1120 1128 +8 
Misses 48 48 

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

@jan-janssenjan-janssen mentioned this pull request Feb 11, 2025
@jan-janssen

Copy link
Copy Markdown
MemberAuthor

Documentation is still missing.

Sign up for freeto 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

@jan-janssen
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[feature] Add option to specify number of nodes - #565

Merged
jan-janssen merged 6 commits into
mainfrom
num_nodes
Feb 11, 2025
Merged

[feature] Add option to specify number of nodes#565
jan-janssen merged 6 commits into
mainfrom
num_nodes

Conversation

@jan-janssen

@jan-janssenjan-janssen commented Feb 10, 2025

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Enhanced job submission flexibility by introducing new options to specify the number of nodes and enable exclusive execution. These updates allow users to tailor job allocation and resource management more precisely for varying workload requirements.
    • Updated SLURM command generation to include new parameters for improved resource management.
  • Documentation

    • Updated documentation for executors to reflect the new parameters and their usage.

@coderabbitai

coderabbitaiBot commented Feb 10, 2025

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces two optional parameters, num_nodes and exclusive, into the job spawner classes. In the Flux implementation, the FluxPythonSpawner constructor now assigns these parameters to instance variables and utilizes them in the bootup method for job specification creation. Similarly, for SLURM, the SrunSpawner constructor and the generate_slurm_command function are enhanced to accept these parameters, enabling the dynamic construction of SLURM commands with new flags for node count and exclusivity.

Changes

File(s)Change Summary
executorlib/.../flux.pyAdded optional parameters num_nodes and exclusive to FluxPythonSpawner.__init__; created _num_nodes and _exclusive variables; updated bootup to use them.
executorlib/.../slurm.pyAdded optional parameters num_nodes and exclusive to SrunSpawner.__init__ and generate_slurm_command; updated command generation to include -N and --exact flags.
executorlib/.../interfaces/flux.pyRemoved openmpi_oversubscribe and slurm_cmd_args from resource_dict; added num_nodes and exclusive to FluxJobExecutor, FluxClusterExecutor, and create_flux_executor.
executorlib/.../interfaces/slurm.pyAdded num_nodes and exclusive parameters to SlurmJobExecutor and create_slurm_executor, enhancing resource management.
tests/.../test_pysqa_subprocess.pyUpdated generate_slurm_command to include new parameters; modified expected command list length and content to reflect changes.

Sequence Diagram(s)

sequenceDiagram
participant U as User
participant F as FluxPythonSpawner
participant J as JobspecV1
U->>F: Call bootup(command_lst)
F->>J: Create job spec using _num_nodes & _exclusive via from_command
F->>J: Create job spec using _num_nodes & _exclusive via from_nest_command
J-->>F: Return job specs
Loading
sequenceDiagram
participant U as User
participant S as SrunSpawner
participant G as generate_slurm_command
U->>S: Call generate_command()
S->>G: Invoke with _num_nodes & _exclusive
G-->>S: Return command list with flags (-N, --exact)
S-->>U: Return complete SLURM command
Loading

Possibly related PRs

  • [bug] SLURM: Fix CPUs per task #569: The changes in the main PR and the retrieved PR are related as both involve modifications to the generate_slurm_command function in executorlib/interactive/slurm.py, with the main PR adding new parameters while the retrieved PR fixes the formatting of an existing parameter.

Poem

I hop through the code with joyous flair,
New options added with a gentle air.
Nodes and flags in a rhythmic dance,
Commanding jobs with every chance.
With whiskers twitching, I celebrate the change—
A bunny’s delight in a code rearranged!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 68f1e4c and d599a76.

📒 Files selected for processing (5)
  • executorlib/interactive/flux.py (4 hunks)
  • executorlib/interactive/slurm.py (7 hunks)
  • executorlib/interfaces/flux.py (3 hunks)
  • executorlib/interfaces/slurm.py (3 hunks)
  • tests/test_pysqa_subprocess.py (1 hunks)
✨ 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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (3)
executorlib/interactive/slurm.py (2)

35-45: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.

93-105: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.
executorlib/interactive/flux.py (1)

24-37: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per base. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe. Defaults to False.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7de7f7 and 68f1e4c.

📒 Files selected for processing (2)
  • executorlib/interactive/flux.py (3 hunks)
  • executorlib/interactive/slurm.py (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.10)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
  • GitHub Check: unittest_win
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.13)
  • GitHub Check: unittest_openmpi (macos-latest, 3.13)
  • GitHub Check: unittest_old
  • GitHub Check: unittest_mpich (macos-latest, 3.13)
  • GitHub Check: unittest_flux_openmpi
  • GitHub Check: unittest_flux_mpich
  • GitHub Check: notebooks
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)
🔇 Additional comments (1)
executorlib/interactive/flux.py (1)

87-103: LGTM!

The implementation correctly passes the node count and exclusivity parameters to both job specification methods, maintaining consistency with the SLURM implementation.

Comment threadexecutorlib/interactive/slurm.py Outdated
if num_nodes is not None:
command_prepend_lst += ["-N", str(num_nodes)]
if threads_per_core > 1:
command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix missing = in --cpus-per-task flag.

The --cpus-per-task flag is missing the = separator, which will cause the command to fail.

- command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]+ command_prepend_lst += ["--cpus-per-task=" + str(threads_per_core)]
📝 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
command_prepend_lst+= ["--cpus-per-task"+str(threads_per_core)]
command_prepend_lst+= ["--cpus-per-task="+str(threads_per_core)]

@jan-janssen
jan-janssen marked this pull request as draft February 10, 2025 19:01
@codecov

codecovBot commented Feb 11, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.91%. Comparing base (ca707f9) to head (d599a76).
Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #565 +/- ##
==========================================
+ Coverage 95.89% 95.91% +0.02% 
==========================================
Files 26 26 Lines 1168 1176 +8 ==========================================
+ Hits 1120 1128 +8 
Misses 48 48 

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

@jan-janssenjan-janssen mentioned this pull request Feb 11, 2025
@jan-janssen

Copy link
Copy Markdown
MemberAuthor

Documentation is still missing.

Sign up for freeto 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

@jan-janssen
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

[feature] Add option to specify number of nodes - #565

Merged
jan-janssen merged 6 commits into
mainfrom
num_nodes
Feb 11, 2025
Merged

[feature] Add option to specify number of nodes#565
jan-janssen merged 6 commits into
mainfrom
num_nodes

Conversation

@jan-janssen

@jan-janssenjan-janssen commented Feb 10, 2025

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Enhanced job submission flexibility by introducing new options to specify the number of nodes and enable exclusive execution. These updates allow users to tailor job allocation and resource management more precisely for varying workload requirements.
    • Updated SLURM command generation to include new parameters for improved resource management.
  • Documentation

    • Updated documentation for executors to reflect the new parameters and their usage.

@coderabbitai

coderabbitaiBot commented Feb 10, 2025

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces two optional parameters, num_nodes and exclusive, into the job spawner classes. In the Flux implementation, the FluxPythonSpawner constructor now assigns these parameters to instance variables and utilizes them in the bootup method for job specification creation. Similarly, for SLURM, the SrunSpawner constructor and the generate_slurm_command function are enhanced to accept these parameters, enabling the dynamic construction of SLURM commands with new flags for node count and exclusivity.

Changes

File(s)Change Summary
executorlib/.../flux.pyAdded optional parameters num_nodes and exclusive to FluxPythonSpawner.__init__; created _num_nodes and _exclusive variables; updated bootup to use them.
executorlib/.../slurm.pyAdded optional parameters num_nodes and exclusive to SrunSpawner.__init__ and generate_slurm_command; updated command generation to include -N and --exact flags.
executorlib/.../interfaces/flux.pyRemoved openmpi_oversubscribe and slurm_cmd_args from resource_dict; added num_nodes and exclusive to FluxJobExecutor, FluxClusterExecutor, and create_flux_executor.
executorlib/.../interfaces/slurm.pyAdded num_nodes and exclusive parameters to SlurmJobExecutor and create_slurm_executor, enhancing resource management.
tests/.../test_pysqa_subprocess.pyUpdated generate_slurm_command to include new parameters; modified expected command list length and content to reflect changes.

Sequence Diagram(s)

sequenceDiagram
participant U as User
participant F as FluxPythonSpawner
participant J as JobspecV1
U->>F: Call bootup(command_lst)
F->>J: Create job spec using _num_nodes & _exclusive via from_command
F->>J: Create job spec using _num_nodes & _exclusive via from_nest_command
J-->>F: Return job specs
Loading
sequenceDiagram
participant U as User
participant S as SrunSpawner
participant G as generate_slurm_command
U->>S: Call generate_command()
S->>G: Invoke with _num_nodes & _exclusive
G-->>S: Return command list with flags (-N, --exact)
S-->>U: Return complete SLURM command
Loading

Possibly related PRs

  • [bug] SLURM: Fix CPUs per task #569: The changes in the main PR and the retrieved PR are related as both involve modifications to the generate_slurm_command function in executorlib/interactive/slurm.py, with the main PR adding new parameters while the retrieved PR fixes the formatting of an existing parameter.

Poem

I hop through the code with joyous flair,
New options added with a gentle air.
Nodes and flags in a rhythmic dance,
Commanding jobs with every chance.
With whiskers twitching, I celebrate the change—
A bunny’s delight in a code rearranged!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 68f1e4c and d599a76.

📒 Files selected for processing (5)
  • executorlib/interactive/flux.py (4 hunks)
  • executorlib/interactive/slurm.py (7 hunks)
  • executorlib/interfaces/flux.py (3 hunks)
  • executorlib/interfaces/slurm.py (3 hunks)
  • tests/test_pysqa_subprocess.py (1 hunks)
✨ 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.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (3)
executorlib/interactive/slurm.py (2)

35-45: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.

93-105: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per core. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe the cores. Defaults to False.
executorlib/interactive/flux.py (1)

24-37: Update docstring to include new parameters.

The docstring is missing documentation for the new parameters num_nodes and exclusive.

Add the following lines to the docstring:

 gpus_per_core (int, optional): The number of GPUs per base. Defaults to 0.
+ num_nodes (int, optional): The number of nodes to allocate. Defaults to None.+ exclusive (bool, optional): Whether to request exclusive node access. Defaults to False.
openmpi_oversubscribe (bool, optional): Whether to oversubscribe. Defaults to False.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7de7f7 and 68f1e4c.

📒 Files selected for processing (2)
  • executorlib/interactive/flux.py (3 hunks)
  • executorlib/interactive/slurm.py (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.10)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
  • GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
  • GitHub Check: unittest_win
  • GitHub Check: unittest_mpich (ubuntu-latest, 3.13)
  • GitHub Check: unittest_openmpi (macos-latest, 3.13)
  • GitHub Check: unittest_old
  • GitHub Check: unittest_mpich (macos-latest, 3.13)
  • GitHub Check: unittest_flux_openmpi
  • GitHub Check: unittest_flux_mpich
  • GitHub Check: notebooks
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
  • GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)
🔇 Additional comments (1)
executorlib/interactive/flux.py (1)

87-103: LGTM!

The implementation correctly passes the node count and exclusivity parameters to both job specification methods, maintaining consistency with the SLURM implementation.

Comment threadexecutorlib/interactive/slurm.py Outdated
if num_nodes is not None:
command_prepend_lst += ["-N", str(num_nodes)]
if threads_per_core > 1:
command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix missing = in --cpus-per-task flag.

The --cpus-per-task flag is missing the = separator, which will cause the command to fail.

- command_prepend_lst += ["--cpus-per-task" + str(threads_per_core)]+ command_prepend_lst += ["--cpus-per-task=" + str(threads_per_core)]
📝 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
command_prepend_lst+= ["--cpus-per-task"+str(threads_per_core)]
command_prepend_lst+= ["--cpus-per-task="+str(threads_per_core)]

@jan-janssen
jan-janssen marked this pull request as draft February 10, 2025 19:01
@codecov

codecovBot commented Feb 11, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.91%. Comparing base (ca707f9) to head (d599a76).
Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #565 +/- ##
==========================================
+ Coverage 95.89% 95.91% +0.02% 
==========================================
Files 26 26 Lines 1168 1176 +8 ==========================================
+ Hits 1120 1128 +8 
Misses 48 48 

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

@jan-janssenjan-janssen mentioned this pull request Feb 11, 2025
@jan-janssen

Copy link
Copy Markdown
MemberAuthor

Documentation is still missing.

Sign up for freeto 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

@jan-janssen