August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1724) Develop an alternative to 'org.wildfly.security.credential.source.OAuth2CredentialSource'

by Ashley Abdel-Sayed (Jira)

[ https://issues.redhat.com/browse/ELY-1724?page=com.atlassian.jira.plugin.... ] Ashley Abdel-Sayed commented on ELY-1724: ----------------------------------------- Since it is the last day of my internship, I am unassigning myself from this issue. > Develop an alternative to 'org.wildfly.security.credential.source.OAuth2CredentialSource' > ----------------------------------------------------------------------------------------- > > Key: ELY-1724 > URL: https://issues.redhat.com/browse/ELY-1724 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Critical > Fix For: 1.13.0.CR4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13672) Upgrade JGroups to 4.2.5.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13672?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13672: ---------------------------------- Description: Tracker for 4.2.5.Final release. Code changes [https://github.com/belaban/JGroups/compare/JGroups-4.2.4.Final...jgroups-...] Release Notes: [https://issues.redhat.com/projects/JGRP/versions/12345857] was: Tracker for 4.2.5.Final release. Code changes [https://github.com/belaban/JGroups/compare/JGroups-4.2.4.Final...jgroups-...] ...tag has not been pushed for this release, so use this link [https://github.com/belaban/JGroups/compare/JGroups-4.2.4.Final...32190c73...] Release Notes: [https://issues.redhat.com/projects/JGRP/versions/12345857] > Upgrade JGroups to 4.2.5.Final > ------------------------------ > > Key: WFLY-13672 > URL: https://issues.redhat.com/browse/WFLY-13672 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 21.0.0.Beta1 > > > Tracker for 4.2.5.Final release. > Code changes > [https://github.com/belaban/JGroups/compare/JGroups-4.2.4.Final...jgroups-...] > Release Notes: [https://issues.redhat.com/projects/JGRP/versions/12345857] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5577) Calling static Java method from DMN model (Drools Business Central)

by Kristina Mandekic (Jira)

Kristina Mandekic created DROOLS-5577: ----------------------------------------- Summary: Calling static Java method from DMN model (Drools Business Central) Key: DROOLS-5577 URL: https://issues.redhat.com/browse/DROOLS-5577 Project: Drools Issue Type: Bug Components: DMN Editor, dmn engine Affects Versions: 7.40.0.Final Reporter: Kristina Mandekic Assignee: Guilherme Gomes Attachments: Artifacts.PNG, Artifacts0.PNG, DroolsNewTypes5-0.0.1-SNAPSHOT.jar, dependencies.PNG, stdev 0.PNG, stdev 1.PNG When calling static Java method {{stdev_a}} (which I created in a new Java Maven project) from Drools Business Central DMN project/model, I'm getting following error: {code:java} DMN: Error compiling Java function 'stdev' on node 'stdev': Error resolving external function as defined by: function(val) external { java: { class: ""com.samplea.drools.DroolsNewTypes5.StandardDeviationA"", method signature: ""stdev_a(java.lang.Number)"" }} (DMN id: _3B4B6CBE-847B-4488-8754-214F506BBB48, Error compiling the referenced FEEL expression){code} Also, how to view logs of DMN model when it has build errors? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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)

Hayk Hovsepyan created SWSQE-1205: ------------------------------------- Summary: 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 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5574) User can not work with project

by Eder Ignatowicz (Jira)

[ https://issues.redhat.com/browse/DROOLS-5574?page=com.atlassian.jira.plug... ] Eder Ignatowicz reassigned DROOLS-5574: --------------------------------------- Assignee: Enrique González Martínez (was: Eder Ignatowicz) > User can not work with project > ------------------------------ > > Key: DROOLS-5574 > URL: https://issues.redhat.com/browse/DROOLS-5574 > Project: Drools > Issue Type: Bug > Components: Examples (Workbench) > Affects Versions: 7.42.0.Final > Reporter: Jozef Marko > Assignee: Enrique González Martínez > Priority: Blocker > Labels: Regression > Attachments: Screenshot from 2020-08-12 15-57-43.png, error.log > > > The issue is after user import sample project and tries to open an Asset, multiple errors appear in server log and the UI is not responsive. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2490) MPerf changes

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2490?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2490. ---------------------------- Release Notes Text: Made MPerf similar to UPerf (time-based) Resolution: Done > MPerf changes > ------------- > > Key: JGRP-2490 > URL: https://issues.redhat.com/browse/JGRP-2490 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0.2 > > > Make MPerf more similar to UPerf: > * Time based > * Better reporting > * Simplifications > * Also look at performance after the changes -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5089) FailedOperationTransformationConfig corrects only one attribute

by Tomasz Adamski (Jira)

Tomasz Adamski created WFCORE-5089: -------------------------------------- Summary: FailedOperationTransformationConfig corrects only one attribute Key: WFCORE-5089 URL: https://issues.redhat.com/browse/WFCORE-5089 Project: WildFly Core Issue Type: Feature Request Reporter: Tomasz Adamski Assignee: Tomasz Adamski FailedOperationTransformationConfig can be initialized with many attributes but during correct attempt it breaks the loop after the first attribute. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5574) User can not work with project

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5574?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-5574: ------------------------------------ Root Cause: https://issues.redhat.com/browse/JBPM-9178 > User can not work with project > ------------------------------ > > Key: DROOLS-5574 > URL: https://issues.redhat.com/browse/DROOLS-5574 > Project: Drools > Issue Type: Bug > Components: Examples (Workbench) > Affects Versions: 7.42.0.Final > Reporter: Jozef Marko > Assignee: Eder Ignatowicz > Priority: Blocker > Labels: Regression > Attachments: Screenshot from 2020-08-12 15-57-43.png, error.log > > > The issue is after user import sample project and tries to open an Asset, multiple errors appear in server log and the UI is not responsive. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4605) DMN alpha network

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4605?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4605: ----------------------------------- Issue Type: Story (was: Epic) > DMN alpha network > ----------------- > > Key: DROOLS-4605 > URL: https://issues.redhat.com/browse/DROOLS-4605 > Project: Drools > Issue Type: Story > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > > *Motivation*: a DMN decision table can be evaluated faster than naive algorithm by translating it into a Rete/Phreak, but the current kie7 approach is suffering from performance bottleneck artificially induced by use of kie7 rule units, which provide more harm than benefit to perfomance (performance is actually worst for most "realistic" cases). > *Goals*: a POC to understand what’s need to be done to support the alpha network compiler (wihout kie7 rule units) in DMN. We currently estimate it will take us 1 to 2 summer sprints and the output will be more epics to implement this feature. > *Impact*: alpha network compiler code refactors for the better use of. > One part of the POC was to hard-code the alpha network for a specific table ([DROOLS-4566]) the remained of the poc is to generalize the approach further to fully assess the impacts thanks to the poc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4605) DMN alpha network

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4605?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4605: ----------------------------------- Sprint: 2020 Week 34-36 (from Aug 17) > DMN alpha network > ----------------- > > Key: DROOLS-4605 > URL: https://issues.redhat.com/browse/DROOLS-4605 > Project: Drools > Issue Type: Story > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > > *Motivation*: a DMN decision table can be evaluated faster than naive algorithm by translating it into a Rete/Phreak, but the current kie7 approach is suffering from performance bottleneck artificially induced by use of kie7 rule units, which provide more harm than benefit to perfomance (performance is actually worst for most "realistic" cases). > *Goals*: a POC to understand what’s need to be done to support the alpha network compiler (wihout kie7 rule units) in DMN. We currently estimate it will take us 1 to 2 summer sprints and the output will be more epics to implement this feature. > *Impact*: alpha network compiler code refactors for the better use of. > One part of the POC was to hard-code the alpha network for a specific table ([DROOLS-4566]) the remained of the poc is to generalize the approach further to fully assess the impacts thanks to the poc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 August 2020