wenjin272 opened a new pull request, #171: URL: https://github.com/apache/flink-connector-elasticsearch/pull/171
## Purpose of the change https://issues.apache.org/jira/browse/FLINK-41461 The ES7 and ES8 tests override the Ryuk version bundled with Testcontainers 2.0.5 (0.14.0) with 0.6.0. Remove these overrides so the tests use the bundled version. The [main-branch CI failure](https://github.com/apache/flink-connector-elasticsearch/actions/runs/43178939508/job/131049883941) occurred while pulling Elasticsearch 8.19.0, with missing-lease and content-store rename errors matching [moby/moby#53321](https://github.com/moby/moby/issues/53321). Old Ryuk uses `ImagesPrune`, while [Ryuk 0.14.0 removes matching images individually](https://github.com/testcontainers/moby-ryuk/blob/0.14.0/reaper.go#L694). This avoids that prune path; the exact cleanup caller in the failed run has not been confirmed. ## Brief change log Delete the two `testcontainers.properties` files, which contain only the Ryuk 0.6.0 override. Test parallelism and automatic cleanup remain unchanged. ## Verifying this change [Full fork CI](https://github.com/wenjin272/flink-connector-elasticsearch/actions/runs/43190887844) passed on JDK 11, 17 and 21 with Docker 29.4.2, including ES7/ES8 vector-search tests, E2E tests and licensing checks. Logs confirm Ryuk 0.14.0 and no recurrence of the reported pull errors in this run. That run tested commit `a166464`; the PR commit has the same tree and only adds the JIRA reference to the commit message. ## Impact and documentation Test-only change: the Ryuk helper image now follows the version bundled with Testcontainers. No public API or connector runtime behavior changes. User documentation is not applicable. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) Generated-by: OpenAI Codex (GPT-6) -- 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]
