Skip to content

Fix the problem that ray.remote reference is not visible at a document.#7311

Merged
simon-mo merged 2 commits intoray-project:masterfrom
rkooo567:ray-remote-doc-issue-2
Feb 28, 2020
Merged

Fix the problem that ray.remote reference is not visible at a document.#7311
simon-mo merged 2 commits intoray-project:masterfrom
rkooo567:ray-remote-doc-issue-2

Conversation

@rkooo567
Copy link
Copy Markdown
Contributor

Why are these changes needed?

ray.remote document is not visible at the latest document. It is because we use fake_ray.remote for doc generation.

Related issue number

Checks

@simon-mo
Copy link
Copy Markdown
Contributor

can you revert the deletion of doc/_build/.gitkeep? you can just touch doc/_build/.gitkeep

Copy link
Copy Markdown
Contributor

@simon-mo simon-mo left a comment

Choose a reason for hiding this comment

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

lgtm, let's check if the doc build successfully

@rkooo567
Copy link
Copy Markdown
Contributor Author

@simon-mo Btw, format.sh deleted /doc/_build/.gitkeep. I am wondering if it is okay? Can you confirm?

@AmplabJenkins
Copy link
Copy Markdown

Can one of the admins verify this patch?

@AmplabJenkins
Copy link
Copy Markdown

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/22365/
Test FAILed.

@rkooo567
Copy link
Copy Markdown
Contributor Author

Jenkins test this please.

@AmplabJenkins
Copy link
Copy Markdown

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/22391/
Test FAILed.

@rkooo567
Copy link
Copy Markdown
Contributor Author

Jenkins test this please.

@AmplabJenkins
Copy link
Copy Markdown

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/22459/
Test FAILed.

@simon-mo
Copy link
Copy Markdown
Contributor

@rkooo567 don't worry about jenkins test, can you add .gitkeep back? once you have done that i'll merge it

@rkooo567
Copy link
Copy Markdown
Contributor Author

@simon-mo Please force merge once it is ready.

@fyrestone
Copy link
Copy Markdown
Contributor

@ray.remote will be executed when sphinx generating doc. If a isinstance(x, cython type) exists in @ray.remote logic, sphinx will raise an exception because cython types are mocked as objects not types.

@AmplabJenkins
Copy link
Copy Markdown

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/22478/
Test PASSed.

Copy link
Copy Markdown
Contributor

@raulchen raulchen left a comment

Choose a reason for hiding this comment

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

Thanks for fixing this.

@simon-mo simon-mo merged commit 50145e6 into ray-project:master Feb 28, 2020
@simon-mo
Copy link
Copy Markdown
Contributor

@fyrestone the doc seems to be building with this PR (without the exception). Is there any way we can catch the instance(x, cython type) error? If so we you help us create a separate PR to fix the cython mocking?

ffbin pushed a commit to antgroup/ant-ray that referenced this pull request Mar 20, 2020
@rkooo567 rkooo567 deleted the ray-remote-doc-issue-2 branch February 17, 2022 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants