Conversation
…ocking the caller. Added a new method for handling summary tasks asynchronously and improved error logging for background operations.
…d `get_knowledge_chunk` method to return `None` for backward compatibility and added logging for deprecation. Removed unused chunk-related methods and adjusted memory store initialization to support SQLite or in-memory options. Cleaned up environment configuration by removing obsolete parameters.
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a fundamental change in how knowledge and tool results are managed within the system. By moving away from granular chunk-based retrieval and indexing, the process of offloading and accessing context information becomes more streamlined and efficient. The focus shifts to treating entire artifacts as units, simplifying the architecture and improving responsiveness by offloading heavy operations like summary generation to background tasks. This change aims to enhance the system's performance and maintainability by reducing complexity in knowledge management. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request effectively decouples the system from the chunk-based knowledge retrieval mechanism, which is a significant and positive refactoring. The changes simplify the knowledge service and workspace implementations by removing complex chunking, indexing, and retrieval logic. I've also noticed a good improvement in aworld/memory/main.py where summary generation is now non-blocking.
My main feedback is regarding some leftover parameters in a refactored function signature in knowledge_service.py, which could lead to confusion and is a breaking change that needs to be propagated to its call site. Please see the specific comment for details.
| top_k: int = 20, load_content: bool = True, load_index: bool = True, | ||
| search_by_index: bool = True) -> str: |
There was a problem hiding this comment.
The parameters load_content, load_index, and search_by_index are no longer used in the new implementation of this function. To improve code clarity and maintainability, they should be removed from the function signature.
Note that this is a breaking change. You will also need to update the call to this function in aworld.core.context.amni.ApplicationContext.load_context_by_workspace to remove these arguments.
top_k: int = 20) -> str:
No description provided.