Conversation
…tructure and remove deprecated features - Updated README files to clarify the usage of the `pulsing actor` command, now requiring full class paths for actor types. - Enhanced documentation for starting actors, including examples for the new Router and worker classes. - Removed references to the deprecated `pulsing actor list` command, replacing it with `pulsing inspect` for actor system observation. - Updated various examples and guides to align with the new command structure and improve user understanding.
…onality - Introduced `pulsing_pingpong.py` demonstrating a simple ping-pong interaction using the @Remote decorator. - Added `pulsing_research.py` showcasing a multi-agent research workflow with Researcher, Analyst, and Reporter agents. - Created `chaos_proof.py` to illustrate actor resilience with automatic restarts on failure, simulating task completion despite crashes. - Implemented `function_to_fleet.py` to demonstrate scaling functions into a fleet of workers for improved throughput. - Updated README with new examples and usage instructions for enhanced clarity and user guidance.
- Added new sections to the API documentation, including an overview of core concepts and detailed usage patterns for the Pulsing framework. - Updated existing examples to reflect recent changes in actor spawning and resolution methods, ensuring clarity and usability. - Improved documentation for the `@pul.remote` decorator and actor lifecycle management, providing clearer guidance for users. - Introduced new API reference files for both Python and Rust, enhancing accessibility and understanding of the framework's capabilities. - Refactored various documentation files to improve consistency and readability across the codebase.
…g framework - Revised descriptions in `README.md`, `README.zh.md`, and `llms.binding.md` to emphasize Pulsing as a distributed actor framework with specialized support for AI applications. - Improved site description in `mkdocs.yml` for better alignment with the framework's capabilities. - Added a comprehensive FAQ section in `faq.md` and its Chinese counterpart `faq.zh.md`, addressing common user questions and installation issues. - Enhanced navigation structure in `mkdocs.yml` for better accessibility to documentation resources. - Updated API overview documentation to reflect recent changes and improve user understanding of the framework's functionalities.
- Added a newline at the end of the FAQ sections in both English and Chinese versions of the document to adhere to markdown standards and improve readability.
… installation - Added cargo-binstall action to streamline the installation of Rust tools. - Updated installation command for cargo-nextest to use cargo binstall for improved security and efficiency.
…ld-env action to default to latest version, streamlining the installation process.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview:
Details:
Where should the reviewer start?
Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)