slfan1989 opened a new pull request, #1366: URL: https://github.com/apache/flink-agents/pull/1366
<!-- * Thank you very much for contributing to Flink Agents. * Please add the relevant components in the PR title. E.g., [api], [runtime], [java], [python], [hotfix], etc. --> <!-- Please link the PR to the relevant issue(s). Hotfix doesn't need this. --> Linked issue: #1365 ### Purpose of change A shared resource name conflict could leave resources from a failed YAML file registered in the Java execution environment. Those resources could then block a retry after the user corrected the file. ### Behavioral Semantics Duplicate shared resource names and chat model names that conflict with an existing router raise `IllegalArgumentException`. The failing file registers nothing, earlier files remain registered, and the corrected file can be retried in the same environment. ### Tests - Duplicate tool name and chat model/router name conflict - Correct and retry the second file after a failed multi-file load ### API Existing Java `loadYaml` signatures are preserved. ### Documentation <!-- Do not remove this section. Check the proper box only. --> - [ ] `doc-needed` <!-- Your PR changes impact docs --> - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs --> - [ ] `doc-included` <!-- Your PR already contains the necessary documentation updates --> ### Was this patch authored or co-authored using generative AI tooling? <!-- Do not remove this section. Check the proper box only. --> - [ ] Yes - [ ] No If yes, include a `Generated-by: <tool name and version> (<model name and version>)` line, for example `Generated-by: Claude Code 2.1.226 (Claude Opus 4.6)`, in the commit message so it reaches Git history. Repeat the same line here for reviewer visibility. See the [ASF generative tooling guidance](https://www.apache.org/legal/generative-tooling.html). -- 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]
