-
Notifications
You must be signed in to change notification settings - Fork 3
Bugfix/agent new #1281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix/agent new #1281
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary of ChangesHello @athul-ab, 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 refines the user experience in two key areas: simplifying the agent creation process and enhancing the log viewing functionality. The 'Add Agent' workflow has been streamlined by removing an unnecessary model selection step, making the process more efficient. Concurrently, the agent logs page has been upgraded to support reverse infinite scrolling for historical data, improving navigation and access to older logs. Additionally, the behavior of live log streaming has been adjusted to append new entries and preserve existing data when switching to live mode, providing a more consistent and user-friendly logging interface. 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces two main changes. First, it refactors the 'Add Agent' flow by removing the separate 'Select Model' step, which simplifies the user experience. The related changes across multiple files are consistent. Second, it significantly refactors the logs view to implement a reverse infinite scroll for historical data and improves the handling of live data. While the reverse scroll is a good UX improvement, I've identified a potential issue with how live data is stored, which could lead to performance problems over time. My review includes a specific comment and suggestion to address this.
|
|
||
| console.log('[LiveTrace] Created LogEntry:', newEntry); | ||
| setLogsData(prev => [newEntry, ...prev].slice(0, MAX_LIVE_ITEMS)); | ||
| setLogsData(prev => [...prev, newEntry]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In live mode, the logsData array is appended with new entries without any size limit. This could lead to performance degradation and high memory usage over time if a large number of traces are received. The previous implementation had a MAX_LIVE_ITEMS limit which has been removed.
It's recommended to re-introduce a limit on the number of items stored for the live view. A similar change should be applied on lines 1202 and 1232.
| setLogsData(prev => [...prev, newEntry]); | |
| setLogsData(prev => [...prev, newEntry].slice(-200)); |
References
- To prevent potential memory leaks and performance degradation, it's important to cap the size of arrays that can grow indefinitely, especially when handling real-time data streams.
No description provided.