Croway opened a new pull request, #30080: URL: https://github.com/apache/camel/pull/30080
Backport of #30006 to camel-4.18.x. Cherry-pick (`git cherry-pick -x`) of 12666b7136d4 (CAMEL-26977: camel-file - idempotent=true or noop=true with an idempotent read lock consumes the file). The bug dates from Camel 4.7, so this branch has it too: with `idempotent=true` (or `noop=true`) and an idempotent read lock, the consumer adds the key to the repository eagerly, so the read lock refuses the file on every poll. Adjustments: - The hunk of `camel-4x-upgrade-guide-4_24.adoc` is left out: that guide is not on this branch (it was the only conflict). The 4.18.6 upgrade note comes with #30047 on main. - The `Co-Authored-By` trailer of the main commit is not carried over. `GenericFileEndpoint` and `FileIdempotentReadLockIdempotentConsumerTest` apply unchanged. Tests, on camel-4.18.x with JDK 25 (`mvnd test -pl core/camel-core -am -Dtest=FileIdempotentReadLockIdempotentConsumerTest`): 4 tests pass. `idempotentConsumesTheFileOnce` passed at its second run (surefire reruns), as it can on main: the move of the first file to `.camel` happens when the exchange completes and can take the second file. The test fix is in #30047, and comes with its backport. _Claude Code on behalf of Federico Mariani_ -- 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]
