slfan1989 commented on issue #1365: URL: https://github.com/apache/flink-agents/issues/1365#issuecomment-6753320568
> Thanks for reporting this and providing a reproducible example. Could you share the use case that requires reusing the same `AgentsExecutionEnvironment` after YAML loading fails? In a typical job submission, a configuration error would fail startup, and the next submission would create a new environment. Understanding the intended workflow would help us assess the impact and expected behavior. Thanks, @wenjin272 . I found this while testing `loadYaml` locally. I loaded a valid YAML file, then loaded a second file with a resource name conflict. After fixing the conflict, I retried in the same environment and found that a resource left behind by the failed load blocked the retry. I agree that a typical job submission would start with a fresh environment. I don’t have a production use case that requires retrying in place. The concern behind #1366 is that a failed file load can still modify the caller’s environment. -- 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]
