oscerd commented on PR #2987: URL: https://github.com/apache/camel-kamelets/pull/2987#issuecomment-5448639462
## Correction, and this PR is more urgent than I said In my previous comment I described `mail-sink-pipe-test` as a regression that the stale catalog had been **hiding**, surfaced by this branch. That is not accurate, and the real picture matters for scheduling this PR. **`main` is currently red, and has been since 24 Aug.** The last four `Integration Tests` runs on `main`: ``` 2026-08-25T14:35:59Z failure 2015bcf8 2026-08-25T09:52:53Z failure d6ad23f9 2026-08-25T06:39:29Z failure 957fd47d 2026-08-24T17:00:37Z failure 3969f06e ``` and the failure there is the same one, with the same shape: ``` TEST FAILED: mail-sink-pipe-test PASSED: 61 (98.4%) FAILED: 1 (1.6%) ``` The first failure follows `ff0ac602b` (#2968, `mail-sink` to `smtps`) merging on 24 Aug. So the breakage was never hidden - it went red on `main` immediately and stayed red. ## What the gap actually hides Refining the #2984 diagnosis rather than retracting it. The evidence together: - integration dumps load Kamelets from `classpath:kamelets/...`, i.e. out of a resolved `camel-kamelets` artifact, not the working tree - a change that exists **only on a PR branch** is invisible - #2978's `CamelKafkaOverrideTopic` strip provably breaks `kafka-router-pipe-test`, yet that test reported success on its head - a change **merged to `main`** *is* visible - #2968 turned `main` red the same day So the catalog under test tracks `main`'s published snapshot rather than the build produced in the same run. The blind spot is precisely PR-level changes: every PR is tested against a catalog that does not contain it, and defects only become visible after merge, on `main`, where they are most expensive. That is still exactly what this PR fixes, and it is why `--local-kamelet-dir` is the right lever - it removes artifact resolution from the question entirely. ## Practical consequence Every open PR is currently red through no fault of its own - #2988, #2989 and #2990 all fail on `mail-sink-pipe-test` alone, 61/62 passing. This branch is the only green one, because it carries the one-line test fix. Merging this unblocks `main` and every open PR at once. If it would be preferable to land the `mail-sink-pipe.yaml` pin as its own tiny PR first and rebase this one behind it, say the word and I will split it - I did not want to fragment the change without asking. --- _Claude Code on behalf of Andrea Cosentino_ -- 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]
