KOGITO-9849 DataIndex is not processing well the http cloud events #3240
Conversation
|
Hi @nmirasch , would you mind review this PR with the fix for http events. (I can't add you as reviewer by now) |
|
Related to: apache/incubator-kie-kogito-apps#1889 |
|
PR job Reproducerbuild-chain build full_downstream -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/pull-request-config.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u #3240 --skipParallelCheckout NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3240/2/display/redirect Test results:
Those are the test failures: org.kie.kogito.index.service.KeycloakInmemoryPostgreSqlIndexingServiceIT.testUnauthorizedUserAccessjava.lang.reflect.InvocationTargetExceptionorg.kie.kogito.index.service.KeycloakOracleIndexingServiceIT.testUnauthorizedUserAccessjava.lang.reflect.InvocationTargetExceptionorg.kie.kogito.index.service.KeycloakPostgreSqlIndexingServiceIT.testUnauthorizedUserAccessjava.lang.reflect.InvocationTargetExceptionorg.kie.kogito.jobs.service.messaging.InfinispanMessagingApiTest.cancelJobjava.lang.RuntimeException: Failed to start quarkusorg.kie.kogito.quarkus.outbox.OutboxIT.(?)org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (172.17.0.1 ports: [8083, 37100] should be listening)org.kie.kogito.springboot.outbox.OutboxIT.(?)org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (172.17.0.1 ports: [8083, 37144] should be listening)org.kie.kogito.examples.OpenVinoRestIT.testOpenvino1 expectation failed.Expected status code <201> but was <500>. org.kie.kogito.quarkus.serverless.workflow.deployment.livereload.LiveReloadProcessorTest.testOpenApijava.lang.RuntimeException: Failed to start quarkus |
- Ensures that the kogito-addons-quarkus-events-process addon produces the proper content type header when http cloud events are used.
- Ensure the data index dev services produce the proper content type header.
|
PR job Reproducerbuild-chain build full_downstream -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u #3240 --skipParallelCheckout NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution Please look here: https://ci-builds.apache.org/job/KIE/job/test/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3240/2/display/redirect Test results:
Those are the test failures: org.kie.kogito.mongodb.PersistentProcessInstancesIT.(?)Container startup failed |
…pache#3240) - Ensures that the kogito-addons-quarkus-events-process addon produces the proper content type header when http cloud events are used. - Ensure the data index dev services produce the proper content type header.
Many thanks for submitting your Pull Request ❤️!
Please make sure that your PR meets the following requirements:
KOGITO-XYZ Subject[0.9.x] KOGITO-XYZ SubjectHow to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.
How to retest this PR or trigger a specific build:
for pull request checks
Please add comment: Jenkins retest this
for a specific pull request check
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] tests
for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch
for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch
for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main
for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-main
for quarkus lts checks
Run checks against Quarkus lts branch
Please add comment: Jenkins run quarkus-lts
for a specific quarkus lts check
Run checks against Quarkus lts branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts
for native checks
Run native checks
Please add comment: Jenkins run native
for a specific native check
Run native checks
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native
for native lts checks
Run native checks against quarkus lts branch
Please add comment: Jenkins run native-lts
for a specific native lts check
Run native checks against quarkus lts branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native-lts
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>, where<branch-name>is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.xto backport the original PR to the7.67.xbranch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.
Quarkus-3 PR check is failing ... what to do ?
The Quarkus 3 check is applying patches from the `.ci/environments/quarkus-3/patches`.The first patch, called
0001_before_sh.patch, is generated from Openrewrite.ci/environments/quarkus-3/quarkus3.ymlrecipe. The patch is created to speed up the check. But it may be that some changes in the PR broke this patch.No panic, there is an easy way to regenerate it. You just need to comment on the PR:
and it should, after some minutes (~20/30min) apply a commit on the PR with the patch regenerated.
Other patches were generated manually. If any of it fails, you will need to manually update it... and push your changes.