wenjin272 commented on issue #458:
URL: https://github.com/apache/flink-agents/issues/458#issuecomment-6906121735

   Thanks @Rishankgupta08 for offering to work on this! Startup discovery has 
already been implemented in #1373 for #606, so this issue can focus on updates 
while the job is running.
   
   Could you start a Discussion with a detailed design proposal before 
implementation? I’d like us to compare notification-driven refresh with 
alternatives, such as refreshing on demand with an optional TTL, before 
choosing a direction.
   
   Please cover:
   
   - Tool/prompt additions, removals, and changes to existing definitions, 
including how newly discovered tools become available to an Agent.
   - The full flow from detecting a change to using the updated definitions in 
model requests and tool execution, with a sequence diagram showing the 
components and their execution contexts.
   - How refresh interacts with in-flight requests, failures, name conflicts, 
reconnection, and resource cleanup.
   - The proposed Java/Python scope, cross-language implications, and how the 
implementation builds on #1373.
   - The behavioral contracts and how they will be tested.
   
   We can then discuss the tradeoffs and agree on the approach and scope for 
the initial implementation.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to