-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Mark SLURM detection methods in AcceleratorConnector
as protected
#10101
Conversation
if these are both internal methods, could we just skip deprecation cycle? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !
@daniellepintz If this goes into 1.5 then for us the cost will be almost 0. I marked it for removal in 1.6 so we can remove it immediately on master. |
Co-authored-by: Justus Schock <12886177+justusschock@users.noreply.github.com>
Codecov Report
@@ Coverage Diff @@
## master #10101 +/- ##
========================================
- Coverage 92% 89% -4%
========================================
Files 182 182
Lines 16153 16164 +11
========================================
- Hits 14940 14332 -608
- Misses 1213 1832 +619 |
…ightning-AI#10101) Co-authored-by: Justus Schock <12886177+justusschock@users.noreply.github.com>
What does this PR do?
Marks two SLURM related APIs as protected.
AcceleratorConnector.is_slurm_managing_tasks
: This is an internal bool used to select the right plugins. A user should checkisinstance(trainer.cluster_environment, SLURMEnvironment)
instead.AcceleratorConnector.configure_slurm_ddp
: This is an internal method used to set bools and select the right plugin for cluster management. A user is not meant to interact directly with this method.I propose a short deprecation phase of 1.5-1.6 because these public methods are likely not being used by anyone.
Part of #9778
Part of #6303
Does your PR introduce any breaking changes? If yes, please list them.
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
I made sure I had fun coding 🙃
Part of #1 (it's a lie, this is just here to avoid noisy GitHub bot)