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

[Train] Remove deprecated mosaic and sklearn trainer code #47901

Merged
merged 5 commits into from
Oct 8, 2024

Conversation

Superskyyy
Copy link
Contributor

@Superskyyy Superskyyy commented Oct 4, 2024

#42257
#42814

Why are these changes needed?

Both trainers are now hard-deprecated. This PR removes the code paths that confuses Ray train users on Mosaic and Sklearn. This should have been done a while ago.

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: Superskyyy <yihaochen@apache.org>
Signed-off-by: Superskyyy <yihaochen@apache.org>
Signed-off-by: Superskyyy <yihaochen@apache.org>
@Superskyyy
Copy link
Contributor Author

I'm not sure about the mosaic util - RayLogger, is it still potentially required by TorchTrainer in any case?

@Superskyyy Superskyyy changed the title Remove deprecated mosaic and sklearn trainer code [Train] Remove deprecated mosaic and sklearn trainer code Oct 4, 2024
@Superskyyy Superskyyy marked this pull request as ready for review October 4, 2024 17:13
Signed-off-by: Superskyyy <yihaochen@apache.org>
Copy link
Contributor

@matthewdeng matthewdeng left a comment

Choose a reason for hiding this comment

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

Thank you for doing this!

Copy link
Contributor

Choose a reason for hiding this comment

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

We can go ahead and remove this entirely, the RayLogger was only used as part of the MosaicTrainer before.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, thanks!

Copy link
Contributor

Choose a reason for hiding this comment

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

Could you also do a quick scan to remove anything that might reference these? e.g. I saw there is a python/ray/train/examples/mosaic_cifar10_example.py that references the MosaicTrainer.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, I will do that

@anyscalesam
Copy link
Contributor

@Superskyyy is this ready for re-review?

@matthewdeng matthewdeng added the go add ONLY when ready to merge, run all tests label Oct 8, 2024
@matthewdeng matthewdeng merged commit 5e4b1bc into ray-project:master Oct 8, 2024
6 checks passed
ujjawal-khare pushed a commit to ujjawal-khare-27/ray that referenced this pull request Oct 15, 2024
…t#47901)

**Both trainers are now hard-deprecated.** This PR removes the code
paths that confuses Ray train users on Mosaic and Sklearn. This should
have been done a while ago.

Signed-off-by: Superskyyy <yihaochen@apache.org>
Signed-off-by: ujjawal-khare <ujjawal.khare@dream11.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants