Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't needlessly instantiate GlobusComputeExecutor #1704

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

khk-globus
Copy link
Contributor

The MEP does not use an Executor, and even takes pains to prevent it from being specified (e.g., from user error or oversight) in the MEP configuration. However, because the MEP and UEP have initially shared the same basal data structure, and the Config() object historically automatically created the Executor, the MEP codes have been needlessly instantiating a useless executor. No more.

Type of change

  • Bug fix (non-breaking change that fixes an issue)

The MEP does not use an Executor, and even takes pains to prevent it from being
specified (e.g., from user error or oversight) in the MEP configuration.
However, because the MEP and UEP have initially shared the same basal data
structure, and the `Config()` object historically automatically created the
Executor, the MEP codes have been needlessly instantiating a useless executor.
No more.
@khk-globus khk-globus added no-news-is-good-news This change does not require a news file quick-review Review of this should be quick and easy labels Nov 4, 2024
@khk-globus khk-globus requested a review from rjmello November 4, 2024 15:32
@khk-globus khk-globus merged commit 2684bf9 into main Nov 4, 2024
17 checks passed
@khk-globus khk-globus deleted the do_not_instantiate_executor_for_MEPs branch November 4, 2024 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-news-is-good-news This change does not require a news file quick-review Review of this should be quick and easy
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants