April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3614) [DMN Designer] Maximize Event brings palette to expression editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3614?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-3614: -------------------------------- Affects Version/s: 7.36.0.Final > [DMN Designer] Maximize Event brings palette to expression editor > ----------------------------------------------------------------- > > Key: DROOLS-3614 > URL: https://issues.redhat.com/browse/DROOLS-3614 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final, 7.36.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-02-07 16-06-01.png > > > If the expression editor is maximized, there appears the palette, that should be shown just for diagram editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2657) [DMN Designer] Select Box for Decision Table input columns

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-2657?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-2657. ------------------------------- Fix Version/s: 7.36.0.Final Resolution: Won't Do No input for ~2 years. Reported internally. If customer requires can report with proper description/versions. > [DMN Designer] Select Box for Decision Table input columns > ---------------------------------------------------------- > > Key: DROOLS-2657 > URL: https://issues.redhat.com/browse/DROOLS-2657 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Fix For: 7.36.0.Final > > > Currently the decision table input columns can be named with any name. However their names should correspond to InputData elements in the DRG, thus we should provide select box for each decision table input column, where user would select corresponding InputData element for the given decision table input column. > h3. Acceptance test > # Sorting in select box > # Rename InputData, change reflected in select box > # Same InputData connected to multiple nodes, appropriate select boxes contain the value -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3317) Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3317?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-3317. ------------------------------- Fix Version/s: 7.36.0.Final Resolution: Cannot Reproduce Tried to construct rule with setting boolean on right site. No validation/build error thrown. > Guided Decision Tables: Insert in RHS not creating valid code for boolean fields. > --------------------------------------------------------------------------------- > > Key: DROOLS-3317 > URL: https://issues.redhat.com/browse/DROOLS-3317 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.15.0.Final > Reporter: Toni Rikkola > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Fix For: 7.36.0.Final > > > Insert a fact with a boolean field in dtable RHS. > The DRL generated looks like this: > {code:java} > rule "Row 3 The Table" > dialect "mvel" > when > s : Source( age >= 18 , kitten == "Dog" ) > then > s.setRisk( "ok" ); > DroolsUtil fact0 = new DroolsUtil(); > fact0.setARuleFired( true ); > insert( fact0 ); > end > {code} > The line > {code:java} > fact0.setARuleFired( true ); > {code} > does not compile. It should be ( for example ): > {code:java} > fact0.aRuleFired = true; > {code} > The above is done by inserting the fact with BRL action, but the same error bothers the "Set the value of field" option. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2464) Getting OutOfMemory Error

by Bhavesh Kharwa (Jira)

Bhavesh Kharwa created JGRP-2464: ------------------------------------ Summary: Getting OutOfMemory Error Key: JGRP-2464 URL: https://issues.redhat.com/browse/JGRP-2464 Project: JGroups Issue Type: Bug Affects Versions: 3.6.13 Reporter: Bhavesh Kharwa Assignee: Bela Ban Attachments: oom-jgroup.jpg I am using artemis version 2.11.0 and run artemis in master slave. There are two master and each master having slave. Please find attached screenshot of OutOfMemory error. I have tried to reproduce this issue but not able to reproduce it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1099) Automate labels https://github.com/kiali/kiali-ui/pull/1686

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1099?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1099: ---------------------------------- Sprint: Kiali Sprint #38 > Automate labels https://github.com/kiali/kiali-ui/pull/1686 > ----------------------------------------------------------- > > Key: SWSQE-1099 > URL: https://issues.redhat.com/browse/SWSQE-1099 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2403) Dump information in panic scenarios

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2403?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2403: --------------------------- Description: When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. The question is *when* do we do this? If the pool fluctuates between almost-full and full, we can't obviously take a thread dump every time! was: When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. > Dump information in panic scenarios > ----------------------------------- > > Key: JGRP-2403 > URL: https://issues.redhat.com/browse/JGRP-2403 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.2, 5.0.0.Alpha4 > > > When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. > The question is *when* do we do this? If the pool fluctuates between almost-full and full, we can't obviously take a thread dump every time! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5220) Make @watch annotation to also work with oopath

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5220: ----------------------------------- Summary: Make @watch annotation to also work with oopath Key: DROOLS-5220 URL: https://issues.redhat.com/browse/DROOLS-5220 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco Property reactivity is currently working on oopath as demostrated by this test case: {code} @Test public void testPropertyReactivityWithOOPath() { String str = "import " + Person.class.getCanonicalName() + ";" + "import " + AdultUnit.class.getCanonicalName() + "\n" + "rule Adult @Unit( AdultUnit.class ) when\n" + " $p : /persons[name == \"Mario\"]\n" + "then\n" + " modify($p) { setAge($p.getAge()+1) };\n" + "end\n"; KieContainer kieContainer = getKieContainer( null, str ); RuleUnitExecutor executor = RuleUnitExecutor.newRuleUnitExecutor( kieContainer ); Person mario = new Person( "Mario", 45 ); Person sofia = new Person( "Sofia", 8 ); DataSource<Person> persons = DataSource.create( mario, sofia ); AdultUnit unit = new AdultUnit(persons); assertEquals(1, executor.run( unit ) ); assertEquals(46, mario.getAge() ); } {code} Conversely what it is not working (it doesn't compile at all) is the use of the @watch annotation like in {code} @Test public void testPropertyReactivityWithOOPathAndWatch() { String str = "import " + Person.class.getCanonicalName() + ";" + "import " + AdultUnit.class.getCanonicalName() + "\n" + "rule Adult @Unit( AdultUnit.class ) when\n" + " $p : /persons[$age : age, name == \"Mario\"] @watch( !age )\n" + "then\n" + " modify($p) { setAge($age+1) };\n" + "end\n"; KieContainer kieContainer = getKieContainer( null, str ); RuleUnitExecutor executor = RuleUnitExecutor.newRuleUnitExecutor( kieContainer ); Person mario = new Person( "Mario", 45 ); Person sofia = new Person( "Sofia", 8 ); DataSource<Person> persons = DataSource.create( mario, sofia ); AdultUnit unit = new AdultUnit(persons); assertEquals(1, executor.run( unit ) ); assertEquals(46, mario.getAge() ); } {code} Of course this can work only on a one-level oopath. It has to be decided what to do (trigger a compile time error?) when trying to use that annotation on a oopath made of 2 or more chunks. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1111) UI job - Swagger Version Always 'master'

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1111?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1111. ---------------------------------- Resolution: Done Swagger.json is taken based on KIALI_REVISION_OR_BRANCH Main pipelines are setting it according to CORE_BRANCH parameter so it will not work for PR pipelines, but it's possible to run tests manually and set KIALI_REVISION_OR_BRANCH for given commit in the PR. > UI job - Swagger Version Always 'master' > ---------------------------------------- > > Key: SWSQE-1111 > URL: https://issues.redhat.com/browse/SWSQE-1111 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > UI tests are not getting correct swagger version - https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1110) E2E job - Swagger Version Always 'master'

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1110?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1110. ---------------------------------- Resolution: Done Swagger.json is taken based on KIALI_REVISION_SHA1 Main pipeline are setting it according to CORE_BRANCH parameter so it will not work for PR pipelines, but it's possible to run tests manually and set KIALI_REVISION_SHA1 for given commit in the PR. > E2E job - Swagger Version Always 'master' > ----------------------------------------- > > Key: SWSQE-1110 > URL: https://issues.redhat.com/browse/SWSQE-1110 > Project: Kiali QE > Issue Type: Bug > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Issue is that the swagger json is always 'master'. > prepare-e2e-tests-env.sh needs to set the swagger file version/path appropriately based on KIALI_REVISION_SHA1 > https://github.com/kiali/kiali/blob/master/tests/e2e/config/env.yaml#L10 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1107) Update prepare-e2e-tests-env.sh and prepare-ui-tests-env.sh to be less verbose

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1107?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1107. ---------------------------------- Resolution: Done > Update prepare-e2e-tests-env.sh and prepare-ui-tests-env.sh to be less verbose > ------------------------------------------------------------------------------ > > Key: SWSQE-1107 > URL: https://issues.redhat.com/browse/SWSQE-1107 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > It produces very long output containing lot of: > Cloning into '/home/jenkins/agent/workspace/run-kiali-e2e-tests/kiali'... > Checking out files: 42% (3633/8645) > Checking out files: 43% (3718/8645) > Checking out files: 44% (3804/8645) > Checking out files: 45% (3891/8645) > Checking out files: 46% (3977/8645) > Checking out files: 47% (4064/8645) > Checking out files: 48% (4150/8645) > From https://github.com/kiali/kiali > * [new ref] refs/pull/1/head -> origin/pr/1/head > * [new ref] refs/pull/1/merge -> origin/pr/1/merge > * [new ref] refs/pull/10/head -> origin/pr/10/head > * [new ref] refs/pull/10/merge -> origin/pr/10/merge > * [new ref] refs/pull/100/head -> origin/pr/100/head > * [new ref] refs/pull/1000/head -> origin/pr/1000/head > * [new ref] refs/pull/1001/head -> origin/pr/1001/head > * [new ref] refs/pull/1002/head -> origin/pr/1002/head > * [new ref] refs/pull/1003/head -> origin/pr/1003/head > * [new ref] refs/pull/1004/head -> origin/pr/1004/head > * [new ref] refs/pull/1005/head -> origin/pr/1005/head > * [new ref] refs/pull/1009/head -> origin/pr/1009/head > * [new ref] refs/pull/101/head -> origin/pr/101/head > * [new ref] refs/pull/1010/head -> origin/pr/1010/head > * [new ref] refs/pull/1011/head -> origin/pr/1011/head > * [new ref] refs/pull/1012/head -> origin/pr/1012/head > * [new ref] refs/pull/1013/head -> origin/pr/1013/head > * [new ref] refs/pull/1014/head -> origin/pr/1014/head > * [new ref] refs/pull/1015/head -> origin/pr/1015/head > * [new ref] refs/pull/1016/head -> origin/pr/1016/head -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2020