python/ray/actor.py
    DOC102: Function `method`: Docstring contains more arguments than in function signature.
    DOC106: Function `method`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC103: Function `method`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: , *args: ]. Arguments in the docstring but not in the function signature: [concurrency_group: , max_task_retries: , num_returns: , retry_exceptions: , tensor_transport: ].
    DOC201: Function `method` does not have a return section in docstring
    DOC107: Method `ActorMethod.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC101: Method `ActorMethod.options`: Docstring contains fewer arguments than in function signature.
    DOC106: Method `ActorMethod.options`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC103: Method `ActorMethod.options`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**options: ].
    DOC201: Method `ActorMethod.options` does not have a return section in docstring
    DOC101: Method `_ActorClassMetadata.__init__`: Docstring contains fewer arguments than in function signature.
    DOC107: Method `_ActorClassMetadata.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `_ActorClassMetadata.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [accelerator_type: , actor_creation_function_descriptor: , class_id: , concurrency_groups: , enable_tensor_transport: bool, fallback_strategy: , label_selector: , language: , max_restarts: , max_task_retries: , memory: , method_meta: , modified_class: , num_cpus: , num_gpus: , object_store_memory: , resources: , runtime_env: , scheduling_strategy: SchedulingStrategyT].
    DOC101: Method `ActorClass.__init__`: Docstring contains fewer arguments than in function signature.
    DOC106: Method `ActorClass.__init__`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `ActorClass.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `ActorClass.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [attr: , bases: , name: ].
    DOC101: Method `ActorClass.__call__`: Docstring contains fewer arguments than in function signature.
    DOC106: Method `ActorClass.__call__`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC103: Method `ActorClass.__call__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: , *args: ].
    DOC106: Method `ActorClass.remote`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC103: Method `ActorClass.remote`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: , *args: ]. Arguments in the docstring but not in the function signature: [args: , kwargs: ].
    DOC102: Method `ActorClass.options`: Docstring contains more arguments than in function signature.
    DOC106: Method `ActorClass.options`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC111: Method `ActorClass.options`: The option `--arg-type-hints-in-docstring` is `False` but there are type hints in the docstring arg list
    DOC103: Method `ActorClass.options`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**actor_options: ]. Arguments in the docstring but not in the function signature: [accelerator_type: , allow_out_of_order_execution: , enable_task_events: , fallback_strategy: List[Dict[str, Any]], label_selector: Dict[str, str], lifetime: , max_concurrency: , max_pending_calls: , max_restarts: , max_task_retries: , memory: , name: , namespace: , num_cpus: , num_gpus: , object_store_memory: , resources: Dict[str, float], runtime_env: Dict[str, Any], scheduling_strategy: ].
    DOC201: Method `ActorClass.options` does not have a return section in docstring
    DOC106: Method `ActorClass._remote`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `ActorClass._remote`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC107: Method `ActorHandle.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC107: Method `ActorHandle._deserialization_helper`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC104: Method `ActorHandle._deserialization_helper`: Arguments are the same in the docstring and the function signature, but are in a different order.
    DOC105: Method `ActorHandle._deserialization_helper`: Argument names match, but type hints in these args do not match: weak_ref
    DOC201: Method `ActorHandle._deserialization_helper` does not have a return section in docstring
--------------------
python/ray/client_builder.py
    DOC111: Method `ClientBuilder.env`: The option `--arg-type-hints-in-docstring` is `False` but there are type hints in the docstring arg list
    DOC201: Method `ClientBuilder.env` does not have a return section in docstring
    DOC201: Method `ClientBuilder.namespace` does not have a return section in docstring
--------------------
python/ray/cluster_utils.py
    DOC101: Method `AutoscalingCluster.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `AutoscalingCluster.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**config_kwargs: , autoscaler_v2: bool].
    DOC103: Method `Cluster.add_node`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**node_args: ]. Arguments in the docstring but not in the function signature: [node_args: ].
    DOC101: Method `Cluster.remove_node`: Docstring contains fewer arguments than in function signature.
    DOC106: Method `Cluster.remove_node`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `Cluster.remove_node`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `Cluster.remove_node`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [allow_graceful: ].
    DOC107: Method `Cluster._wait_for_node`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC111: Method `Cluster._wait_for_node`: The option `--arg-type-hints-in-docstring` is `False` but there are type hints in the docstring arg list
    DOC201: Method `Cluster.wait_for_nodes` does not have a return section in docstring
--------------------
python/ray/cross_language.py
    DOC201: Function `java_function` does not have a return section in docstring
    DOC201: Function `cpp_function` does not have a return section in docstring
    DOC201: Function `java_actor_class` does not have a return section in docstring
    DOC201: Function `cpp_actor_class` does not have a return section in docstring
    DOC106: Function `_format_args`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `_format_args`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC107: Function `_get_function_descriptor_for_actor_method`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/dag/compiled_dag_node.py
    DOC201: Function `_check_unused_dag_input_attributes` does not have a return section in docstring
    DOC101: Function `do_allocate_channel`: Docstring contains fewer arguments than in function signature.
    DOC107: Function `do_allocate_channel`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Function `do_allocate_channel`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [self: ].
    DOC101: Function `do_exec_tasks`: Docstring contains fewer arguments than in function signature.
    DOC107: Function `do_exec_tasks`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Function `do_exec_tasks`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [self: ].
    DOC101: Function `do_profile_tasks`: Docstring contains fewer arguments than in function signature.
    DOC107: Function `do_profile_tasks`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Function `do_profile_tasks`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [self: ].
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `CompiledTask.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `CompiledTask.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [dag_node: 'ray.dag.DAGNode', idx: int].
    DOC201: Method `_ExecutableTaskInput.resolve` does not have a return section in docstring
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `ExecutableTask.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `ExecutableTask.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [resolved_args: List[Any], resolved_kwargs: Dict[str, Any], task: 'CompiledTask'].
    DOC201: Method `ExecutableTask.prepare` does not have a return section in docstring
    DOC107: Method `ExecutableTask._compute`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC107: Method `ExecutableTask.exec_operation`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC303: Class `CompiledDAG`: The __init__() docstring does not need a "Returns" section, because it cannot return anything
    DOC103: Method `CompiledDAG.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [default_communicator: Optional[Union[Communicator, str]]]. Arguments in the docstring but not in the function signature: [_default_communicator: ].
    DOC302: Class `CompiledDAG`: The class docstring does not need a "Returns" section, because __init__() cannot return anything
    DOC106: Method `CompiledDAG.execute`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC103: Method `CompiledDAG.execute`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: , *args: ]. Arguments in the docstring but not in the function signature: [args: , kwargs: ].
    DOC106: Method `CompiledDAG.execute_async`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC103: Method `CompiledDAG.execute_async`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: , *args: ]. Arguments in the docstring but not in the function signature: [args: , kwargs: ].
    DOC106: Method `CompiledDAG.visualize`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `CompiledDAG.visualize`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/dag/dag_node.py
    DOC201: Method `DAGNode.with_tensor_transport` does not have a return section in docstring
    DOC101: Method `DAGNode.execute`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `DAGNode.execute`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: , *args: ].
    DOC201: Method `DAGNode.execute` does not have a return section in docstring
    DOC201: Method `DAGNode._get_all_child_nodes` does not have a return section in docstring
    DOC106: Method `DAGNode._raise_nested_dag_node_error`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `DAGNode._raise_nested_dag_node_error`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/dag/dag_node_operation.py
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `_DAGNodeOperation.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `_DAGNodeOperation.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [exec_task_idx: int, method_name: Optional[str], operation_type: _DAGNodeOperationType].
    DOC101: Function `_add_edge`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `_add_edge`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [control_dependency: bool].
    DOC201: Function `_actor_viz_label` does not have a return section in docstring
    DOC201: Function `_node_viz_id_and_label` does not have a return section in docstring
--------------------
python/ray/dag/dag_operation_future.py
    DOC106: Method `ResolvedFuture.__init__`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `ResolvedFuture.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/dag/input_node.py
    DOC101: Method `InputNode.__init__`: Docstring contains fewer arguments than in function signature.
    DOC107: Method `InputNode.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `InputNode.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: , *args: ].
    DOC101: Method `InputAttributeNode.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `InputAttributeNode.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [accessor_method: str, dag_input_node: InputNode, input_type: str, key: Union[int, str]].
--------------------
python/ray/dag/tests/experimental/test_dag_visualization.py
    DOC106: Method `TestVisualizationAscii.parse_ascii_visualization`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `TestVisualizationAscii.parse_ascii_visualization`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/dag/tests/experimental/test_torch_tensor_dag.py
    DOC106: Method `TorchTensorWorker.recv_and_matmul`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `TorchTensorWorker.recv_and_matmul`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC201: Method `TorchTensorWorker.recv_and_matmul` does not have a return section in docstring
--------------------
python/ray/dag/tests/experimental/test_torch_tensor_transport.py
    DOC106: Function `run_driver_to_worker_dag`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `run_driver_to_worker_dag`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC106: Function `run_worker_to_worker_dag`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `run_worker_to_worker_dag`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC106: Function `run_worker_to_driver_dag`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `run_worker_to_driver_dag`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/data/_internal/arrow_ops/transform_pyarrow.py
    DOC201: Function `combine_chunks` does not have a return section in docstring
    DOC201: Function `combine_chunked_array` does not have a return section in docstring
--------------------
python/ray/data/_internal/block_batching/iter_batches.py
    DOC201: Function `_format_in_threadpool` does not have a return section in docstring
--------------------
python/ray/data/_internal/block_batching/util.py
    DOC402: Function `resolve_block_refs` has "yield" statements, but the docstring does not have a "Yields" section
    DOC404: Function `resolve_block_refs` yield type(s) in docstring not consistent with the return annotation. Return annotation exists, but docstring "yields" section does not exist or has 0 type(s).
--------------------
python/ray/data/_internal/datasource/sql_datasource.py
    DOC101: Method `SQLDatasource.supports_sharding`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `SQLDatasource.supports_sharding`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [parallelism: int].
--------------------
python/ray/data/_internal/datasource/tfrecords_datasource.py
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `TFRecordDatasource.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `TFRecordDatasource.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**file_based_datasource_kwargs: , paths: Union[str, List[str]], tf_schema: Optional['schema_pb2.Schema']].
--------------------
python/ray/data/_internal/datasource/webdataset_datasource.py
    DOC201: Function `_valid_sample` does not have a return section in docstring
    DOC201: Function `_check_suffix` does not have a return section in docstring
    DOC101: Function `_tar_file_iterator`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `_tar_file_iterator`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [filerename: Optional[Union[bool, callable, list]], verbose_open: bool].
    DOC402: Function `_tar_file_iterator` has "yield" statements, but the docstring does not have a "Yields" section
    DOC404: Function `_tar_file_iterator` yield type(s) in docstring not consistent with the return annotation. Return annotation exists, but docstring "yields" section does not exist or has 0 type(s).
    DOC402: Function `_group_by_keys` has "yield" statements, but the docstring does not have a "Yields" section
    DOC404: Function `_group_by_keys` yield type(s) in docstring not consistent with the return annotation. Return annotation exists, but docstring "yields" section does not exist or has 0 type(s).
    DOC101: Function `_default_decoder`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `_default_decoder`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [format: Optional[Union[bool, str]]].
    DOC201: Function `_default_decoder` does not have a return section in docstring
    DOC101: Function `_default_encoder`: Docstring contains fewer arguments than in function signature.
    DOC111: Function `_default_encoder`: The option `--arg-type-hints-in-docstring` is `False` but there are type hints in the docstring arg list
    DOC103: Function `_default_encoder`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [format: Optional[Union[str, bool]]].
    DOC201: Function `_default_encoder` does not have a return section in docstring
    DOC102: Method `WebDatasetDatasource._read_stream`: Docstring contains more arguments than in function signature.
    DOC103: Method `WebDatasetDatasource._read_stream`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the docstring but not in the function signature: [decoder: , fileselect: , suffixes: , verbose_open: ].
    DOC403: Method `WebDatasetDatasource._read_stream` has a "Yields" section in the docstring, but there are no "yield" statements, or the return annotation is not a Generator/Iterator/Iterable. (Or it could be because the function lacks a return annotation.)
    DOC404: Method `WebDatasetDatasource._read_stream` yield type(s) in docstring not consistent with the return annotation. Return annotation does not exist or is not Generator[...]/Iterator[...]/Iterable[...], but docstring "yields" section has 1 type(s).
--------------------
python/ray/data/_internal/equalize.py
    DOC101: Function `_equalize`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `_equalize`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [owned_by_consumer: bool].
    DOC103: Function `_shave_all_splits`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [per_split_num_rows: List[List[int]]].
--------------------
python/ray/data/_internal/execution/interfaces/execution_options.py
    DOC201: Method `ExecutionResources.for_limits` does not have a return section in docstring
    DOC101: Method `ExecutionResources.add`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `ExecutionResources.add`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [other: 'ExecutionResources'].
    DOC101: Method `ExecutionResources.subtract`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `ExecutionResources.subtract`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [other: 'ExecutionResources'].
    DOC107: Method `ExecutionResources.satisfies_limit`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC201: Method `ExecutionResources.satisfies_limit` does not have a return section in docstring
--------------------
python/ray/data/_internal/execution/interfaces/executor.py
    DOC201: Method `OutputIterator.get_next` does not have a return section in docstring
    DOC201: Method `Executor.execute` does not have a return section in docstring
--------------------
python/ray/data/_internal/execution/interfaces/physical_operator.py
    DOC201: Method `DataOpTask.on_data_ready` does not have a return section in docstring
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `MetadataOpTask.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `MetadataOpTask.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [object_ref: ray.ObjectRef, task_done_callback: Callable[[], None], task_index: int, task_resource_bundle: Optional[ExecutionResources]].
--------------------
python/ray/data/_internal/execution/interfaces/task_context.py
    DOC106: Method `TaskContext.set_current`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `TaskContext.set_current`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/data/_internal/execution/operators/base_physical_operator.py
    DOC101: Method `OneToOneOperator.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `OneToOneOperator.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [data_context: DataContext].
--------------------
python/ray/data/_internal/execution/operators/hash_shuffle.py
    DOC104: Function `_shuffle_block`: Arguments are the same in the docstring and the function signature, but are in a different order.
    DOC105: Function `_shuffle_block`: Argument names match, but type hints in these args do not match: block, input_index, key_columns, pool, block_transformer, send_empty_blocks, override_partition_id
--------------------
python/ray/data/_internal/execution/operators/map_operator.py
    DOC103: Method `MapOperator.create`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [data_context: DataContext, map_transformer: MapTransformer]. Arguments in the docstring but not in the function signature: [init_fn: , transform_fn: ].
    DOC201: Method `MapOperator.create` does not have a return section in docstring
    DOC101: Function `_map_task`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `_map_task`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: Dict[str, Any], *blocks: Block, ctx: TaskContext, data_context: DataContext, map_transformer: MapTransformer]. Arguments in the docstring but not in the function signature: [blocks: , fn: ].
    DOC402: Function `_map_task` has "yield" statements, but the docstring does not have a "Yields" section
    DOC404: Function `_map_task` yield type(s) in docstring not consistent with the return annotation. Return annotation exists, but docstring "yields" section does not exist or has 0 type(s).
--------------------
python/ray/data/_internal/execution/operators/map_transformer.py
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `MapTransformFn.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `MapTransformFn.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [input_type: MapTransformFnDataType, is_udf: bool, output_block_size_option: Optional[OutputBlockSizeOption]].
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `MapTransformer.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `MapTransformer.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [init_fn: Optional[Callable[[], None]], output_block_size_option_override: Optional[OutputBlockSizeOption], transform_fns: List[MapTransformFn]].
--------------------
python/ray/data/_internal/execution/operators/output_splitter.py
    DOC101: Method `OutputSplitter._get_locations`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `OutputSplitter._get_locations`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [bundle: RefBundle].
--------------------
python/ray/data/_internal/execution/operators/task_pool_map_operator.py
    DOC101: Method `TaskPoolMapOperator.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `TaskPoolMapOperator.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [data_context: DataContext, map_transformer: MapTransformer]. Arguments in the docstring but not in the function signature: [transform_fn: ].
--------------------
python/ray/data/_internal/execution/operators/union_operator.py
    DOC101: Method `UnionOperator.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `UnionOperator.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [*input_ops: PhysicalOperator, data_context: DataContext]. Arguments in the docstring but not in the function signature: [input_ops: ].
--------------------
python/ray/data/_internal/execution/operators/zip_operator.py
    DOC101: Method `ZipOperator.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `ZipOperator.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [*input_ops: PhysicalOperator, data_context: DataContext]. Arguments in the docstring but not in the function signature: [input_ops: ].
--------------------
python/ray/data/_internal/execution/streaming_executor.py
    DOC101: Method `StreamingExecutor._scheduling_loop_step`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `StreamingExecutor._scheduling_loop_step`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [topology: Topology].
--------------------
python/ray/data/_internal/execution/streaming_executor_state.py
    DOC201: Method `OpBufferQueue.has_next` does not have a return section in docstring
    DOC101: Method `OpState.get_output_blocking`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `OpState.get_output_blocking`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [output_split_idx: Optional[int]].
--------------------
python/ray/data/_internal/iterator/stream_split_iterator.py
    DOC101: Method `SplitCoordinator.start_epoch`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `SplitCoordinator.start_epoch`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [split_idx: int].
--------------------
python/ray/data/_internal/logging.py
    DOC201: Function `register_dataset_logger` does not have a return section in docstring
    DOC201: Function `unregister_dataset_logger` does not have a return section in docstring
--------------------
python/ray/data/_internal/logical/operators/n_ary_operator.py
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `NAry.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `NAry.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [*input_ops: LogicalOperator, num_outputs: Optional[int]].
--------------------
python/ray/data/_internal/metadata_exporter.py
    DOC101: Method `Topology.create_topology_metadata`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `Topology.create_topology_metadata`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [op_to_id: Dict['PhysicalOperator', str]].
--------------------
python/ray/data/_internal/numpy_support.py
    DOC111: Function `_convert_datetime_to_np_datetime`: The option `--arg-type-hints-in-docstring` is `False` but there are type hints in the docstring arg list
    DOC101: Function `convert_to_numpy`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `convert_to_numpy`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [column_values: Any].
--------------------
python/ray/data/_internal/output_buffer.py
    DOC101: Method `BlockOutputBuffer.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `BlockOutputBuffer.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [output_block_size_option: Optional[OutputBlockSizeOption]].
--------------------
python/ray/data/_internal/planner/exchange/interfaces.py
    DOC103: Method `ExchangeTaskSpec.reduce`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [*mapper_outputs: List[Block]]. Arguments in the docstring but not in the function signature: [mapper_outputs: ].
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `ExchangeTaskScheduler.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `ExchangeTaskScheduler.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [exchange_spec: ExchangeTaskSpec].
--------------------
python/ray/data/_internal/planner/plan_expression/expression_evaluator.py
    DOC201: Method `_ConvertToArrowExpressionVisitor.visit_UnaryOp` does not have a return section in docstring
--------------------
python/ray/data/_internal/stats.py
    DOC107: Method `DatasetStatsSummary.to_string`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC104: Method `OperatorStatsSummary.from_block_metadata`: Arguments are the same in the docstring and the function signature, but are in a different order.
    DOC105: Method `OperatorStatsSummary.from_block_metadata`: Argument names match, but type hints in these args do not match: operator_name, block_stats, is_sub_operator
    DOC101: Method `OperatorStatsSummary.__repr__`: Docstring contains fewer arguments than in function signature.
    DOC106: Method `OperatorStatsSummary.__repr__`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `OperatorStatsSummary.__repr__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `OperatorStatsSummary.__repr__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [level: ].
--------------------
python/ray/data/_internal/util.py
    DOC201: Function `_estimate_avail_cpus` does not have a return section in docstring
    DOC107: Function `_check_import`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC402: Function `make_async_gen` has "yield" statements, but the docstring does not have a "Yields" section
    DOC404: Function `make_async_gen` yield type(s) in docstring not consistent with the return annotation. Return annotation exists, but docstring "yields" section does not exist or has 0 type(s).
    DOC103: Method `RetryingPyFileSystemHandler.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [retryable_errors: List[str]]. Arguments in the docstring but not in the function signature: [context: ].
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `MemoryProfiler.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `MemoryProfiler.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [poll_interval_s: Optional[float]].
--------------------
python/ray/data/block.py
    DOC201: Method `BlockAccessor.iter_rows` does not have a return section in docstring
    DOC201: Method `BlockAccessor.to_numpy` does not have a return section in docstring
    DOC102: Method `BlockAccessor._get_group_boundaries_sorted`: Docstring contains more arguments than in function signature.
    DOC103: Method `BlockAccessor._get_group_boundaries_sorted`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the docstring but not in the function signature: [block: ].
--------------------
python/ray/data/checkpoint/checkpoint_writer.py
    DOC201: Method `BatchBasedCheckpointWriter.write_block_checkpoint` does not have a return section in docstring
--------------------
python/ray/data/context.py
    DOC201: Method `DataContext.get_current` does not have a return section in docstring
    DOC201: Method `DataContext.get_config` does not have a return section in docstring
--------------------
python/ray/data/datasource/file_datasink.py
    DOC101: Method `_FileDatasink.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `_FileDatasink.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [mode: SaveMode].
    DOC101: Method `BlockBasedFileDatasink.__init__`: Docstring contains fewer arguments than in function signature.
    DOC107: Method `BlockBasedFileDatasink.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `BlockBasedFileDatasink.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**file_datasink_kwargs: , min_rows_per_file: Optional[int], path: ].
--------------------
python/ray/data/datasource/file_meta_provider.py
    DOC101: Method `BaseFileMetadataProvider.expand_paths`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `BaseFileMetadataProvider.expand_paths`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [partitioning: Optional[Partitioning]].
    DOC101: Function `_expand_directory`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `_expand_directory`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [ignore_missing_path: bool].
--------------------
python/ray/data/datasource/filename_provider.py
    DOC201: Method `FilenameProvider.get_filename_for_block` does not have a return section in docstring
    DOC201: Method `FilenameProvider.get_filename_for_row` does not have a return section in docstring
--------------------
python/ray/data/datasource/path_util.py
    DOC201: Function `_has_file_extension` does not have a return section in docstring
--------------------
python/ray/data/grouped_data.py
    DOC103: Method `GroupedData.aggregate`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [*aggs: AggregateFn]. Arguments in the docstring but not in the function signature: [aggs: ].
    DOC103: Method `GroupedData.map_groups`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**ray_remote_args: ]. Arguments in the docstring but not in the function signature: [ray_remote_args: ].
--------------------
python/ray/data/preprocessor.py
    DOC101: Method `Preprocessor._derive_and_validate_output_columns`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `Preprocessor._derive_and_validate_output_columns`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [columns: List[str], output_columns: Optional[List[str]]].
    DOC201: Method `Preprocessor._derive_and_validate_output_columns` does not have a return section in docstring
--------------------
python/ray/data/tests/test_split.py
    DOC106: Function `assert_split_assignment`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `assert_split_assignment`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/exceptions.py
    DOC101: Method `TaskCancelledError.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `TaskCancelledError.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [error_message: Optional[str]].
    DOC304: Class `ActorDiedError`: Class docstring has an argument/parameter section; please put it in the __init__() docstring
    DOC101: Method `ObjectLostError.__init__`: Docstring contains fewer arguments than in function signature.
    DOC106: Method `ObjectLostError.__init__`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `ObjectLostError.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `ObjectLostError.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [call_site: , owner_address: ].
--------------------
python/ray/experimental/channel/auto_transport_type.py
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `TypeHintResolver.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `TypeHintResolver.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [actor_to_gpu_ids: Dict['ray.actor.ActorHandle', List[str]]].
    DOC101: Method `TypeHintResolver._get_gpu_ids`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `TypeHintResolver._get_gpu_ids`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [actor: 'ray.actor.ActorHandle'].
--------------------
python/ray/experimental/channel/common.py
    DOC201: Method `ReaderInterface._read_list` does not have a return section in docstring
    DOC201: Method `ReaderInterface.read` does not have a return section in docstring
    DOC107: Method `WriterInterface.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC101: Method `WriterInterface.write`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `WriterInterface.write`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [val: Any].
    DOC201: Function `_adapt` does not have a return section in docstring
--------------------
python/ray/experimental/channel/communicator.py
    DOC201: Method `Communicator.get_rank` does not have a return section in docstring
    DOC201: Method `Communicator.recv` does not have a return section in docstring
--------------------
python/ray/experimental/channel/cpu_communicator.py
    DOC201: Method `CPUCommunicator.get_rank` does not have a return section in docstring
--------------------
python/ray/experimental/channel/intra_process_channel.py
    DOC101: Method `IntraProcessChannel.__init__`: Docstring contains fewer arguments than in function signature.
    DOC107: Method `IntraProcessChannel.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `IntraProcessChannel.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [_channel_id: Optional[str]].
--------------------
python/ray/experimental/channel/nccl_group.py
    DOC201: Method `_NcclGroup.get_rank` does not have a return section in docstring
    DOC101: Method `_NcclGroup.recv`: Docstring contains fewer arguments than in function signature.
    DOC107: Method `_NcclGroup.recv`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `_NcclGroup.recv`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [allocator: , dtype: 'torch.dtype', shape: Tuple[int]]. Arguments in the docstring but not in the function signature: [buf: ].
    DOC201: Method `_NcclGroup.recv` does not have a return section in docstring
--------------------
python/ray/experimental/channel/shared_memory_channel.py
    DOC101: Function `_create_channel_ref`: Docstring contains fewer arguments than in function signature.
    DOC107: Function `_create_channel_ref`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Function `_create_channel_ref`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [self: ].
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `_ResizeChannel.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `_ResizeChannel.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [_node_id_to_reader_ref_info: Dict[str, ReaderRefInfo]].
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `SharedMemoryType.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `SharedMemoryType.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [buffer_size_bytes: Optional[int], num_shm_buffers: Optional[int]].
    DOC303: Class `Channel`: The __init__() docstring does not need a "Returns" section, because it cannot return anything
    DOC101: Method `Channel.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `Channel.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [_node_id_to_reader_ref_info: Optional[Dict[str, ReaderRefInfo]], _reader_registered: bool, _writer_node_id: Optional['ray.NodeID'], _writer_ref: Optional['ray.ObjectRef'], _writer_registered: bool].
    DOC302: Class `Channel`: The class docstring does not need a "Returns" section, because __init__() cannot return anything
    DOC101: Method `CompositeChannel.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `CompositeChannel.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [_channel_dict: Optional[Dict[ray.ActorID, ChannelInterface]], _channels: Optional[Set[ChannelInterface]], _reader_registered: bool, _writer_registered: bool].
--------------------
python/ray/experimental/channel/torch_tensor_accelerator_channel.py
    DOC201: Method `TorchTensorAcceleratorChannel._recv_cpu_and_gpu_data` does not have a return section in docstring
    DOC201: Function `_get_ranks` does not have a return section in docstring
    DOC201: Function `_init_communicator` does not have a return section in docstring
--------------------
python/ray/experimental/channel/utils.py
    DOC103: Function `split_actors_by_node_locality`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [node: str]. Arguments in the docstring but not in the function signature: [writer_node: ].
--------------------
python/ray/experimental/compiled_dag_ref.py
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `CompiledDAGRef.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `CompiledDAGRef.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [channel_index: Optional[int], dag: 'ray.experimental.CompiledDAG', execution_index: int].
--------------------
python/ray/experimental/internal_kv.py
    DOC101: Function `_internal_kv_put`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `_internal_kv_put`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [key: Union[str, bytes], namespace: Optional[Union[str, bytes]], overwrite: bool, value: Union[str, bytes]].
--------------------
python/ray/experimental/locations.py
    DOC111: Function `get_object_locations`: The option `--arg-type-hints-in-docstring` is `False` but there are type hints in the docstring arg list
    DOC103: Function `get_object_locations`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [obj_refs: List[ObjectRef]]. Arguments in the docstring but not in the function signature: [object_refs: List[ObjectRef]].
    DOC111: Function `get_local_object_locations`: The option `--arg-type-hints-in-docstring` is `False` but there are type hints in the docstring arg list
    DOC103: Function `get_local_object_locations`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [obj_refs: List[ObjectRef]]. Arguments in the docstring but not in the function signature: [object_refs: List[ObjectRef]].
--------------------
python/ray/experimental/shuffle.py
    DOC404: Function `round_robin_partitioner` yield type(s) in docstring not consistent with the return annotation. The yield type (the 0th arg in Generator[...]/Iterator[...]): Tuple[PartitionID, InType]; docstring "yields" section types:
--------------------
python/ray/job_config.py
    DOC101: Method `JobConfig.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `JobConfig.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [_client_job: bool, _py_driver_sys_path: Optional[List[str]]].
    DOC106: Method `JobConfig.from_json`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `JobConfig.from_json`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC201: Method `JobConfig.from_json` does not have a return section in docstring
--------------------
python/ray/remote_function.py
    DOC101: Method `RemoteFunction.__init__`: Docstring contains fewer arguments than in function signature.
    DOC106: Method `RemoteFunction.__init__`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `RemoteFunction.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `RemoteFunction.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [function: , function_descriptor: , language: , task_options: ].
    DOC102: Method `RemoteFunction.options`: Docstring contains more arguments than in function signature.
    DOC106: Method `RemoteFunction.options`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC111: Method `RemoteFunction.options`: The option `--arg-type-hints-in-docstring` is `False` but there are type hints in the docstring arg list
    DOC103: Method `RemoteFunction.options`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**task_options: ]. Arguments in the docstring but not in the function signature: [_labels: , accelerator_type: , enable_task_events: , fallback_strategy: List[Dict[str, Any]], label_selector: Dict[str, str], max_calls: , max_retries: , memory: , num_cpus: , num_gpus: , num_returns: , object_store_memory: , resources: Dict[str, float], retry_exceptions: , runtime_env: Dict[str, Any], scheduling_strategy: ].
    DOC201: Method `RemoteFunction.options` does not have a return section in docstring
--------------------
python/ray/runtime_context.py
    DOC201: Function `get_runtime_context` does not have a return section in docstring
--------------------
python/ray/runtime_env/runtime_env.py
    DOC101: Method `RuntimeEnvConfig.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `RuntimeEnvConfig.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [log_files: Optional[List[str]]].
    DOC101: Method `RuntimeEnv.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `RuntimeEnv.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [**kwargs: , _validate: bool, py_executable: Optional[str]].
--------------------
python/ray/scripts/scripts.py
    DOC101: Function `kill_procs`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `kill_procs`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [force: bool, grace_period: int, processes_to_kill: List[str]].
    DOC101: Function `submit`: Docstring contains fewer arguments than in function signature.
    DOC107: Function `submit`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Function `submit`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [args: , cluster_config_file: , cluster_name: , disable_usage_stats: , extra_screen_args: Optional[str], no_config_cache: , port_forward: , screen: , script: , script_args: , start: , stop: , tmux: ].
--------------------
python/ray/tests/autoscaler_test_utils.py
    DOC201: Method `MockProcessRunner.assert_has_call` does not have a return section in docstring
--------------------
python/ray/tests/aws/utils/helpers.py
    DOC106: Function `node_provider_tags`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `node_provider_tags`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC106: Function `apply_node_provider_config_updates`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `apply_node_provider_config_updates`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/tests/conftest.py
    DOC107: Function `wait_for_redis_to_start`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC104: Function `wait_for_redis_to_start`: Arguments are the same in the docstring and the function signature, but are in a different order.
    DOC105: Function `wait_for_redis_to_start`: Argument names match, but type hints in these args do not match: redis_ip_address, redis_port
--------------------
python/ray/tests/kuberay/test_kuberay_node_provider.py
    DOC106: Function `test_create_node_cap_at_max`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `test_create_node_cap_at_max`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/tests/kuberay/utils.py
    DOC404: Function `_kubectl_port_forward` yield type(s) in docstring not consistent with the return annotation. The yield type (the 0th arg in Generator[...]/Iterator[...]): int; docstring "yields" section types: The local port. The service can then be accessed at 127.0.0.1
    DOC101: Function `kubectl_delete`: Docstring contains fewer arguments than in function signature.
    DOC103: Function `kubectl_delete`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [wait: bool].
--------------------
python/ray/tests/modin/modin_test_utils.py
    DOC106: Function `df_equals`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `df_equals`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/tests/test_autoscaler_gcp.py
    DOC106: Function `test_gcp_broken_pipe_retry`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Function `test_gcp_broken_pipe_retry`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
--------------------
python/ray/tests/test_batch_node_provider_unit.py
    DOC106: Method `BatchingNodeProviderTester.update`: The option `--arg-type-hints-in-signature` is `True` but there are no argument type hints in the signature
    DOC107: Method `BatchingNodeProviderTester.update`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC111: Method `BatchingNodeProviderTester.update`: The option `--arg-type-hints-in-docstring` is `False` but there are type hints in the docstring arg list
    DOC201: Method `BatchingNodeProviderTester.update` does not have a return section in docstring
--------------------
python/ray/tests/test_client_reconnect.py
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `MiddlemanDataServicer.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `MiddlemanDataServicer.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [on_request: Optional[Hook], on_response: Optional[Hook]].
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `MiddlemanLogServicer.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `MiddlemanLogServicer.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [on_response: Optional[Hook]].
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `MiddlemanRayletServicer.__init__`: Docstring contains fewer arguments than in function signature.
    DOC103: Method `MiddlemanRayletServicer.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [on_request: Optional[Hook], on_response: Optional[Hook]].
    DOC001: Method `__init__` Potential formatting errors in docstring. Error message: No specification for "Args": ""
    DOC001: Function/method `__init__`: Potential formatting errors in docstring. Error message: No specification for "Args": "" (Note: DOC001 could trigger other unrelated violations under this function/method too. Please fix the docstring formatting first.)
    DOC101: Method `MiddlemanServer.__init__`: Docstring contains fewer arguments than in function signature.
    DOC107: Method `MiddlemanServer.__init__`: The option `--arg-type-hints-in-signature` is `True` but not all args in the signature have type hints
    DOC103: Method `MiddlemanServer.__init__`: Docstring arguments are different from function arguments. (Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ). Arguments in the function signature but not in the docstring: [listen_addr: str, on_data_request: Optional[Hook], on_data_response: Optional[Hook], on_log_response: Optional[Hook], on_task_request: Optional[Hook], on_task_response: Optional[Hook], real_addr: ].
--------------------
