Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[incubator-kie-issues#1541] Add “evaluationHitIds” to the response of jitexecutor-dmn’s “/dmnresult” route #2120

Merged
merged 17 commits into from
Oct 24, 2024

Conversation

gitgabrio
Copy link
Contributor

Fixes apache/incubator-kie-issues#1541

This PR:

  1. add Set<String> evaluationHitIds field to JITDMNResult
  2. define a specific JITDMNListener that store evaluated ids
  3. add the above listener to DMNRuntime used behind /dmnresult rest endpoint
  4. add the retrieved ids to the returned JITDMNResult
How 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-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-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-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-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-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-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.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

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.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

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.yml recipe. 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:

jenkins rewrite quarkus-3

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.

Copy link
Contributor

@yesamer yesamer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @gitgabrio, your changes are fine. Just some autoformatting points

* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
* <p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* <p>
*

* with the License. You may obtain a copy of the License at
* <p>
* http://www.apache.org/licenses/LICENSE-2.0
* <p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* <p>
*

@@ -99,7 +110,8 @@ public static DMNEvaluator fromMultiple(MultipleResourcesPayload payload) {
}
}
if (mainModel == null) {
throw new IllegalStateException("Was not able to identify main model from MultipleResourcesPayload contents.");
throw new IllegalStateException("Was not able to identify main model from MultipleResourcesPayload " +
"contents.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gitgabrio autoformatting? :D

Copy link
Contributor

@jomarko jomarko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gitgabrio I put some comments to code, I didn't checked added tests for now, will do later, probably once we figure out if it is possible to hit single rule multiple times in single evaluation. See the private discussion with @ljmotta

import java.util.Map;
import java.util.Optional;
import java.util.Set;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is maybe unused now?

.findFirst()
.map(JITDMNListener.class::cast)
.map(JITDMNListener::getEvaluationHitIds);
return new JITDMNResult(getNamespace(), getName(), dmnResult, evaluationHitIds.orElse(Collections.emptySet()));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

emptyList

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for spotting!

@kie-ci3
Copy link
Contributor

kie-ci3 commented Oct 21, 2024

PR job #4 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer

build-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-apps -u #2120 --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-apps-pr/job/PR-2120/4/display/redirect

Test results:

  • PASSED: 1648
  • FAILED: 2

Those are the test failures:

PR check / Build projects / org.kie.kogito.it.jobs.WorkflowTimeoutsIT.workflowTimeoutExceeded java.lang.IllegalStateException: Unable to determine the status of the running process. See the above logs for details
org.kie.kogito.jobs.service.resource.KeycloakPostgreSqlJobResourceTest.(?) java.lang.RuntimeException: Unable to start Quarkus test resource class org.kie.kogito.testcontainers.quarkus.PostgreSqlQuarkusTestResource

jomarko added a commit to jomarko/drools that referenced this pull request Oct 22, 2024
This PR is related to: apache/incubator-kie-kogito-apps#2120 where we are adding new unit tests using DMN models from the drools/kie-dmn/kie-dmn-test-resources
- test DMN model where a decision table is nested under conditional expression
- test DMN model where collection data type is used as input and output
gitgabrio pushed a commit to apache/incubator-kie-drools that referenced this pull request Oct 23, 2024
* kie-issues#1541: Add testing models into kie-dmn-test-resources

This PR is related to: apache/incubator-kie-kogito-apps#2120 where we are adding new unit tests using DMN models from the drools/kie-dmn/kie-dmn-test-resources

* Collections.dmn -> MultipleHitRules.dmn

* Remove <output/> name attribute
Copy link
Contributor

@jomarko jomarko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @gitgabrio

@gitgabrio
Copy link
Contributor Author

kogito-apps failure unrelated

Failed to execute goal com.google.cloud.tools:jib-maven-plugin:2.8.0:dockerBuild (default) on project integration-tests-trusty-service-springboot: Unknown mediaType: application/vnd.oci.image.index.v1+json

@kie-ci3
Copy link
Contributor

kie-ci3 commented Oct 23, 2024

PR job #7 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer

build-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-apps -u #2120 --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-apps-pr/job/PR-2120/7/display/redirect

Test results:

  • PASSED: 1662
  • FAILED: 1

Those are the test failures:

org.kie.kogito.explainability.messaging.ExplainabilityMessagingHandlerCounterfactualsIT.explainabilityRequestIsProcessedAndAnIntermediateMessageIsSent
Wanted but not invoked:
explanationServiceImpl.explainAsync(
,

);
-> at org.kie.kogito.explainability.messaging.BaseExplainabilityMessagingHandlerIT.explainabilityRequestIsProcessedAndAnIntermediateMessageIsSent(BaseExplainabilityMessagingHandlerIT.java:140)
Actually, there were zero interactions with this mock.

@kie-ci3
Copy link
Contributor

kie-ci3 commented Oct 23, 2024

PR job #9 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer

build-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-apps -u #2120 --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-apps-pr/job/PR-2120/9/display/redirect

Test results:

  • PASSED: 1677
  • FAILED: 7

Those are the test failures:

org.kie.kogito.index.postgresql.ProcessDataIndexPostgreSqlHttpIT.testProcessInstanceEvents java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to start Quarkus test resource class org.kie.kogito.index.test.quarkus.http.DataIndexPostgreSqlHttpQuarkusTestResource
org.kie.kogito.index.postgresql.ProcessDataIndexPostgreSqlKafkaIT.testProcessInstanceEvents java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to start Quarkus test resource class org.kie.kogito.index.test.quarkus.kafka.DataIndexPostgreSqlQuarkusKafkaTestResource
org.kie.kogito.index.ProcessDataIndexMongoDBIT.testProcessInstanceEvents Cannot invoke method size() on null object
org.kie.kogito.index.ProcessDataIndexPostgreSqlIT.testProcessInstanceEvents Failed to load ApplicationContext for [WebMergedContextConfiguration@50e3019b testClass = org.kie.kogito.index.ProcessDataIndexPostgreSqlIT, locations = [], classes = [org.kie.kogito.KogitoApplication], contextInitializerClasses = [org.kie.kogito.index.spring.KogitoServiceRandomPortSpringTestResource, org.kie.kogito.index.spring.DataIndexPostgreSqlSpringTestResource], activeProfiles = [], propertySourceDescriptors = [], propertySourceProperties = ["org.springframework.boot.test.context.SpringBootTestContextBootstrapper=true", "server.port=0"], contextCustomizers = [org.springframework.boot.test.context.filter.ExcludeFilterContextCustomizer@6f1c29b7, org.springframework.boot.test.json.DuplicateJsonObjectContextCustomizerFactory$DuplicateJsonObjectContextCustomizer@2a7ed1f, org.springframework.boot.test.mock.mockito.MockitoContextCustomizer@0, org.springframework.boot.test.web.client.TestRestTemplateContextCustomizer@5456afaa, org.springframework.boot.test.autoconfigure.actuate.observability.ObservabilityContextCustomizerFactory$DisableObservabilityContextCustomizer@1f, org.springframework.boot.test.autoconfigure.properties.PropertyMappingContextCustomizer@0, org.springframework.boot.test.autoconfigure.web.servlet.WebDriverContextCustomizer@1787bc24, org.springframework.boot.test.context.SpringBootTestAnnotation@bf04646b], resourceBasePath = "src/main/webapp", contextLoader = org.springframework.boot.test.context.SpringBootContextLoader, parent = null]
PR check / Build projects / org.kie.kogito.it.jobs.ProcessTimerIT.testDeleteTimerCycle java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to start Quarkus test resource class org.kie.kogito.test.resources.JobServiceCompositeQuarkusTestResource
PR check / Build projects / org.kie.kogito.addons.quarkus.data.index.it.PostgreSQLQuarkusAddonDataIndexPersistenceIT.testDataIndexAddon java.util.concurrent.CompletionException: java.lang.RuntimeException: Unable to start Quarkus test resource class org.kie.kogito.index.test.quarkus.http.DataIndexPostgreSqlHttpQuarkusTestResource
PR check / Build projects / org.kie.kogito.addons.quarkus.data.index.it.PostgreSQLQuarkusAddonDataIndexPersistenceIT.testDataIndexAddon java.lang.RuntimeException: Unable to start Quarkus test resource class org.kie.kogito.index.test.quarkus.http.DataIndexPostgreSqlHttpQuarkusTestResource

@gitgabrio
Copy link
Contributor Author

jenkins failure unrelated

Caused by: com.google.api.client.http.HttpResponseException: 502 Bad Gateway

@gitgabrio gitgabrio merged commit 7b582c8 into apache:main Oct 24, 2024
4 of 5 checks passed
@gitgabrio gitgabrio deleted the incubator-kie-issues#1541 branch October 24, 2024 08:28
rgdoliveira pushed a commit to rgdoliveira/drools that referenced this pull request Oct 24, 2024
…he#6135)

* kie-issues#1541: Add testing models into kie-dmn-test-resources

This PR is related to: apache/incubator-kie-kogito-apps#2120 where we are adding new unit tests using DMN models from the drools/kie-dmn/kie-dmn-test-resources

* Collections.dmn -> MultipleHitRules.dmn

* Remove <output/> name attribute
rgdoliveira pushed a commit to rgdoliveira/kogito-apps that referenced this pull request Oct 24, 2024
… jitexecutor-dmn’s “/dmnresult” route (apache#2120)

* exp_dmn_result_mapped_to_input

* [exp_dmn_result_mapped_to_input] WIP

* [incubator-kie-issues#1541] WIP

* [incubator-kie-issues#1541] Implemented retrieval and population of "evaluationHitIds" field

* [incubator-kie-issues#1541] Fixed tests. Minor refactoring

* [incubator-kie-issues#1541] Fix formatting

* [incubator-kie-issues#1541] Fix as per suggestion

* [incubator-kie-issues#1541] Fix as per suggestion

* kie-issues#1541: Extend test coverage

- test DMN model where a decision table is nested under conditional expression
- test DMN model where collection data type is used as input and output

* Collections -> MultipleHitRules

* [incubator-kie-issues#1541] Remove duplicated test

* [incubator-kie-issues#1541] Fix imports

---------

Co-authored-by: Gabriele-Cardosi <[email protected]>
Co-authored-by: Jozef Marko <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add “evaluationHitIds” to the response of jitexecutor-dmn’s “/dmnresult” route
5 participants