Skip to content

[CI] Re-enable isort for python/ray/data #52734

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

MortalHappiness
Copy link
Member

Why are these changes needed?

Follow-up for #52712

Related issue number

N/A

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

@MortalHappiness MortalHappiness requested a review from a team as a code owner May 2, 2025 04:12
@MortalHappiness MortalHappiness requested a review from aslonnie May 2, 2025 04:13
Comment on lines 143 to 146
)
from ray.core.generated.export_dataset_metadata_pb2 import (
Operator as ProtoOperator,
)
from ray.core.generated.export_dataset_metadata_pb2 import (
SubStage as ProtoSubStage,
)
from ray.core.generated.export_dataset_metadata_pb2 import (
Topology as ProtoTopology,
)
Copy link
Collaborator

Choose a reason for hiding this comment

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

this splitting looks weird. why they are not merged but split?

Copy link
Member Author

@MortalHappiness MortalHappiness May 2, 2025

Choose a reason for hiding this comment

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

I created another PR to address this #52742

I turned this PR to draft to avoid introducing additional changes other than python/ray/data in this PR.

Copy link
Member Author

Choose a reason for hiding this comment

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

@aslonnie I've rebased with the master branch and it should be good now.

Comment on lines 6 to 10
)
from ray.llm._internal.batch.processor import (
Processor,
)
from ray.llm._internal.batch.processor import (
ProcessorConfig as _ProcessorConfig,
)
from ray.llm._internal.batch.processor import (
SGLangEngineProcessorConfig as _SGLangEngineProcessorConfig,
)
from ray.llm._internal.batch.processor import (
vLLMEngineProcessorConfig as _vLLMEngineProcessorConfig,
)
Copy link
Collaborator

Choose a reason for hiding this comment

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

why does the splitting happen?

@MortalHappiness MortalHappiness marked this pull request as draft May 2, 2025 15:42
@MortalHappiness MortalHappiness force-pushed the feature/isort-ray-data branch from 650166e to 7a17c94 Compare May 3, 2025 06:01
@MortalHappiness MortalHappiness marked this pull request as ready for review May 3, 2025 06:02
@aslonnie aslonnie added the go add ONLY when ready to merge, run all tests label May 3, 2025
@aslonnie aslonnie self-requested a review May 3, 2025 14:10
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.

2 participants