[JBoss JIRA] (DROOLS-2543) "?" doesn't work with multi-conditions in decision table
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2543?page=com.atlassian.jira.plugi... ]
Tibor Zimányi updated DROOLS-2543:
----------------------------------
Description:
When having multivalue cell in DMN decision table with this values: "? > 10, 90", FEEL compilation fails with the following output [1]. This multivalue works when it is closed in brackets like this: "(? > 10), 90" or when the condition order is switched like this: "90, ? > 10".
Reproducer can be found here [2].
[1] https://gist.github.com/baldimir/d6f51198696e4f2b84d3eb0aaf2a9815
[2] https://github.com/kiegroup/drools/pull/1898/files#diff-388002c5a2500f2ec...
was:
When having multivalue cell in DMN decision table with this values: "? > 10, 90", FEEL compilation fails with the following output [1]. This multivalue works when it is closed in brackets like this: "(? > 10), 90" or when the condition order is switched like this: "90, ? > 10". I will provide a PR with a reproducer.
[1] https://gist.github.com/baldimir/d6f51198696e4f2b84d3eb0aaf2a9815
> "?" doesn't work with multi-conditions in decision table
> --------------------------------------------------------
>
> Key: DROOLS-2543
> URL: https://issues.jboss.org/browse/DROOLS-2543
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.7.0.Final
> Reporter: Tibor Zimányi
> Assignee: Edson Tirelli
>
> When having multivalue cell in DMN decision table with this values: "? > 10, 90", FEEL compilation fails with the following output [1]. This multivalue works when it is closed in brackets like this: "(? > 10), 90" or when the condition order is switched like this: "90, ? > 10".
> Reproducer can be found here [2].
> [1] https://gist.github.com/baldimir/d6f51198696e4f2b84d3eb0aaf2a9815
> [2] https://github.com/kiegroup/drools/pull/1898/files#diff-388002c5a2500f2ec...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3786) ManagementAuthenticationUsersTestCase fails on latest JDKs
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3786?page=com.atlassian.jira.plugi... ]
Richard Opalka edited comment on WFCORE-3786 at 5/14/18 6:02 AM:
-----------------------------------------------------------------
This issue is still present - using latest WFCORE build (commit 3e99c36df7f917d9d7e06088c9dca02521441929)
was (Author: ropalka):
This issue is still present
> ManagementAuthenticationUsersTestCase fails on latest JDKs
> ----------------------------------------------------------
>
> Key: WFCORE-3786
> URL: https://issues.jboss.org/browse/WFCORE-3786
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Richard Opalka
> Assignee: Darran Lofthouse
> Fix For: 5.0.0.Beta2
>
>
> I downloaded both jdk1.8.0_b171 & jdk1.8.0_b172.
> When running whole WFCORE test suite on them
> I'm getting InvalidUserStore exception in
> ManagementAuthenticationUsersTestCase
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (SWSQE-200) B12 OpenShift Cluster is flaky
by Kevin Earls (JIRA)
[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ]
Kevin Earls commented on SWSQE-200:
-----------------------------------
Hi [~gbaufake] . This is much better. I can now run the Flaky job repeatedly, and have been able to run the standalone performance test with both Cassandra and ElasticSearch.
There are a couple of minor issues remaining:
-- I was not able to get a persistent Jenkins instance running in the "jeager-test" project, so for expedience sake I created jaeger-test2 and created an ephemeral jenkins. I tried to delete jaeger-test, but it's still around, so you might be able to find some clues there on why that's failing.
-- I still have to increase the memory for ElasticSearch to 1G even though it runs elsewhere fine with 512M.
I can open new JIRAs for these if you'd like, or we can leave this open but lower the priority.
> B12 OpenShift Cluster is flaky
> ------------------------------
>
> Key: SWSQE-200
> URL: https://issues.jboss.org/browse/SWSQE-200
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
> Priority: Blocker
>
> I'm opening this mostly as a placeholder, and will update it as I get more information on the problems I've been experiencing. Since I've been using B12 I've been experiencing more frequent failures than on other clusters, including minishift on my laptop and the CNCF CI Jenkins. Here are a couple of instances:
> 1. Deploying ElasticSearch along with the Jaeger Production templates requires allocating 2G or memory, even though the default 512M works fine elsewhere. This can be seen in the Jaeger Standalone Performance tests job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/J... . If you run the job without changing the ES_MEMORY parameter to 2Gi it will fail.
> 2. I have a set of smoke tests for Red Hat productized artifacts for the Jaeger Java client which are run using the Jaeger all-in-one template. It's fairly simple, but on B12 deployment of the Jaeger all-in-one images fails on every other build. I've made a copy of the job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/F... and its history should be clear.
> So far I have not been able to get any useful information about why this is failing. In the OpenShift console it looks like Jaeger has started correctly. There are no errors in the logs, nor any to be found under monitoring. But if you click on the Jaeger link, you get the message "Application is not available . The application is currently not serving requests at this endpoint. It may not have been started or is still starting."
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months