[GitHub] [flink-kubernetes-operator] yangjf2019 commented on pull request #567: [FLINK-31815] Fixing the container vulnerability by upgrade the SnakeYaml Maven dependency

2023-04-27 Thread via GitHub
yangjf2019 commented on PR #567: URL: https://github.com/apache/flink-kubernetes-operator/pull/567#issuecomment-1526847015 Okay, I'll fix it, 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

[GitHub] [flink-kubernetes-operator] yangjf2019 commented on pull request #567: [FLINK-31815] Fixing the container vulnerability by upgrade the SnakeYaml Maven dependency

2023-04-26 Thread via GitHub
yangjf2019 commented on PR #567: URL: https://github.com/apache/flink-kubernetes-operator/pull/567#issuecomment-1524470721 Ok, I've updated this file, please take a look, thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [flink-kubernetes-operator] yangjf2019 commented on pull request #567: [FLINK-31815] Fixing the container vulnerability by upgrade the SnakeYaml Maven dependency

2023-04-21 Thread via GitHub
yangjf2019 commented on PR #567: URL: https://github.com/apache/flink-kubernetes-operator/pull/567#issuecomment-1517823027 I found that the exception is generated when I commit `e2e-tests/data/flinkdep-cr.yaml` and run `default/flink-example-statemachine`, do we need to upgrade the flink

[GitHub] [flink-kubernetes-operator] yangjf2019 commented on pull request #567: [FLINK-31815] Fixing the container vulnerability by upgrade the SnakeYaml Maven dependency

2023-04-19 Thread via GitHub
yangjf2019 commented on PR #567: URL: https://github.com/apache/flink-kubernetes-operator/pull/567#issuecomment-1515659259 I understand that although I was able to compile the project locally, the CI was running with the lower version of the `org.yaml:snakeyaml:1.33` dependency in

[GitHub] [flink-kubernetes-operator] yangjf2019 commented on pull request #567: [FLINK-31815] Fixing the container vulnerability by upgrade the SnakeYaml Maven dependency

2023-04-19 Thread via GitHub
yangjf2019 commented on PR #567: URL: https://github.com/apache/flink-kubernetes-operator/pull/567#issuecomment-1515657414 The following exception was found in the error log and looks like a conflict with the snakeyaml package in `org.apache.flink:flink-kubernetes`.

[GitHub] [flink-kubernetes-operator] yangjf2019 commented on pull request #567: [FLINK-31815] Fixing the container vulnerability by upgrade the SnakeYaml Maven dependency

2023-04-19 Thread via GitHub
yangjf2019 commented on PR #567: URL: https://github.com/apache/flink-kubernetes-operator/pull/567#issuecomment-1515584808 Well ,thank you,maybe i should check the unit tests.But when I run the mvn command locally, I can compile the project normally.

[GitHub] [flink-kubernetes-operator] yangjf2019 commented on pull request #567: [FLINK-31815] Fixing the container vulnerability by upgrade the SnakeYaml Maven dependency

2023-04-19 Thread via GitHub
yangjf2019 commented on PR #567: URL: https://github.com/apache/flink-kubernetes-operator/pull/567#issuecomment-1514677539 Hello @mbalassi , may I ask why flink e2e tests will run for more than 5 hours? And I can't see the run log.