Rishankgupta08 commented on issue #458: URL: https://github.com/apache/flink-agents/issues/458#issuecomment-6899034842
Hi Flink Agents maintainers, I'd like to work on the remaining live-refresh part of this issue. I'd like to investigate the MCP list-changed notification flow and implement a safe runtime refresh mechanism that handles tool/prompt additions and removals without exposing a partially updated catalog. I'd also cover duplicate-name conflicts, reconnection, resource cleanup, and concurrent tool lookups during refresh with regression tests. Could you confirm whether notification-driven refresh is the intended direction for #458? Should the initial implementation target Java MCP servers first, or should it cover both Java and Python? Thanks! -- 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]
