Executor Keyword Arguments - #351

Merged
jan-janssen merged 7 commits into
mainfrom
executor_kwargs
May 30, 2024
Merged

Executor Keyword Arguments#351
jan-janssen merged 7 commits into
mainfrom
executor_kwargs

Conversation

@jan-janssen

@jan-janssenjan-janssen commented May 30, 2024

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Introduced executor_kwargs parameter to simplify and enhance the flexibility of executor initialization across various backends (Flux, Local, Slurm).
  • Refactor

    • Consolidated multiple individual arguments into a single executor_kwargs dictionary for executor classes to streamline configurations.
    • Updated test cases to use executor_kwargs for passing parameters.
  • Bug Fixes

    • Ensured default values for cores and max_cores parameters in task execution functions to improve reliability.
  • Chores

    • Cleaned up imports and removed unnecessary dependencies in the codebase.

@coderabbitai

coderabbitaiBot commented May 30, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The recent changes primarily focus on refactoring the pympipool library to streamline the initialization of various executor classes. By introducing an executor_kwargs dictionary parameter, the updates simplify the passing of multiple arguments. This refactor affects classes in the flux, local, and slurm modules, as well as their corresponding test files, ensuring a more flexible and maintainable codebase.

Changes

FilesChange Summary
pympipool/scheduler/__init__.pyUpdated create_executor function to include executor parameter for submitting workers to Flux.
pympipool/scheduler/flux.pyRefactored PyFluxExecutor and PyFluxStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/local.pyRefactored PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/slurm.pyRefactored PySlurmExecutor and PySlurmStepExecutor to use executor_kwargs dictionary for initialization.
tests/test_flux_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyFluxExecutor.
tests/test_local_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyLocalExecutor and PyLocalStepExecutor.
pympipool/shared/executorbase.pyAdded MpiExecInterface to imports and set default values for cores and interface_class parameters in task execution functions.

Poem

In the realm of code so bright,
Executors now take flight,
With kwargs they align,
Simplifying every line.
From Flux to Local, changes bloom,
Bringing flexibility to every room.
🎩🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5c441d4 and a8c24a3.

Files selected for processing (7)
  • pympipool/scheduler/init.py (3 hunks)
  • pympipool/scheduler/flux.py (5 hunks)
  • pympipool/scheduler/local.py (6 hunks)
  • pympipool/scheduler/slurm.py (6 hunks)
  • tests/test_flux_executor.py (4 hunks)
  • tests/test_local_executor.py (18 hunks)
  • tests/test_local_executor_future.py (4 hunks)
Additional comments not posted (8)
tests/test_flux_executor.py (4)

52-55: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


65-66: The refactoring of the test case to use executor_kwargs for threading configuration is consistent with the changes in the executor classes.


77-78: The refactoring of the test case to use executor_kwargs for parallel execution settings is consistent with the changes in the executor classes.


86-87: The refactoring of the test case to use executor_kwargs for single task execution is consistent with the changes in the executor classes.

tests/test_local_executor_future.py (3)

21-22: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


36-37: The refactoring of the test case to use executor_kwargs for multi-core configuration is consistent with the changes in the executor classes.


67-69: The refactoring of the test case to use executor_kwargs for ensuring independence from the executor is consistent with the changes in the executor classes.

Also applies to: 106-108

tests/test_local_executor.py (1)

102-104: Ensure consistency in the use of executor_kwargs across all test cases.

The changes to the test cases correctly reflect the updated constructors of PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs. This aligns with the PR's objective to simplify parameter passing and enhance flexibility.

Also applies to: 114-116, 129-133, 138-142, 152-153, 162-163, 181-182, 195-196, 205-206, 224-225, 236-240, 277-278, 291-292, 302-305, 318-319, 327-328, 335-336, 355-356, 376-377, 390-391, 407-408

cwd: Optional[str] = None,
hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},
):

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

oversubscribe: bool = False,
cwd: Optional[str] = None,
hostname_localhost: bool = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
):
def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):
super().__init__()

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
def__init__(self, max_workers: int=1, executor_kwargs: dict={}):
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None,
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

backend=backend, flux_installed=flux_installed, slurm_installed=slurm_installed
)
check_pmi(backend=backend, pmi=pmi)
executor_kwargs = {

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- executor_kwargs = {+ executor_kwargs = executor_kwargs or {}

Committable suggestion was skipped due low confidence.

@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: 2

Outside diff range and nitpick comments (1)
pympipool/shared/executorbase.py (1)

17-17: Ensure consistent import order and grouping.

Consider grouping all imports from pympipool.shared.interface together for better readability and maintainability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a8c24a3 and 2138ea3.

Files selected for processing (2)
  • pympipool/shared/executorbase.py (5 hunks)
  • tests/test_local_executor.py (19 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tests/test_local_executor.py

future_queue: queue.Queue,
cores: int,
interface_class: BaseInterface,
cores: int = 1,

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.

Standardize default parameter values across similar functions.

It's good practice to ensure consistency in default parameter values across similar functions to avoid confusion and potential bugs. For instance, cores and interface_class have default values in execute_parallel_tasks and execute_separate_tasks, but not in _submit_function_to_separate_process. Consider adding default values for these parameters in _submit_function_to_separate_process as well.

Also applies to: 259-259, 312-312, 313-313, 553-553

Comment on lines +334 to +335
if "cores" not in kwargs.keys():
kwargs["cores"] = 1

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.

Handle default parameter values more robustly.

Instead of checking if cores is not in kwargs and then setting it to 1, you could use kwargs.get('cores', 1) which is a more Pythonic and concise way to handle default values.

- if "cores" not in kwargs.keys():- kwargs["cores"] = 1+ kwargs.setdefault('cores', 1)

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.

Suggested change
if"cores"notinkwargs.keys():
kwargs["cores"] =1
kwargs.setdefault('cores', 1)

@jan-janssen
jan-janssen merged commit b113227 into mainMay 30, 2024
@jan-janssen
jan-janssen deleted the executor_kwargs branch May 30, 2024 13:35
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 \u003cpre\u003e\u003ccode\u003e 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

Executor Keyword Arguments - #351

Merged
jan-janssen merged 7 commits into
mainfrom
executor_kwargs
May 30, 2024
Merged

Executor Keyword Arguments#351
jan-janssen merged 7 commits into
mainfrom
executor_kwargs

Conversation

@jan-janssen

@jan-janssenjan-janssen commented May 30, 2024

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Introduced executor_kwargs parameter to simplify and enhance the flexibility of executor initialization across various backends (Flux, Local, Slurm).
  • Refactor

    • Consolidated multiple individual arguments into a single executor_kwargs dictionary for executor classes to streamline configurations.
    • Updated test cases to use executor_kwargs for passing parameters.
  • Bug Fixes

    • Ensured default values for cores and max_cores parameters in task execution functions to improve reliability.
  • Chores

    • Cleaned up imports and removed unnecessary dependencies in the codebase.

@coderabbitai

coderabbitaiBot commented May 30, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The recent changes primarily focus on refactoring the pympipool library to streamline the initialization of various executor classes. By introducing an executor_kwargs dictionary parameter, the updates simplify the passing of multiple arguments. This refactor affects classes in the flux, local, and slurm modules, as well as their corresponding test files, ensuring a more flexible and maintainable codebase.

Changes

FilesChange Summary
pympipool/scheduler/__init__.pyUpdated create_executor function to include executor parameter for submitting workers to Flux.
pympipool/scheduler/flux.pyRefactored PyFluxExecutor and PyFluxStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/local.pyRefactored PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/slurm.pyRefactored PySlurmExecutor and PySlurmStepExecutor to use executor_kwargs dictionary for initialization.
tests/test_flux_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyFluxExecutor.
tests/test_local_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyLocalExecutor and PyLocalStepExecutor.
pympipool/shared/executorbase.pyAdded MpiExecInterface to imports and set default values for cores and interface_class parameters in task execution functions.

Poem

In the realm of code so bright,
Executors now take flight,
With kwargs they align,
Simplifying every line.
From Flux to Local, changes bloom,
Bringing flexibility to every room.
🎩🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5c441d4 and a8c24a3.

Files selected for processing (7)
  • pympipool/scheduler/init.py (3 hunks)
  • pympipool/scheduler/flux.py (5 hunks)
  • pympipool/scheduler/local.py (6 hunks)
  • pympipool/scheduler/slurm.py (6 hunks)
  • tests/test_flux_executor.py (4 hunks)
  • tests/test_local_executor.py (18 hunks)
  • tests/test_local_executor_future.py (4 hunks)
Additional comments not posted (8)
tests/test_flux_executor.py (4)

52-55: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


65-66: The refactoring of the test case to use executor_kwargs for threading configuration is consistent with the changes in the executor classes.


77-78: The refactoring of the test case to use executor_kwargs for parallel execution settings is consistent with the changes in the executor classes.


86-87: The refactoring of the test case to use executor_kwargs for single task execution is consistent with the changes in the executor classes.

tests/test_local_executor_future.py (3)

21-22: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


36-37: The refactoring of the test case to use executor_kwargs for multi-core configuration is consistent with the changes in the executor classes.


67-69: The refactoring of the test case to use executor_kwargs for ensuring independence from the executor is consistent with the changes in the executor classes.

Also applies to: 106-108

tests/test_local_executor.py (1)

102-104: Ensure consistency in the use of executor_kwargs across all test cases.

The changes to the test cases correctly reflect the updated constructors of PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs. This aligns with the PR's objective to simplify parameter passing and enhance flexibility.

Also applies to: 114-116, 129-133, 138-142, 152-153, 162-163, 181-182, 195-196, 205-206, 224-225, 236-240, 277-278, 291-292, 302-305, 318-319, 327-328, 335-336, 355-356, 376-377, 390-391, 407-408

cwd: Optional[str] = None,
hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},
):

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

oversubscribe: bool = False,
cwd: Optional[str] = None,
hostname_localhost: bool = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
):
def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):
super().__init__()

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
def__init__(self, max_workers: int=1, executor_kwargs: dict={}):
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None,
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

backend=backend, flux_installed=flux_installed, slurm_installed=slurm_installed
)
check_pmi(backend=backend, pmi=pmi)
executor_kwargs = {

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- executor_kwargs = {+ executor_kwargs = executor_kwargs or {}

Committable suggestion was skipped due low confidence.

@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: 2

Outside diff range and nitpick comments (1)
pympipool/shared/executorbase.py (1)

17-17: Ensure consistent import order and grouping.

Consider grouping all imports from pympipool.shared.interface together for better readability and maintainability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a8c24a3 and 2138ea3.

Files selected for processing (2)
  • pympipool/shared/executorbase.py (5 hunks)
  • tests/test_local_executor.py (19 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tests/test_local_executor.py

future_queue: queue.Queue,
cores: int,
interface_class: BaseInterface,
cores: int = 1,

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.

Standardize default parameter values across similar functions.

It's good practice to ensure consistency in default parameter values across similar functions to avoid confusion and potential bugs. For instance, cores and interface_class have default values in execute_parallel_tasks and execute_separate_tasks, but not in _submit_function_to_separate_process. Consider adding default values for these parameters in _submit_function_to_separate_process as well.

Also applies to: 259-259, 312-312, 313-313, 553-553

Comment on lines +334 to +335
if "cores" not in kwargs.keys():
kwargs["cores"] = 1

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.

Handle default parameter values more robustly.

Instead of checking if cores is not in kwargs and then setting it to 1, you could use kwargs.get('cores', 1) which is a more Pythonic and concise way to handle default values.

- if "cores" not in kwargs.keys():- kwargs["cores"] = 1+ kwargs.setdefault('cores', 1)

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.

Suggested change
if"cores"notinkwargs.keys():
kwargs["cores"] =1
kwargs.setdefault('cores', 1)

@jan-janssen
jan-janssen merged commit b113227 into mainMay 30, 2024
@jan-janssen
jan-janssen deleted the executor_kwargs branch May 30, 2024 13:35
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

Executor Keyword Arguments - #351

Merged
jan-janssen merged 7 commits into
mainfrom
executor_kwargs
May 30, 2024
Merged

Executor Keyword Arguments#351
jan-janssen merged 7 commits into
mainfrom
executor_kwargs

Conversation

@jan-janssen

@jan-janssenjan-janssen commented May 30, 2024

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Introduced executor_kwargs parameter to simplify and enhance the flexibility of executor initialization across various backends (Flux, Local, Slurm).
  • Refactor

    • Consolidated multiple individual arguments into a single executor_kwargs dictionary for executor classes to streamline configurations.
    • Updated test cases to use executor_kwargs for passing parameters.
  • Bug Fixes

    • Ensured default values for cores and max_cores parameters in task execution functions to improve reliability.
  • Chores

    • Cleaned up imports and removed unnecessary dependencies in the codebase.

@coderabbitai

coderabbitaiBot commented May 30, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The recent changes primarily focus on refactoring the pympipool library to streamline the initialization of various executor classes. By introducing an executor_kwargs dictionary parameter, the updates simplify the passing of multiple arguments. This refactor affects classes in the flux, local, and slurm modules, as well as their corresponding test files, ensuring a more flexible and maintainable codebase.

Changes

FilesChange Summary
pympipool/scheduler/__init__.pyUpdated create_executor function to include executor parameter for submitting workers to Flux.
pympipool/scheduler/flux.pyRefactored PyFluxExecutor and PyFluxStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/local.pyRefactored PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/slurm.pyRefactored PySlurmExecutor and PySlurmStepExecutor to use executor_kwargs dictionary for initialization.
tests/test_flux_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyFluxExecutor.
tests/test_local_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyLocalExecutor and PyLocalStepExecutor.
pympipool/shared/executorbase.pyAdded MpiExecInterface to imports and set default values for cores and interface_class parameters in task execution functions.

Poem

In the realm of code so bright,
Executors now take flight,
With kwargs they align,
Simplifying every line.
From Flux to Local, changes bloom,
Bringing flexibility to every room.
🎩🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5c441d4 and a8c24a3.

Files selected for processing (7)
  • pympipool/scheduler/init.py (3 hunks)
  • pympipool/scheduler/flux.py (5 hunks)
  • pympipool/scheduler/local.py (6 hunks)
  • pympipool/scheduler/slurm.py (6 hunks)
  • tests/test_flux_executor.py (4 hunks)
  • tests/test_local_executor.py (18 hunks)
  • tests/test_local_executor_future.py (4 hunks)
Additional comments not posted (8)
tests/test_flux_executor.py (4)

52-55: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


65-66: The refactoring of the test case to use executor_kwargs for threading configuration is consistent with the changes in the executor classes.


77-78: The refactoring of the test case to use executor_kwargs for parallel execution settings is consistent with the changes in the executor classes.


86-87: The refactoring of the test case to use executor_kwargs for single task execution is consistent with the changes in the executor classes.

tests/test_local_executor_future.py (3)

21-22: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


36-37: The refactoring of the test case to use executor_kwargs for multi-core configuration is consistent with the changes in the executor classes.


67-69: The refactoring of the test case to use executor_kwargs for ensuring independence from the executor is consistent with the changes in the executor classes.

Also applies to: 106-108

tests/test_local_executor.py (1)

102-104: Ensure consistency in the use of executor_kwargs across all test cases.

The changes to the test cases correctly reflect the updated constructors of PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs. This aligns with the PR's objective to simplify parameter passing and enhance flexibility.

Also applies to: 114-116, 129-133, 138-142, 152-153, 162-163, 181-182, 195-196, 205-206, 224-225, 236-240, 277-278, 291-292, 302-305, 318-319, 327-328, 335-336, 355-356, 376-377, 390-391, 407-408

cwd: Optional[str] = None,
hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},
):

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

oversubscribe: bool = False,
cwd: Optional[str] = None,
hostname_localhost: bool = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
):
def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):
super().__init__()

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
def__init__(self, max_workers: int=1, executor_kwargs: dict={}):
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None,
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

backend=backend, flux_installed=flux_installed, slurm_installed=slurm_installed
)
check_pmi(backend=backend, pmi=pmi)
executor_kwargs = {

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- executor_kwargs = {+ executor_kwargs = executor_kwargs or {}

Committable suggestion was skipped due low confidence.

@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: 2

Outside diff range and nitpick comments (1)
pympipool/shared/executorbase.py (1)

17-17: Ensure consistent import order and grouping.

Consider grouping all imports from pympipool.shared.interface together for better readability and maintainability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a8c24a3 and 2138ea3.

Files selected for processing (2)
  • pympipool/shared/executorbase.py (5 hunks)
  • tests/test_local_executor.py (19 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tests/test_local_executor.py

future_queue: queue.Queue,
cores: int,
interface_class: BaseInterface,
cores: int = 1,

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.

Standardize default parameter values across similar functions.

It's good practice to ensure consistency in default parameter values across similar functions to avoid confusion and potential bugs. For instance, cores and interface_class have default values in execute_parallel_tasks and execute_separate_tasks, but not in _submit_function_to_separate_process. Consider adding default values for these parameters in _submit_function_to_separate_process as well.

Also applies to: 259-259, 312-312, 313-313, 553-553

Comment on lines +334 to +335
if "cores" not in kwargs.keys():
kwargs["cores"] = 1

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.

Handle default parameter values more robustly.

Instead of checking if cores is not in kwargs and then setting it to 1, you could use kwargs.get('cores', 1) which is a more Pythonic and concise way to handle default values.

- if "cores" not in kwargs.keys():- kwargs["cores"] = 1+ kwargs.setdefault('cores', 1)

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.

Suggested change
if"cores"notinkwargs.keys():
kwargs["cores"] =1
kwargs.setdefault('cores', 1)

@jan-janssen
jan-janssen merged commit b113227 into mainMay 30, 2024
@jan-janssen
jan-janssen deleted the executor_kwargs branch May 30, 2024 13:35
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 \u003e 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

Executor Keyword Arguments - #351

Merged
jan-janssen merged 7 commits into
mainfrom
executor_kwargs
May 30, 2024
Merged

Executor Keyword Arguments#351
jan-janssen merged 7 commits into
mainfrom
executor_kwargs

Conversation

@jan-janssen

@jan-janssenjan-janssen commented May 30, 2024

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Introduced executor_kwargs parameter to simplify and enhance the flexibility of executor initialization across various backends (Flux, Local, Slurm).
  • Refactor

    • Consolidated multiple individual arguments into a single executor_kwargs dictionary for executor classes to streamline configurations.
    • Updated test cases to use executor_kwargs for passing parameters.
  • Bug Fixes

    • Ensured default values for cores and max_cores parameters in task execution functions to improve reliability.
  • Chores

    • Cleaned up imports and removed unnecessary dependencies in the codebase.

@coderabbitai

coderabbitaiBot commented May 30, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The recent changes primarily focus on refactoring the pympipool library to streamline the initialization of various executor classes. By introducing an executor_kwargs dictionary parameter, the updates simplify the passing of multiple arguments. This refactor affects classes in the flux, local, and slurm modules, as well as their corresponding test files, ensuring a more flexible and maintainable codebase.

Changes

FilesChange Summary
pympipool/scheduler/__init__.pyUpdated create_executor function to include executor parameter for submitting workers to Flux.
pympipool/scheduler/flux.pyRefactored PyFluxExecutor and PyFluxStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/local.pyRefactored PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/slurm.pyRefactored PySlurmExecutor and PySlurmStepExecutor to use executor_kwargs dictionary for initialization.
tests/test_flux_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyFluxExecutor.
tests/test_local_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyLocalExecutor and PyLocalStepExecutor.
pympipool/shared/executorbase.pyAdded MpiExecInterface to imports and set default values for cores and interface_class parameters in task execution functions.

Poem

In the realm of code so bright,
Executors now take flight,
With kwargs they align,
Simplifying every line.
From Flux to Local, changes bloom,
Bringing flexibility to every room.
🎩🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5c441d4 and a8c24a3.

Files selected for processing (7)
  • pympipool/scheduler/init.py (3 hunks)
  • pympipool/scheduler/flux.py (5 hunks)
  • pympipool/scheduler/local.py (6 hunks)
  • pympipool/scheduler/slurm.py (6 hunks)
  • tests/test_flux_executor.py (4 hunks)
  • tests/test_local_executor.py (18 hunks)
  • tests/test_local_executor_future.py (4 hunks)
Additional comments not posted (8)
tests/test_flux_executor.py (4)

52-55: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


65-66: The refactoring of the test case to use executor_kwargs for threading configuration is consistent with the changes in the executor classes.


77-78: The refactoring of the test case to use executor_kwargs for parallel execution settings is consistent with the changes in the executor classes.


86-87: The refactoring of the test case to use executor_kwargs for single task execution is consistent with the changes in the executor classes.

tests/test_local_executor_future.py (3)

21-22: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


36-37: The refactoring of the test case to use executor_kwargs for multi-core configuration is consistent with the changes in the executor classes.


67-69: The refactoring of the test case to use executor_kwargs for ensuring independence from the executor is consistent with the changes in the executor classes.

Also applies to: 106-108

tests/test_local_executor.py (1)

102-104: Ensure consistency in the use of executor_kwargs across all test cases.

The changes to the test cases correctly reflect the updated constructors of PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs. This aligns with the PR's objective to simplify parameter passing and enhance flexibility.

Also applies to: 114-116, 129-133, 138-142, 152-153, 162-163, 181-182, 195-196, 205-206, 224-225, 236-240, 277-278, 291-292, 302-305, 318-319, 327-328, 335-336, 355-356, 376-377, 390-391, 407-408

cwd: Optional[str] = None,
hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},
):

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

oversubscribe: bool = False,
cwd: Optional[str] = None,
hostname_localhost: bool = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
):
def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):
super().__init__()

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
def__init__(self, max_workers: int=1, executor_kwargs: dict={}):
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None,
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

backend=backend, flux_installed=flux_installed, slurm_installed=slurm_installed
)
check_pmi(backend=backend, pmi=pmi)
executor_kwargs = {

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- executor_kwargs = {+ executor_kwargs = executor_kwargs or {}

Committable suggestion was skipped due low confidence.

@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: 2

Outside diff range and nitpick comments (1)
pympipool/shared/executorbase.py (1)

17-17: Ensure consistent import order and grouping.

Consider grouping all imports from pympipool.shared.interface together for better readability and maintainability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a8c24a3 and 2138ea3.

Files selected for processing (2)
  • pympipool/shared/executorbase.py (5 hunks)
  • tests/test_local_executor.py (19 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tests/test_local_executor.py

future_queue: queue.Queue,
cores: int,
interface_class: BaseInterface,
cores: int = 1,

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.

Standardize default parameter values across similar functions.

It's good practice to ensure consistency in default parameter values across similar functions to avoid confusion and potential bugs. For instance, cores and interface_class have default values in execute_parallel_tasks and execute_separate_tasks, but not in _submit_function_to_separate_process. Consider adding default values for these parameters in _submit_function_to_separate_process as well.

Also applies to: 259-259, 312-312, 313-313, 553-553

Comment on lines +334 to +335
if "cores" not in kwargs.keys():
kwargs["cores"] = 1

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.

Handle default parameter values more robustly.

Instead of checking if cores is not in kwargs and then setting it to 1, you could use kwargs.get('cores', 1) which is a more Pythonic and concise way to handle default values.

- if "cores" not in kwargs.keys():- kwargs["cores"] = 1+ kwargs.setdefault('cores', 1)

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.

Suggested change
if"cores"notinkwargs.keys():
kwargs["cores"] =1
kwargs.setdefault('cores', 1)

@jan-janssen
jan-janssen merged commit b113227 into mainMay 30, 2024
@jan-janssen
jan-janssen deleted the executor_kwargs branch May 30, 2024 13:35
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

Executor Keyword Arguments - #351

Merged
jan-janssen merged 7 commits into
mainfrom
executor_kwargs
May 30, 2024
Merged

Executor Keyword Arguments#351
jan-janssen merged 7 commits into
mainfrom
executor_kwargs

Conversation

@jan-janssen

@jan-janssenjan-janssen commented May 30, 2024

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Introduced executor_kwargs parameter to simplify and enhance the flexibility of executor initialization across various backends (Flux, Local, Slurm).
  • Refactor

    • Consolidated multiple individual arguments into a single executor_kwargs dictionary for executor classes to streamline configurations.
    • Updated test cases to use executor_kwargs for passing parameters.
  • Bug Fixes

    • Ensured default values for cores and max_cores parameters in task execution functions to improve reliability.
  • Chores

    • Cleaned up imports and removed unnecessary dependencies in the codebase.

@coderabbitai

coderabbitaiBot commented May 30, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The recent changes primarily focus on refactoring the pympipool library to streamline the initialization of various executor classes. By introducing an executor_kwargs dictionary parameter, the updates simplify the passing of multiple arguments. This refactor affects classes in the flux, local, and slurm modules, as well as their corresponding test files, ensuring a more flexible and maintainable codebase.

Changes

FilesChange Summary
pympipool/scheduler/__init__.pyUpdated create_executor function to include executor parameter for submitting workers to Flux.
pympipool/scheduler/flux.pyRefactored PyFluxExecutor and PyFluxStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/local.pyRefactored PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/slurm.pyRefactored PySlurmExecutor and PySlurmStepExecutor to use executor_kwargs dictionary for initialization.
tests/test_flux_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyFluxExecutor.
tests/test_local_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyLocalExecutor and PyLocalStepExecutor.
pympipool/shared/executorbase.pyAdded MpiExecInterface to imports and set default values for cores and interface_class parameters in task execution functions.

Poem

In the realm of code so bright,
Executors now take flight,
With kwargs they align,
Simplifying every line.
From Flux to Local, changes bloom,
Bringing flexibility to every room.
🎩🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5c441d4 and a8c24a3.

Files selected for processing (7)
  • pympipool/scheduler/init.py (3 hunks)
  • pympipool/scheduler/flux.py (5 hunks)
  • pympipool/scheduler/local.py (6 hunks)
  • pympipool/scheduler/slurm.py (6 hunks)
  • tests/test_flux_executor.py (4 hunks)
  • tests/test_local_executor.py (18 hunks)
  • tests/test_local_executor_future.py (4 hunks)
Additional comments not posted (8)
tests/test_flux_executor.py (4)

52-55: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


65-66: The refactoring of the test case to use executor_kwargs for threading configuration is consistent with the changes in the executor classes.


77-78: The refactoring of the test case to use executor_kwargs for parallel execution settings is consistent with the changes in the executor classes.


86-87: The refactoring of the test case to use executor_kwargs for single task execution is consistent with the changes in the executor classes.

tests/test_local_executor_future.py (3)

21-22: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


36-37: The refactoring of the test case to use executor_kwargs for multi-core configuration is consistent with the changes in the executor classes.


67-69: The refactoring of the test case to use executor_kwargs for ensuring independence from the executor is consistent with the changes in the executor classes.

Also applies to: 106-108

tests/test_local_executor.py (1)

102-104: Ensure consistency in the use of executor_kwargs across all test cases.

The changes to the test cases correctly reflect the updated constructors of PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs. This aligns with the PR's objective to simplify parameter passing and enhance flexibility.

Also applies to: 114-116, 129-133, 138-142, 152-153, 162-163, 181-182, 195-196, 205-206, 224-225, 236-240, 277-278, 291-292, 302-305, 318-319, 327-328, 335-336, 355-356, 376-377, 390-391, 407-408

cwd: Optional[str] = None,
hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},
):

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

oversubscribe: bool = False,
cwd: Optional[str] = None,
hostname_localhost: bool = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
):
def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):
super().__init__()

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
def__init__(self, max_workers: int=1, executor_kwargs: dict={}):
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None,
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

backend=backend, flux_installed=flux_installed, slurm_installed=slurm_installed
)
check_pmi(backend=backend, pmi=pmi)
executor_kwargs = {

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- executor_kwargs = {+ executor_kwargs = executor_kwargs or {}

Committable suggestion was skipped due low confidence.

@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: 2

Outside diff range and nitpick comments (1)
pympipool/shared/executorbase.py (1)

17-17: Ensure consistent import order and grouping.

Consider grouping all imports from pympipool.shared.interface together for better readability and maintainability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a8c24a3 and 2138ea3.

Files selected for processing (2)
  • pympipool/shared/executorbase.py (5 hunks)
  • tests/test_local_executor.py (19 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tests/test_local_executor.py

future_queue: queue.Queue,
cores: int,
interface_class: BaseInterface,
cores: int = 1,

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.

Standardize default parameter values across similar functions.

It's good practice to ensure consistency in default parameter values across similar functions to avoid confusion and potential bugs. For instance, cores and interface_class have default values in execute_parallel_tasks and execute_separate_tasks, but not in _submit_function_to_separate_process. Consider adding default values for these parameters in _submit_function_to_separate_process as well.

Also applies to: 259-259, 312-312, 313-313, 553-553

Comment on lines +334 to +335
if "cores" not in kwargs.keys():
kwargs["cores"] = 1

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.

Handle default parameter values more robustly.

Instead of checking if cores is not in kwargs and then setting it to 1, you could use kwargs.get('cores', 1) which is a more Pythonic and concise way to handle default values.

- if "cores" not in kwargs.keys():- kwargs["cores"] = 1+ kwargs.setdefault('cores', 1)

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.

Suggested change
if"cores"notinkwargs.keys():
kwargs["cores"] =1
kwargs.setdefault('cores', 1)

@jan-janssen
jan-janssen merged commit b113227 into mainMay 30, 2024
@jan-janssen
jan-janssen deleted the executor_kwargs branch May 30, 2024 13:35
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

Executor Keyword Arguments - #351

Merged
jan-janssen merged 7 commits into
mainfrom
executor_kwargs
May 30, 2024
Merged

Executor Keyword Arguments#351
jan-janssen merged 7 commits into
mainfrom
executor_kwargs

Conversation

@jan-janssen

@jan-janssenjan-janssen commented May 30, 2024

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Introduced executor_kwargs parameter to simplify and enhance the flexibility of executor initialization across various backends (Flux, Local, Slurm).
  • Refactor

    • Consolidated multiple individual arguments into a single executor_kwargs dictionary for executor classes to streamline configurations.
    • Updated test cases to use executor_kwargs for passing parameters.
  • Bug Fixes

    • Ensured default values for cores and max_cores parameters in task execution functions to improve reliability.
  • Chores

    • Cleaned up imports and removed unnecessary dependencies in the codebase.

@coderabbitai

coderabbitaiBot commented May 30, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The recent changes primarily focus on refactoring the pympipool library to streamline the initialization of various executor classes. By introducing an executor_kwargs dictionary parameter, the updates simplify the passing of multiple arguments. This refactor affects classes in the flux, local, and slurm modules, as well as their corresponding test files, ensuring a more flexible and maintainable codebase.

Changes

FilesChange Summary
pympipool/scheduler/__init__.pyUpdated create_executor function to include executor parameter for submitting workers to Flux.
pympipool/scheduler/flux.pyRefactored PyFluxExecutor and PyFluxStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/local.pyRefactored PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/slurm.pyRefactored PySlurmExecutor and PySlurmStepExecutor to use executor_kwargs dictionary for initialization.
tests/test_flux_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyFluxExecutor.
tests/test_local_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyLocalExecutor and PyLocalStepExecutor.
pympipool/shared/executorbase.pyAdded MpiExecInterface to imports and set default values for cores and interface_class parameters in task execution functions.

Poem

In the realm of code so bright,
Executors now take flight,
With kwargs they align,
Simplifying every line.
From Flux to Local, changes bloom,
Bringing flexibility to every room.
🎩🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5c441d4 and a8c24a3.

Files selected for processing (7)
  • pympipool/scheduler/init.py (3 hunks)
  • pympipool/scheduler/flux.py (5 hunks)
  • pympipool/scheduler/local.py (6 hunks)
  • pympipool/scheduler/slurm.py (6 hunks)
  • tests/test_flux_executor.py (4 hunks)
  • tests/test_local_executor.py (18 hunks)
  • tests/test_local_executor_future.py (4 hunks)
Additional comments not posted (8)
tests/test_flux_executor.py (4)

52-55: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


65-66: The refactoring of the test case to use executor_kwargs for threading configuration is consistent with the changes in the executor classes.


77-78: The refactoring of the test case to use executor_kwargs for parallel execution settings is consistent with the changes in the executor classes.


86-87: The refactoring of the test case to use executor_kwargs for single task execution is consistent with the changes in the executor classes.

tests/test_local_executor_future.py (3)

21-22: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


36-37: The refactoring of the test case to use executor_kwargs for multi-core configuration is consistent with the changes in the executor classes.


67-69: The refactoring of the test case to use executor_kwargs for ensuring independence from the executor is consistent with the changes in the executor classes.

Also applies to: 106-108

tests/test_local_executor.py (1)

102-104: Ensure consistency in the use of executor_kwargs across all test cases.

The changes to the test cases correctly reflect the updated constructors of PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs. This aligns with the PR's objective to simplify parameter passing and enhance flexibility.

Also applies to: 114-116, 129-133, 138-142, 152-153, 162-163, 181-182, 195-196, 205-206, 224-225, 236-240, 277-278, 291-292, 302-305, 318-319, 327-328, 335-336, 355-356, 376-377, 390-391, 407-408

cwd: Optional[str] = None,
hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},
):

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

oversubscribe: bool = False,
cwd: Optional[str] = None,
hostname_localhost: bool = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
):
def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):
super().__init__()

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
def__init__(self, max_workers: int=1, executor_kwargs: dict={}):
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None,
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

backend=backend, flux_installed=flux_installed, slurm_installed=slurm_installed
)
check_pmi(backend=backend, pmi=pmi)
executor_kwargs = {

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- executor_kwargs = {+ executor_kwargs = executor_kwargs or {}

Committable suggestion was skipped due low confidence.

@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: 2

Outside diff range and nitpick comments (1)
pympipool/shared/executorbase.py (1)

17-17: Ensure consistent import order and grouping.

Consider grouping all imports from pympipool.shared.interface together for better readability and maintainability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a8c24a3 and 2138ea3.

Files selected for processing (2)
  • pympipool/shared/executorbase.py (5 hunks)
  • tests/test_local_executor.py (19 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tests/test_local_executor.py

future_queue: queue.Queue,
cores: int,
interface_class: BaseInterface,
cores: int = 1,

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.

Standardize default parameter values across similar functions.

It's good practice to ensure consistency in default parameter values across similar functions to avoid confusion and potential bugs. For instance, cores and interface_class have default values in execute_parallel_tasks and execute_separate_tasks, but not in _submit_function_to_separate_process. Consider adding default values for these parameters in _submit_function_to_separate_process as well.

Also applies to: 259-259, 312-312, 313-313, 553-553

Comment on lines +334 to +335
if "cores" not in kwargs.keys():
kwargs["cores"] = 1

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.

Handle default parameter values more robustly.

Instead of checking if cores is not in kwargs and then setting it to 1, you could use kwargs.get('cores', 1) which is a more Pythonic and concise way to handle default values.

- if "cores" not in kwargs.keys():- kwargs["cores"] = 1+ kwargs.setdefault('cores', 1)

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.

Suggested change
if"cores"notinkwargs.keys():
kwargs["cores"] =1
kwargs.setdefault('cores', 1)

@jan-janssen
jan-janssen merged commit b113227 into mainMay 30, 2024
@jan-janssen
jan-janssen deleted the executor_kwargs branch May 30, 2024 13:35
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

Executor Keyword Arguments - #351

Merged
jan-janssen merged 7 commits into
mainfrom
executor_kwargs
May 30, 2024
Merged

Executor Keyword Arguments#351
jan-janssen merged 7 commits into
mainfrom
executor_kwargs

Conversation

@jan-janssen

@jan-janssenjan-janssen commented May 30, 2024

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Introduced executor_kwargs parameter to simplify and enhance the flexibility of executor initialization across various backends (Flux, Local, Slurm).
  • Refactor

    • Consolidated multiple individual arguments into a single executor_kwargs dictionary for executor classes to streamline configurations.
    • Updated test cases to use executor_kwargs for passing parameters.
  • Bug Fixes

    • Ensured default values for cores and max_cores parameters in task execution functions to improve reliability.
  • Chores

    • Cleaned up imports and removed unnecessary dependencies in the codebase.

@coderabbitai

coderabbitaiBot commented May 30, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The recent changes primarily focus on refactoring the pympipool library to streamline the initialization of various executor classes. By introducing an executor_kwargs dictionary parameter, the updates simplify the passing of multiple arguments. This refactor affects classes in the flux, local, and slurm modules, as well as their corresponding test files, ensuring a more flexible and maintainable codebase.

Changes

FilesChange Summary
pympipool/scheduler/__init__.pyUpdated create_executor function to include executor parameter for submitting workers to Flux.
pympipool/scheduler/flux.pyRefactored PyFluxExecutor and PyFluxStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/local.pyRefactored PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/slurm.pyRefactored PySlurmExecutor and PySlurmStepExecutor to use executor_kwargs dictionary for initialization.
tests/test_flux_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyFluxExecutor.
tests/test_local_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyLocalExecutor and PyLocalStepExecutor.
pympipool/shared/executorbase.pyAdded MpiExecInterface to imports and set default values for cores and interface_class parameters in task execution functions.

Poem

In the realm of code so bright,
Executors now take flight,
With kwargs they align,
Simplifying every line.
From Flux to Local, changes bloom,
Bringing flexibility to every room.
🎩🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5c441d4 and a8c24a3.

Files selected for processing (7)
  • pympipool/scheduler/init.py (3 hunks)
  • pympipool/scheduler/flux.py (5 hunks)
  • pympipool/scheduler/local.py (6 hunks)
  • pympipool/scheduler/slurm.py (6 hunks)
  • tests/test_flux_executor.py (4 hunks)
  • tests/test_local_executor.py (18 hunks)
  • tests/test_local_executor_future.py (4 hunks)
Additional comments not posted (8)
tests/test_flux_executor.py (4)

52-55: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


65-66: The refactoring of the test case to use executor_kwargs for threading configuration is consistent with the changes in the executor classes.


77-78: The refactoring of the test case to use executor_kwargs for parallel execution settings is consistent with the changes in the executor classes.


86-87: The refactoring of the test case to use executor_kwargs for single task execution is consistent with the changes in the executor classes.

tests/test_local_executor_future.py (3)

21-22: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


36-37: The refactoring of the test case to use executor_kwargs for multi-core configuration is consistent with the changes in the executor classes.


67-69: The refactoring of the test case to use executor_kwargs for ensuring independence from the executor is consistent with the changes in the executor classes.

Also applies to: 106-108

tests/test_local_executor.py (1)

102-104: Ensure consistency in the use of executor_kwargs across all test cases.

The changes to the test cases correctly reflect the updated constructors of PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs. This aligns with the PR's objective to simplify parameter passing and enhance flexibility.

Also applies to: 114-116, 129-133, 138-142, 152-153, 162-163, 181-182, 195-196, 205-206, 224-225, 236-240, 277-278, 291-292, 302-305, 318-319, 327-328, 335-336, 355-356, 376-377, 390-391, 407-408

cwd: Optional[str] = None,
hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},
):

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

oversubscribe: bool = False,
cwd: Optional[str] = None,
hostname_localhost: bool = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
):
def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):
super().__init__()

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
def__init__(self, max_workers: int=1, executor_kwargs: dict={}):
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None,
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

backend=backend, flux_installed=flux_installed, slurm_installed=slurm_installed
)
check_pmi(backend=backend, pmi=pmi)
executor_kwargs = {

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- executor_kwargs = {+ executor_kwargs = executor_kwargs or {}

Committable suggestion was skipped due low confidence.

@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: 2

Outside diff range and nitpick comments (1)
pympipool/shared/executorbase.py (1)

17-17: Ensure consistent import order and grouping.

Consider grouping all imports from pympipool.shared.interface together for better readability and maintainability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a8c24a3 and 2138ea3.

Files selected for processing (2)
  • pympipool/shared/executorbase.py (5 hunks)
  • tests/test_local_executor.py (19 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tests/test_local_executor.py

future_queue: queue.Queue,
cores: int,
interface_class: BaseInterface,
cores: int = 1,

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.

Standardize default parameter values across similar functions.

It's good practice to ensure consistency in default parameter values across similar functions to avoid confusion and potential bugs. For instance, cores and interface_class have default values in execute_parallel_tasks and execute_separate_tasks, but not in _submit_function_to_separate_process. Consider adding default values for these parameters in _submit_function_to_separate_process as well.

Also applies to: 259-259, 312-312, 313-313, 553-553

Comment on lines +334 to +335
if "cores" not in kwargs.keys():
kwargs["cores"] = 1

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.

Handle default parameter values more robustly.

Instead of checking if cores is not in kwargs and then setting it to 1, you could use kwargs.get('cores', 1) which is a more Pythonic and concise way to handle default values.

- if "cores" not in kwargs.keys():- kwargs["cores"] = 1+ kwargs.setdefault('cores', 1)

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.

Suggested change
if"cores"notinkwargs.keys():
kwargs["cores"] =1
kwargs.setdefault('cores', 1)

@jan-janssen
jan-janssen merged commit b113227 into mainMay 30, 2024
@jan-janssen
jan-janssen deleted the executor_kwargs branch May 30, 2024 13:35
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

Executor Keyword Arguments - #351

Merged
jan-janssen merged 7 commits into
mainfrom
executor_kwargs
May 30, 2024
Merged

Executor Keyword Arguments#351
jan-janssen merged 7 commits into
mainfrom
executor_kwargs

Conversation

@jan-janssen

@jan-janssenjan-janssen commented May 30, 2024

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • New Features

    • Introduced executor_kwargs parameter to simplify and enhance the flexibility of executor initialization across various backends (Flux, Local, Slurm).
  • Refactor

    • Consolidated multiple individual arguments into a single executor_kwargs dictionary for executor classes to streamline configurations.
    • Updated test cases to use executor_kwargs for passing parameters.
  • Bug Fixes

    • Ensured default values for cores and max_cores parameters in task execution functions to improve reliability.
  • Chores

    • Cleaned up imports and removed unnecessary dependencies in the codebase.

@coderabbitai

coderabbitaiBot commented May 30, 2024

Copy link
Copy Markdown
Contributor

Walkthrough

The recent changes primarily focus on refactoring the pympipool library to streamline the initialization of various executor classes. By introducing an executor_kwargs dictionary parameter, the updates simplify the passing of multiple arguments. This refactor affects classes in the flux, local, and slurm modules, as well as their corresponding test files, ensuring a more flexible and maintainable codebase.

Changes

FilesChange Summary
pympipool/scheduler/__init__.pyUpdated create_executor function to include executor parameter for submitting workers to Flux.
pympipool/scheduler/flux.pyRefactored PyFluxExecutor and PyFluxStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/local.pyRefactored PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs dictionary for initialization.
pympipool/scheduler/slurm.pyRefactored PySlurmExecutor and PySlurmStepExecutor to use executor_kwargs dictionary for initialization.
tests/test_flux_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyFluxExecutor.
tests/test_local_executor.pyUpdated tests to pass parameters via executor_kwargs dictionary for PyLocalExecutor and PyLocalStepExecutor.
pympipool/shared/executorbase.pyAdded MpiExecInterface to imports and set default values for cores and interface_class parameters in task execution functions.

Poem

In the realm of code so bright,
Executors now take flight,
With kwargs they align,
Simplifying every line.
From Flux to Local, changes bloom,
Bringing flexibility to every room.
🎩🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5c441d4 and a8c24a3.

Files selected for processing (7)
  • pympipool/scheduler/init.py (3 hunks)
  • pympipool/scheduler/flux.py (5 hunks)
  • pympipool/scheduler/local.py (6 hunks)
  • pympipool/scheduler/slurm.py (6 hunks)
  • tests/test_flux_executor.py (4 hunks)
  • tests/test_local_executor.py (18 hunks)
  • tests/test_local_executor_future.py (4 hunks)
Additional comments not posted (8)
tests/test_flux_executor.py (4)

52-55: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


65-66: The refactoring of the test case to use executor_kwargs for threading configuration is consistent with the changes in the executor classes.


77-78: The refactoring of the test case to use executor_kwargs for parallel execution settings is consistent with the changes in the executor classes.


86-87: The refactoring of the test case to use executor_kwargs for single task execution is consistent with the changes in the executor classes.

tests/test_local_executor_future.py (3)

21-22: The refactoring of the test case to use executor_kwargs aligns well with the changes in the executor classes.


36-37: The refactoring of the test case to use executor_kwargs for multi-core configuration is consistent with the changes in the executor classes.


67-69: The refactoring of the test case to use executor_kwargs for ensuring independence from the executor is consistent with the changes in the executor classes.

Also applies to: 106-108

tests/test_local_executor.py (1)

102-104: Ensure consistency in the use of executor_kwargs across all test cases.

The changes to the test cases correctly reflect the updated constructors of PyLocalExecutor and PyLocalStepExecutor to use executor_kwargs. This aligns with the PR's objective to simplify parameter passing and enhance flexibility.

Also applies to: 114-116, 129-133, 138-142, 152-153, 162-163, 181-182, 195-196, 205-206, 224-225, 236-240, 277-278, 291-292, 302-305, 318-319, 327-328, 335-336, 355-356, 376-377, 390-391, 407-408

cwd: Optional[str] = None,
hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
command_line_argument_lst: list[str] = [],
executor_kwargs: dict = {},
):

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

oversubscribe: bool = False,
cwd: Optional[str] = None,
hostname_localhost: bool = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

hostname_localhost: bool = False,
):
def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):
super().__init__()

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
def__init__(self, max_workers: int=1, executor_kwargs: dict={}):
def__init__(self, max_workers: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- def __init__(self, max_workers: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_workers: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
executor_kwargs: dict=None,
ifexecutor_kwargsisNone:
executor_kwargs= {}

executor: Optional[flux.job.FluxExecutor] = None,
pmi: Optional[str] = None,
hostname_localhost: Optional[bool] = False,
executor_kwargs: dict = {},

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.

Ensure that executor_kwargs is safely initialized to avoid issues with mutable default arguments.

- def __init__(self, max_cores: int = 1, executor_kwargs: dict = {}):+ def __init__(self, max_cores: int = 1, executor_kwargs: dict = None):+ if executor_kwargs is None:+ executor_kwargs = {}

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.

Suggested change
executor_kwargs: dict={},
def__init__(self, max_cores: int=1, executor_kwargs: dict=None):
ifexecutor_kwargsisNone:
executor_kwargs= {}

backend=backend, flux_installed=flux_installed, slurm_installed=slurm_installed
)
check_pmi(backend=backend, pmi=pmi)
executor_kwargs = {

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.

Consider using a more robust default for executor_kwargs to avoid potential issues with mutable default arguments.

- executor_kwargs = {+ executor_kwargs = executor_kwargs or {}

Committable suggestion was skipped due low confidence.

@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: 2

Outside diff range and nitpick comments (1)
pympipool/shared/executorbase.py (1)

17-17: Ensure consistent import order and grouping.

Consider grouping all imports from pympipool.shared.interface together for better readability and maintainability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a8c24a3 and 2138ea3.

Files selected for processing (2)
  • pympipool/shared/executorbase.py (5 hunks)
  • tests/test_local_executor.py (19 hunks)
Files skipped from review as they are similar to previous changes (1)
  • tests/test_local_executor.py

future_queue: queue.Queue,
cores: int,
interface_class: BaseInterface,
cores: int = 1,

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.

Standardize default parameter values across similar functions.

It's good practice to ensure consistency in default parameter values across similar functions to avoid confusion and potential bugs. For instance, cores and interface_class have default values in execute_parallel_tasks and execute_separate_tasks, but not in _submit_function_to_separate_process. Consider adding default values for these parameters in _submit_function_to_separate_process as well.

Also applies to: 259-259, 312-312, 313-313, 553-553

Comment on lines +334 to +335
if "cores" not in kwargs.keys():
kwargs["cores"] = 1

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.

Handle default parameter values more robustly.

Instead of checking if cores is not in kwargs and then setting it to 1, you could use kwargs.get('cores', 1) which is a more Pythonic and concise way to handle default values.

- if "cores" not in kwargs.keys():- kwargs["cores"] = 1+ kwargs.setdefault('cores', 1)

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.

Suggested change
if"cores"notinkwargs.keys():
kwargs["cores"] =1
kwargs.setdefault('cores', 1)

@jan-janssen
jan-janssen merged commit b113227 into mainMay 30, 2024
@jan-janssen
jan-janssen deleted the executor_kwargs branch May 30, 2024 13:35
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