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

[Doc] We should not add doctest to thirdparty libraries like cloudpickle #23661

Closed
1 of 2 tasks
suquark opened this issue Apr 1, 2022 · 3 comments
Closed
1 of 2 tasks
Assignees
Labels
bug Something that is supposed to be working; but isn't stale The issue is stale. It will be closed within 7 days unless there are further conversation triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@suquark
Copy link
Member

suquark commented Apr 1, 2022

Search before asking

  • I searched the issues and found no similar issues.

Ray Component

Ray Core

Issue Severity

Low: It annoys or frustrates me for a moment.

What happened + What you expected to happen

#23418 formats docs of thirdparty libraries like cloudpickle, this causes serious conflicts when we are updating these libraries.

Versions / Dependencies

latest

Reproduction script

/

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@suquark suquark added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Apr 1, 2022
@suquark
Copy link
Member Author

suquark commented Apr 1, 2022

This affects: #22553

@scv119 scv119 changed the title We should not add doctest to thirdparty libraries like cloudpickle [Doc] We should not add doctest to thirdparty libraries like cloudpickle Apr 5, 2022
@stale
Copy link

stale bot commented Aug 10, 2022

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

  • If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
  • If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.

@stale stale bot added the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Aug 10, 2022
@stale
Copy link

stale bot commented Sep 20, 2022

Hi again! The issue will be closed because there has been no more activity in the 14 days since the last message.

Please feel free to reopen or open a new issue if you'd still like it to be addressed.

Again, you can always ask for help on our discussion forum or Ray's public slack channel.

Thanks again for opening the issue!

@stale stale bot closed this as completed Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't stale The issue is stale. It will be closed within 7 days unless there are further conversation triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

No branches or pull requests

2 participants