Skip to content

try fix doc build ..#57163

Closed
aslonnie wants to merge 1 commit intomasterfrom
lonnie-251003-docfix
Closed

try fix doc build ..#57163
aslonnie wants to merge 1 commit intomasterfrom
lonnie-251003-docfix

Conversation

@aslonnie
Copy link
Copy Markdown
Collaborator

@aslonnie aslonnie commented Oct 3, 2025

No description provided.

@aslonnie aslonnie requested a review from a team as a code owner October 3, 2025 17:03
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request aims to fix the documentation build by removing ray.data._internal.arrow_ops from the list of mocked modules. This change seems plausible, but it might be incomplete. I've pointed out that a dependency, ray.air.util.tensor_extensions, is still mocked, which could cause new import errors. I recommend also removing ray.air.util.tensor_extensions from the mocked list to prevent this. For future pull requests, providing a more descriptive title and a body explaining the problem and the fix would be very helpful for reviewers.

"ray.core.generated",
"ray.serve.generated",
"ray.air.util.tensor_extensions",
"ray.data._internal.arrow_ops",
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.

high

While removing ray.data._internal.arrow_ops from the mocked imports is a good step, this change might be incomplete and could lead to further import errors during the documentation build.

The module ray.data._internal.arrow_ops.transform_pyarrow (which will now be imported) has a dependency on ray.air.util.tensor_extensions.arrow. However, ray.air.util.tensor_extensions is still listed in autodoc_mock_imports on the line above. Mocking the parent package ray.air.util.tensor_extensions will likely cause the import of its submodule arrow to fail.

To fully resolve the issue, you should consider also removing ray.air.util.tensor_extensions from autodoc_mock_imports. Its own dependencies like numpy and pyarrow are already mocked, so it should be safe to un-mock it.

@aslonnie aslonnie force-pushed the lonnie-251003-docfix branch from 49f450d to df8709d Compare October 3, 2025 17:33
cursor[bot]

This comment was marked as outdated.

Copy link
Copy Markdown
Contributor

@dstrodtman dstrodtman left a comment

Choose a reason for hiding this comment

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

I believe I'm currently seeing the related errors here. Haven't tested the fix, but stamping to unblock

@dstrodtman dstrodtman mentioned this pull request Oct 3, 2025
8 tasks
Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
@aslonnie aslonnie force-pushed the lonnie-251003-docfix branch from df8709d to 5ebca78 Compare October 3, 2025 18:12
@ray-gardener ray-gardener bot added docs An issue or change related to documentation core Issues that should be addressed in Ray Core labels Oct 3, 2025
@aslonnie aslonnie closed this Oct 3, 2025
@aslonnie aslonnie deleted the lonnie-251003-docfix branch November 2, 2025 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Issues that should be addressed in Ray Core docs An issue or change related to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants