claudio4j commented on PR #3373:
URL: https://github.com/apache/camel-k/pull/3373#issuecomment-1225775067
I see all of the failing CI tests are timeouts.
--
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
claudio4j commented on PR #3373:
URL: https://github.com/apache/camel-k/pull/3373#issuecomment-1224268133
> @claudio4j can we rebase this please?
rebased.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
claudio4j commented on PR #3373:
URL: https://github.com/apache/camel-k/pull/3373#issuecomment-1164413704
> @claudio4j will users of the component be able to listen for all events on
a broker with this fix, too? At the moment users need to filter for a given
event type and can not listen fo
claudio4j commented on PR #3373:
URL: https://github.com/apache/camel-k/pull/3373#issuecomment-1161846661
> some e2e tests failed. is this because the fixed Camel component is not
part of Camel K yet?
Yes, we should wait the release train of camel artifacts.
--
This is an automated
claudio4j commented on PR #3373:
URL: https://github.com/apache/camel-k/pull/3373#issuecomment-1159523638
@christophd @squakez for review.
--
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 spe
