February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1067) Automate 3Scale Config

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1067?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1067. ----------------------------------- Resolution: Done > Automate 3Scale Config > ---------------------- > > Key: SWSQE-1067 > URL: https://issues.redhat.com/browse/SWSQE-1067 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > The UI of 3Scale Handler integration is changed. > Automation needs to be adjusted. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3648) [DMN Designer] Boxed expressions - Decision Table - Allow Literal Expressions in the Decision Table header

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3648?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-3648: ---------------------------------------- When the change to trim {{Name}} values is applied the _Input Expression_ for {{InputClause}} columns continues to function like a {{Name}} and its value is therefore trimmed (and possibly white-space [normalised|https://issues.redhat.com/browse/DROOLS-5062?focusedCommentId=...]: "Finally bonus point for normalizing spaces such as...)" > [DMN Designer] Boxed expressions - Decision Table - Allow Literal Expressions in the Decision Table header > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3648 > URL: https://issues.redhat.com/browse/DROOLS-3648 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: DROOLS-3648.png > > > Currently, when users click on "Input Clauses", the popover show "Name", however, the expected label is "Expression". > !DROOLS-3648.png|thumbnail! > ⚠️ Before starting this task, check with if only changing the label is enough. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1067) Automate 3Scale Config

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1067?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1067: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/250 > Automate 3Scale Config > ---------------------- > > Key: SWSQE-1067 > URL: https://issues.redhat.com/browse/SWSQE-1067 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > The UI of 3Scale Handler integration is changed. > Automation needs to be adjusted. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13106) Extract microprofile-metrics galleon layer from observability

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-13106: --------------------------------- Summary: Extract microprofile-metrics galleon layer from observability Key: WFLY-13106 URL: https://issues.redhat.com/browse/WFLY-13106 Project: WildFly Issue Type: Task Components: MP Metrics Reporter: Ingo Weiss Assignee: Radoslav Husar Fix For: 19.0.0.Beta1 Similar to WFLY-12759: {quote}Some microprofile extensions only depend on microprofile-config and not health or metrics. Splitting this into a separate layer will accommodate layers for other microprofile specs.{quote} The fault tolerance unfortunately requires config and metrics, but not health. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3648) [DMN Designer] Boxed expressions - Decision Table - Allow Literal Expressions in the Decision Table header

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3648?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3648: -------------------------------------- Story Points: 5 Sprint: 2020 Week 07-09 (from Feb 10) Assignee: Michael Anstis (was: Guilherme Gomes) > [DMN Designer] Boxed expressions - Decision Table - Allow Literal Expressions in the Decision Table header > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3648 > URL: https://issues.redhat.com/browse/DROOLS-3648 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: DROOLS-3648.png > > > Currently, when users click on "Input Clauses", the popover show "Name", however, the expected label is "Expression". > !DROOLS-3648.png|thumbnail! > ⚠️ Before starting this task, check with if only changing the label is enough. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13105) Move base layers to the full galleon feature pack

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-13105: --------------------------------- Summary: Move base layers to the full galleon feature pack Key: WFLY-13105 URL: https://issues.redhat.com/browse/WFLY-13105 Project: WildFly Issue Type: Feature Request Components: Build System, Clustering Reporter: Ingo Weiss Assignee: Jean Francois Denise Fix For: 19.0.0.Beta1 Move the web-clustering, cloud-server, jaxrs-server and datasources-web-server layers from https://github.com/wildfly/wildfly/tree/master/testsuite/test-feature-pac... to the galleon-pack module so non-test users can use it. It got put in test-feature-pack because it came in late for WF 18. [~jdenise] you said this needed some form of adjustment, which is why I assigned this to you. [~pferraro] FYI. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2317) FEEL Syntax error on function(bkm) containing `for` keyword

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-2317?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-2317: ---------------------------------------- Glad that helped [~lukasz.hanik], don't hesitate to get in touch for any other bug report (here on JIRA) or on the other channels if more general requests! > FEEL Syntax error on function(bkm) containing `for` keyword > ----------------------------------------------------------- > > Key: DROOLS-2317 > URL: https://issues.redhat.com/browse/DROOLS-2317 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Fedor Gavrilov > Priority: Major > Attachments: DROOLS-2317.dmn, Dynamic composition.dmn, screenshot-1.png, screenshot-2.png, screenshot-3.png > > > Attached model > {code:java} > Error compiling FEEL expression 'for item in Order.items return Federal Tax for Item( item )' for name 'Calculate Federal Taxes' on node 'Calculate Federal Taxes': syntax error near 'for' > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2452) UFC_NB/MFC_NB: blocks

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2452?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2452: -------------------------------- Investigate (also for *UFC* and *MFC*!): when A blocks on credits from B, and B is removed from the membership (or A stops) -> make sure A stops blocking. > UFC_NB/MFC_NB: blocks > --------------------- > > Key: JGRP-2452 > URL: https://issues.redhat.com/browse/JGRP-2452 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0, 4.2.0 > > > Despite having full credits and {{queuing==false}}, we have a sender thread blocking (see below). > This can happen when a thread is queueing; when we stop the member, or a new view is installed, {{queueing}} is never set to false and the thread is never unblocked! > {noformat} > "jgroups-830,ma267mlvjdg021" #1394 prio=5 os_prio=0 tid=0x0000000004442000 nid=0x307c waiting on condition [0x00007fbda44be000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000005f2189da0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at org.jgroups.util.SizeBoundedQueue.add(SizeBoundedQueue.java:51) > at org.jgroups.util.NonBlockingCredit.addToQueue(NonBlockingCredit.java:98) > at org.jgroups.util.NonBlockingCredit.decrementIfEnoughCredits(NonBlockingCredit.java:58) > at org.jgroups.protocols.UFC_NB.handleDownMessage(UFC_NB.java:87) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:315) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:309) > at org.jgroups.protocols.FRAG3.down(FRAG3.java:145) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:914) > at org.jgroups.JChannel.down(JChannel.java:677) > at org.jgroups.JChannel.send(JChannel.java:516) > at org.jgroups.protocols.relay.Route.send(Route.java:42) > at org.jgroups.protocols.relay.RELAY2.route(RELAY2.java:572) > at org.jgroups.protocols.relay.RELAY2.down(RELAY2.java:425) > at org.jgroups.stack.Protocol.down(Protocol.java:317) > at org.jgroups.fork.ForkProtocol.down(ForkProtocol.java:42) > at org.jgroups.fork.ForkProtocolStack.down(ForkProtocolStack.java:62) > at org.jgroups.fork.ForkChannel.send(ForkChannel.java:222) > at org.jgroups.fork.ForkChannel.send(ForkChannel.java:21) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.send(JGroupsTransport.java:1041) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.sendCommand(JGroupsTransport.java:998) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.backupRemotely(JGroupsTransport.java:329) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeXSite(RpcManagerImpl.java:414) > at org.infinispan.xsite.BackupSenderImpl.backupCommand(BackupSenderImpl.java:250) > at org.infinispan.xsite.BackupSenderImpl.backupWrite(BackupSenderImpl.java:201) > at org.infinispan.interceptors.xsite.NonTransactionalBackupInterceptor.handleSingleKeyWriteReturn(NonTransactionalBackupInterceptor.java:144) > at org.infinispan.interceptors.xsite.NonTransactionalBackupInterceptor$$Lambda$655/1680487200.accept(Unknown Source) > at org.infinispan.interceptors.InvocationSuccessAction.apply(InvocationSuccessAction.java:22) > at org.infinispan.interceptors.impl.QueueAsyncInvocationStage.invokeQueuedHandlers(QueueAsyncInvocationStage.java:118) > at org.infinispan.interceptors.impl.QueueAsyncInvocationStage.accept(QueueAsyncInvocationStage.java:81) > at org.infinispan.interceptors.impl.QueueAsyncInvocationStage.accept(QueueAsyncInvocationStage.java:30) > at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) > at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) > at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) > at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962) > at org.infinispan.remoting.transport.AbstractRequest.complete(AbstractRequest.java:67) > at org.infinispan.remoting.transport.impl.MultiTargetRequest.onResponse(MultiTargetRequest.java:102) > at org.infinispan.remoting.transport.impl.RequestRepository.addResponse(RequestRepository.java:52) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.processResponse(JGroupsTransport.java:1361) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.processMessage(JGroupsTransport.java:1264) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.access$300(JGroupsTransport.java:127) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport$ChannelCallbacks.up(JGroupsTransport.java:1425) > at org.jgroups.JChannel.up(JChannel.java:816) > at org.jgroups.fork.ForkProtocolStack.up(ForkProtocolStack.java:134) > at org.jgroups.stack.Protocol.up(Protocol.java:339) > at org.jgroups.protocols.FORK.up(FORK.java:142) > at org.jgroups.protocols.relay.RELAY2.up(RELAY2.java:452) > at org.jgroups.protocols.FRAG3.up(FRAG3.java:171) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:339) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:339) > at org.jgroups.protocols.pbcast.GMS.up(GMS.java:872) > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:240) > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1008) > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:734) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:389) > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:590) > at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:131) > at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:203) > at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:253) > at org.jgroups.protocols.MERGE3.up(MERGE3.java:280) > at org.jgroups.protocols.Discovery.up(Discovery.java:295) > at org.jgroups.protocols.TP.passMessageUp(TP.java:1250) > at org.jgroups.util.SubmitToThreadPool$SingleMessageHandler.run(SubmitToThreadPool.java:87) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2317) FEEL Syntax error on function(bkm) containing `for` keyword

by Lukasz Hanik (Jira)

[ https://issues.redhat.com/browse/DROOLS-2317?page=com.atlassian.jira.plug... ] Lukasz Hanik commented on DROOLS-2317: -------------------------------------- Hi [~tari_manga], Thanks for prompt response, creating output data type helped to get rid of compiling error. > FEEL Syntax error on function(bkm) containing `for` keyword > ----------------------------------------------------------- > > Key: DROOLS-2317 > URL: https://issues.redhat.com/browse/DROOLS-2317 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Fedor Gavrilov > Priority: Major > Attachments: DROOLS-2317.dmn, Dynamic composition.dmn, screenshot-1.png, screenshot-2.png, screenshot-3.png > > > Attached model > {code:java} > Error compiling FEEL expression 'for item in Order.items return Federal Tax for Item( item )' for name 'Calculate Federal Taxes' on node 'Calculate Federal Taxes': syntax error near 'for' > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-95) (7.3.z) A doPrivileged it required to access the JASPI AuthConfigFactory

by Ilia Vassilev (Jira)

Ilia Vassilev created ELYWEB-95: ----------------------------------- Summary: (7.3.z) A doPrivileged it required to access the JASPI AuthConfigFactory Key: ELYWEB-95 URL: https://issues.redhat.com/browse/ELYWEB-95 Project: Elytron Web Issue Type: Bug Components: Undertow Servlet Reporter: Ilia Vassilev Assignee: Darran Lofthouse Fix For: 2.0.0.Alpha2, 1.7.0.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020