July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4369) Global Variable Dialog - Cancel button style

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4369: ----------------------------------- Summary: Global Variable Dialog - Cancel button style Key: DROOLS-4369 URL: https://issues.jboss.org/browse/DROOLS-4369 Project: Drools Issue Type: Bug Affects Versions: 7.25.0.Final Reporter: Jozef Marko Assignee: Jozef Marko Attachments: Screenshot from 2019-07-26 12-56-37.png See the attached picture. The cancel button in add global variable dialog is not styled properly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4368) HACEP Refactor DefaultKafkaConsumer

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4368?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4368: ---------------------------------- Description: Try to uniform leader/replica flow: - If I'm the leader it invokes `defaultProcessAsLeader` -> `processLeader` -> `process/processWithSnapshot` - If I'm a replica it invokes `defaultProcessAsAReplica` -> `consumeEventsFromBufferAsAReplica` -> `processEventsAsAReplica` -> `process` Try to remove most/all boolean and use proper method parameter Verify defaultProcessAsAReplica else branch. This should never happen because if leader sent a message about process a specific event, it should be available was: Try to uniform leader/replica flow: - If I'm the leader it invokes `defaultProcessAsLeader` -> `processLeader` -> `process/processWithSnapshot` - If I'm a replica it invokes `defaultProcessAsAReplica` -> `consumeEventsFromBufferAsAReplica` -> `processEventsAsAReplica` -> `process` Try to remove most/all boolean and use proper method parameter > HACEP Refactor DefaultKafkaConsumer > ----------------------------------- > > Key: DROOLS-4368 > URL: https://issues.jboss.org/browse/DROOLS-4368 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Daniele Zonca > Assignee: Massimiliano Dessi > Priority: Major > > Try to uniform leader/replica flow: > - If I'm the leader it invokes `defaultProcessAsLeader` -> `processLeader` -> `process/processWithSnapshot` > - If I'm a replica it invokes `defaultProcessAsAReplica` -> `consumeEventsFromBufferAsAReplica` -> `processEventsAsAReplica` -> `process` > Try to remove most/all boolean and use proper method parameter > Verify defaultProcessAsAReplica else branch. This should never happen because if leader sent a message about process a specific event, it should be available -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4368) HACEP Refactor DefaultKafkaConsumer

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4368: ------------------------------------- Summary: HACEP Refactor DefaultKafkaConsumer Key: DROOLS-4368 URL: https://issues.jboss.org/browse/DROOLS-4368 Project: Drools Issue Type: Task Components: core engine Reporter: Daniele Zonca Assignee: Massimiliano Dessi Try to uniform leader/replica flow: - If I'm the leader it invokes `defaultProcessAsLeader` -> `processLeader` -> `process/processWithSnapshot` - If I'm a replica it invokes `defaultProcessAsAReplica` -> `consumeEventsFromBufferAsAReplica` -> `processEventsAsAReplica` -> `process` Try to remove most/all boolean and use proper method parameter -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12129) The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory

by terry liang (Jira)

[ https://issues.jboss.org/browse/WFLY-12129?page=com.atlassian.jira.plugin... ] terry liang edited comment on WFLY-12129 at 7/26/19 5:27 AM: ------------------------------------------------------------- @brian.stansberry[mailto:brian.stansberry@redhat.com], Sorry that I thought regression label means which stage I got this error and I already removed it. I upgrade from wildfly 16.0 Final to 17.0 beta, and got that error that I disconnect from messaging activemq, the topic was removed. Actually this happens in Wildfly 17.0 Final too as I tried. was (Author: terryyrliang): @Brian Stansberry, Sorry that I thought regression label means which stage I got this error and I already removed it. I upgrade from wildfly 16.0 Final to 17.0 beta, and got that error that I disconnect from messaging activemq, the topic was removed. Actually this happens in Wildfly 17.0 Final too as I tried. > The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory > -------------------------------------------------------------------------------------------------- > > Key: WFLY-12129 > URL: https://issues.jboss.org/browse/WFLY-12129 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 17.0.0.Alpha1, 17.0.0.Beta1 > Reporter: terry liang > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: blocker-WF18 > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12129) The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory

by terry liang (Jira)

[ https://issues.jboss.org/browse/WFLY-12129?page=com.atlassian.jira.plugin... ] terry liang edited comment on WFLY-12129 at 7/26/19 5:27 AM: ------------------------------------------------------------- [~brian.stansberry], Sorry that I thought regression label means which stage I got this error and I already removed it. I upgrade from wildfly 16.0 Final to 17.0 beta, and got that error that I disconnect from messaging activemq, the topic was removed. Actually this happens in Wildfly 17.0 Final too as I tried. was (Author: terryyrliang): @brian.stansberry[mailto:brian.stansberry@redhat.com], Sorry that I thought regression label means which stage I got this error and I already removed it. I upgrade from wildfly 16.0 Final to 17.0 beta, and got that error that I disconnect from messaging activemq, the topic was removed. Actually this happens in Wildfly 17.0 Final too as I tried. > The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory > -------------------------------------------------------------------------------------------------- > > Key: WFLY-12129 > URL: https://issues.jboss.org/browse/WFLY-12129 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 17.0.0.Alpha1, 17.0.0.Beta1 > Reporter: terry liang > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: blocker-WF18 > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4367) Tests in drools coverage are not really using the executable model

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4367: ------------------------------------ Summary: Tests in drools coverage are not really using the executable model Key: DROOLS-4367 URL: https://issues.jboss.org/browse/DROOLS-4367 Project: Drools Issue Type: Bug Reporter: Luca Molteni Assignee: Tibor Zimanyi Such as https://github.com/kiegroup/drools/blob/ba9c79c4bfaf9cfc1ec2363bee3865c3d... Even if the test itself is parametrized, in the body it calls directly buildAll therefore discarding the executable model -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1311) Add PDF in kie-docs zips: upgrade to maven-asciidoctor-plugin 1.5.6 and enable the PDF generation

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-1311?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer closed DROOLS-1311. ------------------------------------------ Resolution: Done > Add PDF in kie-docs zips: upgrade to maven-asciidoctor-plugin 1.5.6 and enable the PDF generation > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-1311 > URL: https://issues.jboss.org/browse/DROOLS-1311 > Project: Drools > Issue Type: Feature Request > Components: docs > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Major > > Using approach from optaplanner-docs in asciidoc, the *kie-docs must also generated a PDF* (next to the html): > https://github.com/kiegroup/optaplanner/blob/master/optaplanner-docs/pom.... > Steps to take: > - first upgrade the maven-asciidoctor-plugin to version 1.5.6 or higher > - try uncommenting the generate-pdf execution here: https://github.com/kiegroup/kie-docs/blob/master/docs/pom.xml#L102 > - add the pdf in the assembly zips > Feel free to ping me (Geoffrey) if you tried this and you're stuck. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-807) Tablue Project Access

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-807?page=com.atlassian.jira.plugin.... ] Sunil Kondkar resolved SWSQE-807. --------------------------------- Resolution: Done > Tablue Project Access > --------------------- > > Key: SWSQE-807 > URL: https://issues.jboss.org/browse/SWSQE-807 > Project: Kiali QE > Issue Type: Task > Reporter: Matthew Mahoney > Assignee: Sunil Kondkar > Priority: Major > Labels: PQI > > [~skondkar] now has access to Tablue, but no visible projects. > [~pyadav] will you work with Sunil to get access to the following projects? > Swiftsunshine > Jaeger > Maistra -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-807) Tablue Project Access

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-807?page=com.atlassian.jira.plugin.... ] Sunil Kondkar reassigned SWSQE-807: ----------------------------------- Assignee: Sunil Kondkar (was: Prachi Yadav) > Tablue Project Access > --------------------- > > Key: SWSQE-807 > URL: https://issues.jboss.org/browse/SWSQE-807 > Project: Kiali QE > Issue Type: Task > Reporter: Matthew Mahoney > Assignee: Sunil Kondkar > Priority: Major > Labels: PQI > > [~skondkar] now has access to Tablue, but no visible projects. > [~pyadav] will you work with Sunil to get access to the following projects? > Swiftsunshine > Jaeger > Maistra -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-807) Tablue Project Access

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-807?page=com.atlassian.jira.plugin.... ] Sunil Kondkar commented on SWSQE-807: ------------------------------------- Got access to projects in Tableau. > Tablue Project Access > --------------------- > > Key: SWSQE-807 > URL: https://issues.jboss.org/browse/SWSQE-807 > Project: Kiali QE > Issue Type: Task > Reporter: Matthew Mahoney > Assignee: Prachi Yadav > Priority: Major > Labels: PQI > > [~skondkar] now has access to Tablue, but no visible projects. > [~pyadav] will you work with Sunil to get access to the following projects? > Swiftsunshine > Jaeger > Maistra -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 July 2019