examples/data visualization app #1892
Draft
Conversation
This file contains 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
Changes: - Addition of post init function to Workflows to sync the session ids of Agents
…into refactor/agno
## Description **Please include:** - **Summary of changes**: Clearly describe the key changes in this PR and their purpose. - **Related issues**: Mention if this PR fixes or is connected to any issues (e.g., "Fixes #123" or "Relates to #456"). - **Motivation and context**: Explain the reason for the changes and the problem they solve. - **Environment or dependencies**: Specify any changes in dependencies or environment configurations required for this update. - **Impact on AI/ML components**: (If applicable) Describe changes to AI/ML models and include performance metrics (e.g., accuracy, F1-score). Fixes # (issue) ## Type of change Please check the options that are relevant: - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Model update - [ ] Infrastructure change ## Checklist - [ ] My code follows Phidata's style guidelines and best practices - [ ] I have performed a self-review of my code - [ ] I have added docstrings and comments for complex logic - [ ] My changes generate no new warnings or errors - [ ] I have added cookbook examples for my new addition (if needed) - [ ] I have updated requirements.txt/pyproject.toml (if needed) - [ ] I have verified my changes in a clean environment ## Additional Notes Include any deployment notes, performance implications, or other relevant information: --------- Co-authored-by: Dirk Brand <[email protected]>
This renames a few models and sorts out all the cookbooks. All the models are also tested after this. This goes with the [compatibility matrix ](https://www.notion.so/Compatibility-Matrix-Analysis-176733793ba2802f8658c5cdd8a93bb4?pvs=4)
## Description Fixes # (issue) ## Type of change Please check the options that are relevant: - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Model update - [ ] Infrastructure change ## Checklist - [ ] My code follows Phidata's style guidelines and best practices - [ ] I have performed a self-review of my code - [ ] I have added docstrings and comments for complex logic - [ ] My changes generate no new warnings or errors - [ ] I have added cookbook examples for my new addition (if needed) - [ ] I have updated requirements.txt/pyproject.toml (if needed) - [ ] I have verified my changes in a clean environment ## Additional Notes Include any deployment notes, performance implications, or other relevant information:
If you have agents that produce structured_output, and then you stored that in the session_state, it would break because classes would not be json serialisable. This fixes that --------- Co-authored-by: Ayush <[email protected]> Co-authored-by: ansub <[email protected]>
Changes: - Concurrent execution of tools Notes: - Please uncomment line 485 of `libs/agno/agno/models/base.py` to confirm the concurrent execution of tools. I will remove it in an update afterwards. - With arun/aprint_response, it would be advisable to use custom async tools (We can also start supporting Async Toolkits). But it fully supports sync functions as well To test: - Please run `cookbook/tools/async/demo.py` and `cookbook/agent_concepts/async/tool_use.py` Next steps: - Catch the error when a user tries to use an async function with run/print_response. - Integration of `stop_execution_after_tool_call` logic in `arun_function_calls` --------- Co-authored-by: Dirk Brand <[email protected]> Co-authored-by: Ashpreet <[email protected]>
Co-authored-by: Dirk Brand <[email protected]> Co-authored-by: Willem Carel de Jongh <[email protected]>
## Description **Please include:** - added agentic rag usecase Please check the options that are relevant: - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Model update - [ ] Infrastructure change ## Checklist - [x] My code follows Phidata's style guidelines and best practices - [x] I have performed a self-review of my code - [x] I have added docstrings and comments for complex logic - [x] My changes generate no new warnings or errors - [x] I have added cookbook examples for my new addition (if needed) - [x] I have updated requirements.txt/pyproject.toml (if needed) - [x] I have verified my changes in a clean environment ## Additional Notes Include any deployment notes, performance implications, or other relevant information: --------- Co-authored-by: Manthan Gupta <[email protected]> Co-authored-by: Dirk Brand <[email protected]>
## Description Chess team example Please check the options that are relevant: - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Model update - [ ] Infrastructure change ## Checklist - [ ] My code follows Phidata's style guidelines and best practices - [ ] I have performed a self-review of my code - [ ] I have added docstrings and comments for complex logic - [ ] My changes generate no new warnings or errors - [ ] I have added cookbook examples for my new addition (if needed) - [ ] I have updated requirements.txt/pyproject.toml (if needed) - [ ] I have verified my changes in a clean environment ## Additional Notes Include any deployment notes, performance implications, or other relevant information: --------- Co-authored-by: Dirk Brand <[email protected]> Co-authored-by: Dirk Brand <[email protected]>
Co-authored-by: Dirk Brand <[email protected]>
…into examples/data-visualization
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Please include:
Please check the options that are relevant:
Checklist
Additional Notes
Include any deployment notes, performance implications, or other relevant information: