September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5609) Cannot use as parameter of a function the result of another function receiving a parameter of its own

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5609?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5609: --------------------------------- Sprint: 2020 Week 34-36 (from Aug 17) > Cannot use as parameter of a function the result of another function receiving a parameter of its own > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-5609 > URL: https://issues.redhat.com/browse/DROOLS-5609 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.42.0.Final > Reporter: Ciprian Chiru > Assignee: Luca Molteni > Priority: Major > > Given the following rule: > > {code:java} > import java.util.*; > global java.util.Set controlSet; > global org.example.drools.service.DummyService dummyService; > rule "will execute per each Measurement having ID color" > no-loop > when > Measurement( id == "color", $colorVal : val ) > String() from dummyService.dummy(dummyService.dummy($colorVal)) > then > controlSet.add($colorVal); > end{code} > > The compilation fails with: > {code:java} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile-1) on project rules: Compilation failure > [ERROR] .../target/generated-sources/drools-model-compiler/main/java/rules/Rules38bbab4141b64289855d5e28d5f95ca6RuleMethods0.java:[24,111] no suitable method found for from(org.drools.model.Global<org.example.drools.service.DummyService>,org.drools.model.Global<org.example.drools.service.DummyService>,org.drools.model.Variable<java.lang.String>,rules.P4C.LambdaExtractor4CA52645EC5319D0363A23796D4739AE) > [ERROR] method org.drools.model.DSL.<T>from(T) is not applicable > [ERROR] (cannot infer type-variable(s) T > [ERROR] (actual and formal argument lists differ in length)) > [ERROR] method org.drools.model.DSL.<T>from(org.drools.model.Variable<T>) is not applicable > [ERROR] (cannot infer type-variable(s) T > [ERROR] (actual and formal argument lists differ in length)) > [ERROR] method org.drools.model.DSL.<T>from(org.drools.model.functions.Function0<T>) is not applicable > [ERROR] (cannot infer type-variable(s) T > [ERROR] (actual and formal argument lists differ in length)) > [ERROR] method org.drools.model.DSL.<T>from(org.drools.model.Variable<T>,org.drools.model.functions.Function1<T,?>) is not applicable > [ERROR] (cannot infer type-variable(s) T > [ERROR] (actual and formal argument lists differ in length)) > [ERROR] method org.drools.model.DSL.<A,B>from(org.drools.model.Variable<A>,org.drools.model.Variable<B>,org.drools.model.functions.Function2<A,B,?>) is not applicable > [ERROR] (cannot infer type-variable(s) A,B > [ERROR] (actual and formal argument lists differ in length)) > [ERROR] method org.drools.model.DSL.<A,B,C>from(org.drools.model.Variable<A>,org.drools.model.Variable<B>,org.drools.model.Variable<C>,org.drools.model.functions.Function3<A,B,C,?>) is not applicable > [ERROR] (cannot infer type-variable(s) A,B,C > [ERROR] (argument mismatch; rules.P4C.LambdaExtractor4CA52645EC5319D0363A23796D4739AE cannot be converted to org.drools.model.functions.Function3<A,B,C,?>)) > [ERROR] method org.drools.model.DSL.<A,B,C,D>from(org.drools.model.Variable<A>,org.drools.model.Variable<B>,org.drools.model.Variable<C>,org.drools.model.Variable<D>,org.drools.model.functions.Function4<A,B,C,D,?>) is not applicable > [ERROR] (cannot infer type-variable(s) A,B,C,D > [ERROR] (actual and formal argument lists differ in length)){code} > This error can be reproduced with version _7.43.0-SNAPSHOT_ -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5608) Cannot use method chaining as source for facts

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5608?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5608: --------------------------------- Sprint: 2020 Week 34-36 (from Aug 17) > Cannot use method chaining as source for facts > ---------------------------------------------- > > Key: DROOLS-5608 > URL: https://issues.redhat.com/browse/DROOLS-5608 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.42.0.Final > Reporter: Ciprian Chiru > Assignee: Luca Molteni > Priority: Major > > Given the sample rule below: > {code:java} > import java.util.*; > global java.util.Set controlSet; > rule "will execute per each Measurement having ID color" > no-loop > when > Measurement( id == "color", $colorVal : val ) > String() from Optional.of($colorVal).orElse("blah") > then > controlSet.add($colorVal); > end{code} > > Compiling the resulting model fails with: > {code:java} > .../target/generated-sources/drools-model-compiler/main/java/rules/Rules79f20b1c9ba841128eaf4b2dbb336819RuleMethods0.java:[24,129] cannot find symbol > [ERROR] symbol: variable $colorVal > [ERROR] location: class rules.Rules79f20b1c9ba841128eaf4b2dbb336819RuleMethods0{code} > Can be reproduced with _7.43.0-SNAPSHOT_ > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1202) UI Automations - Overview Filters Apply

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1202?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1202: ---------------------------------- Sprint: Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #44) > UI Automations - Overview Filters Apply > --------------------------------------- > > Key: SWSQE-1202 > URL: https://issues.redhat.com/browse/SWSQE-1202 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > Labels: automation > > Overview page contains Filter options. > We need to automate all filter types apply and result checking. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1205) Automate Joined Configs Section https://github.com/kiali/kiali-ui/pull/1885

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1205?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1205: ---------------------------------- Sprint: Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #44) > Automate Joined Configs Section https://github.com/kiali/kiali-ui/pull/1885 > --------------------------------------------------------------------------- > > Key: SWSQE-1205 > URL: https://issues.redhat.com/browse/SWSQE-1205 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1168) Document alternatives for PSI OpenStack

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1168?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1168: ---------------------------------- Sprint: Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44) > Document alternatives for PSI OpenStack > --------------------------------------- > > Key: SWSQE-1168 > URL: https://issues.redhat.com/browse/SWSQE-1168 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > When the PSI OpenStack is down, we need to use something else to provisioning OCP clusters. > We need to document options: > * AWS > * https://quicklab.upshift.redhat.com/clusters > * bot on coreos slack -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1143) Solve python2 vs. python3 problem on jenkins slaves

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1143?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1143: ---------------------------------- Sprint: Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44) > Solve python2 vs. python3 problem on jenkins slaves > --------------------------------------------------- > > Key: SWSQE-1143 > URL: https://issues.redhat.com/browse/SWSQE-1143 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Usage of python2 as a default python version on our jenkins slaves causes lot of troubles. It would be good to use python3 everywhere. > e.g. lot of problem2 with openstack client on python2: > /usr/lib/python2.7/site-packages/pkg_resources/py2_warn.py:21: UserWarning: Setuptools will stop working on Python 2 > ************************************************************ > You are running Setuptools on Python 2, which is no longer > supported and > >>> SETUPTOOLS WILL STOP WORKING <<< > in a subsequent release (no sooner than 2020-04-20). > Please ensure you are installing > Setuptools using pip 9.x or later or pin to `setuptools<45` > in your environment. > If you have done those things and are still encountering > this message, please follow up at > https://bit.ly/setuptools-py2-warning. > ************************************************************ > sys.version_info < (3,) and warnings.warn(pre + "*" * 60 + msg + "*" * 60) > Traceback (most recent call last): > File "/usr/bin/openstack", line 5, in <module> > from openstackclient.shell import main > File "/usr/lib/python2.7/site-packages/openstackclient/shell.py", line 24, in <module> > from osc_lib import shell > File "/usr/lib/python2.7/site-packages/osc_lib/shell.py", line 33, in <module> > from osc_lib.cli import client_config as cloud_config > File "/usr/lib/python2.7/site-packages/osc_lib/cli/client_config.py", line 18, in <module> > from openstack.config import exceptions as sdk_exceptions > File "/usr/lib/python2.7/site-packages/openstack/__init__.py", line 16, in <module> > import openstack.config > File "/usr/lib/python2.7/site-packages/openstack/config/__init__.py", line 17, in <module> > from openstack.config.loader import OpenStackConfig # noqa > File "/usr/lib/python2.7/site-packages/openstack/config/loader.py", line 33, in <module> > from openstack.config import cloud_region > File "/usr/lib/python2.7/site-packages/openstack/config/cloud_region.py", line 44, in <module> > from openstack import proxy > File "/usr/lib/python2.7/site-packages/openstack/proxy.py", line 24, in <module> > from openstack import resource > File "/usr/lib/python2.7/site-packages/openstack/resource.py", line 49, in <module> > from openstack import utils > File "/usr/lib/python2.7/site-packages/openstack/utils.py", line 13, in <module> > import queue > ImportError: No module named queue -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1208) UI Automations - Fix random failures

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1208?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1208: ---------------------------------- Sprint: Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #44) > UI Automations - Fix random failures > ------------------------------------ > > Key: SWSQE-1208 > URL: https://issues.redhat.com/browse/SWSQE-1208 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/run-kiali-ui-te... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1173) Migration to new opertor metadata format

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1173?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1173: ---------------------------------- Sprint: Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44) > Migration to new opertor metadata format > ---------------------------------------- > > Key: SWSQE-1173 > URL: https://issues.redhat.com/browse/SWSQE-1173 > Project: Kiali QE > Issue Type: Story > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Starting with OCP 4.6 the new operator metadata format will be mandatory. We need to prepare our test infra for that. > https://docs.engineering.redhat.com/display/CFC/Operators -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1077: ---------------------------------- Sprint: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39, Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44) > Kiali Test For Istio.io > ----------------------- > > Key: SWSQE-1077 > URL: https://issues.redhat.com/browse/SWSQE-1077 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: infrastructure > > The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. > Meeting with [~brian.avery] [~gbaufake]: > 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework > https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... > 2) Kiali team then to add an api test case(s) via 'curl' to validate the Istio/Kiali integration is properly functioning. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1182) DropDown - Optimization of hierarchy.

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1182?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1182: ---------------------------------- Sprint: Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45 (was: Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44) > DropDown - Optimization of hierarchy. > ------------------------------------- > > Key: SWSQE-1182 > URL: https://issues.redhat.com/browse/SWSQE-1182 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Currently there is a big hierarchy of DropDown objects. > It needs to be optimized. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2020