January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-578) Add Istioctl from Maistra on Bookinfo as option on Bookinfo Pipeline Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-578?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-578: ------------------------------------------ Summary: Add Istioctl from Maistra on Bookinfo as option on Bookinfo Pipeline Job (was: Add Istioctl from Maistra on Bookinfo as option) > Add Istioctl from Maistra on Bookinfo as option on Bookinfo Pipeline Job > ------------------------------------------------------------------------ > > Key: SWSQE-578 > URL: https://issues.jboss.org/browse/SWSQE-578 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3573) Livelock in PseudoClockScheduler

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3573?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-3573: ---------------------------------- Issue Type: Bug (was: Enhancement) > Livelock in PseudoClockScheduler > -------------------------------- > > Key: DROOLS-3573 > URL: https://issues.jboss.org/browse/DROOLS-3573 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.17.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > Priority: Major > > When running test with pseudo clock and fireUntilHalt, it could end up in a livelock, where a while loop never ends [1]. The main problem in [1] is the isCancel() if statement. Current synchronization doesn't block cancelling the item during ongoing runCallBacksAndIncreaseTimer method call with [2]. That causes a livelock, because new item is not read in the loop, therefore it iterates over the same item again and again. This can be tested by running CepEspTest.testEventExpirationInSlidingWindow [3] more times in a row till it fails (it always fails after some time). > I will create a PR for this. > [1] https://github.com/kiegroup/drools/blob/04d58e7714844e73f68e6143e235bb557... > [2] https://github.com/kiegroup/drools/blob/04d58e7714844e73f68e6143e235bb557... > [3] https://github.com/kiegroup/drools/blob/2bf3c13de000864e7c45b9fd008af2f54... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3573) Livelock in PseudoClockScheduler

by Tibor Zimányi (Jira)

Tibor Zimányi created DROOLS-3573: ------------------------------------- Summary: Livelock in PseudoClockScheduler Key: DROOLS-3573 URL: https://issues.jboss.org/browse/DROOLS-3573 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 7.17.0.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi When running test with pseudo clock and fireUntilHalt, it could end up in a livelock, where a while loop never ends [1]. The main problem in [1] is the isCancel() if statement. Current synchronization doesn't block cancelling the item during ongoing runCallBacksAndIncreaseTimer method call with [2]. That causes a livelock, because new item is not read in the loop, therefore it iterates over the same item again and again. This can be tested by running CepEspTest.testEventExpirationInSlidingWindow [3] more times in a row till it fails (it always fails after some time). I will create a PR for this. [1] https://github.com/kiegroup/drools/blob/04d58e7714844e73f68e6143e235bb557... [2] https://github.com/kiegroup/drools/blob/04d58e7714844e73f68e6143e235bb557... [3] https://github.com/kiegroup/drools/blob/2bf3c13de000864e7c45b9fd008af2f54... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-578) Add Istioctl from Maistra on Bookinfo as option

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-578?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-578: ------------------------------------------ Sprint: Kiali Sprint #17 > Add Istioctl from Maistra on Bookinfo as option > ----------------------------------------------- > > Key: SWSQE-578 > URL: https://issues.jboss.org/browse/SWSQE-578 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-578) Add Istioctl from Maistra on Bookinfo as option

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-578: --------------------------------------------- Summary: Add Istioctl from Maistra on Bookinfo as option Key: SWSQE-578 URL: https://issues.jboss.org/browse/SWSQE-578 Project: Kiali QE Issue Type: Story Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-231) Load Test on Kiali UI

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-231?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo closed SWSQE-231. ----------------------------------------- Resolution: Duplicate Issue Covering in KIALI-1924 > Load Test on Kiali UI > --------------------- > > Key: SWSQE-231 > URL: https://issues.jboss.org/browse/SWSQE-231 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Test how the Kiali is going to behave with multiple users querying it at the same time -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-102) SNI - hostname notation for sni-mapping element does not conform generic rules

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFWIP-102?page=com.atlassian.jira.plugin.... ] Jan Stourac commented on WFWIP-102: ----------------------------------- Hmm, actually after some additional attempts, the fact is that the issue still persist and is still the same. If you want to use '.' character as a real dot-character, you still have to escape it with two backslashes. Otherwise it is accepted as a reg-exp expression for any character. > SNI - hostname notation for sni-mapping element does not conform generic rules > ------------------------------------------------------------------------------ > > Key: WFWIP-102 > URL: https://issues.jboss.org/browse/WFWIP-102 > Project: WildFly WIP > Issue Type: Bug > Environment: Wildfly build with undertow and wildfly-core modules build from following sources: > * https://github.com/stuartwdouglas/undertow/tree/sni > * https://github.com/stuartwdouglas/wildfly-core/tree/sni > Reporter: Jan Stourac > Assignee: Darran Lofthouse > Priority: Major > > Way of configuration of {{sni-mapping}} element in {{server-ssl-sni-context}} is not nice from UX and also does not conform the way it is generally used. > With current implementation administrator has to use following notation: > {code} > .*\.example\.com > {code} > This is standard reg-exp notation and is not for easy reading. I think following notation is much better and also is commonly used for this cases: > {code} > *.example.com > {code} > In other words - simple asterisk is used to match any subdomain and dot in our case does not stand for 'any single character'. Note that is the way it was described in [analysis document|https://github.com/wildfly/wildfly-proposals/pull/67/files#diff-...]. > Truth is that with this change we loose some flexibility, e.g. administrator won't be able to configure following: > {code} > www\.exa.ple\.com > {code} > But I doubt this is a common use case. WDYT? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3455: ------------------------------------- [~tirelli] [~karreiro] I added a revised mockup for enumeration. It uses a similar design approach but slightly different field label presentation. !enumeration.png|thumbnail! > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, enumeration.png, expression.png, range-redo.png, range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3455: -------------------------------- Attachment: enumeration.png > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, enumeration.png, expression.png, range-redo.png, range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3455: -------------------------------- Sprint: 2019 Week 02-04, 2019 Week 05-07 (was: 2019 Week 02-04) > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, expression.png, range-redo.png, range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 January 2019