coderabbitai[bot]
commented
4 weeks ago Walkthrough
## Walkthrough The recent updates to the documentation enhance clarity on blocking I/O operations in asynchronous programming. New sections detail the `write_bytes`, `write_text`, `read_bytes`, and `read_text` functions, emphasizing their blocking nature and the importance of executing them within an executor. Additionally, a reference to `load_cert_chain` reinforces the guidance for managing blocking calls, thus improving the overall comprehensiveness of the documentation. ## Changes | Files | Change Summary | |-----------------------------------------|-------------------------------------------------------------------------------------------------------| | `docs/asyncio_blocking_operations.md` | Added sections for `write_bytes`, `write_text`, `read_bytes`, `read_text`, and a reference to `load_cert_chain`, clarifying their blocking behavior. | ## Sequence Diagram(s) ```mermaid sequenceDiagram participant User participant AsyncFramework participant Executor User->>AsyncFramework: Call write_bytes() AsyncFramework->>Executor: Submit write_bytes() for execution Executor-->>AsyncFramework: Execute write_bytes() AsyncFramework-->>User: Return result ```Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
bdraco
Proposed change
Document new blocking operations that can be detected being called in event loop
Type of change
Additional information
Summary by CodeRabbit
write_bytes,write_text,read_bytes, andread_textfunctions, detailing their blocking I/O operations in asynchronous programming.load_cert_chain, enhancing the guidance on managing blocking calls within executors.