July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-902) Investigate why Red Hat Tutorial is not working with Maistra 0.12.0

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-902?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-902: ------------------------------------------ Issue Type: QE Task (was: Dev Task) > Investigate why Red Hat Tutorial is not working with Maistra 0.12.0 > ------------------------------------------------------------------- > > Key: SWSQE-902 > URL: https://issues.jboss.org/browse/SWSQE-902 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > It seems readinessProbe/LivenessProbes might be causing issues with maistra 0.12.0 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-902) Investigate why Red Hat Tutorial is not working with Maistra 0.12.0

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-902: --------------------------------------------- Summary: Investigate why Red Hat Tutorial is not working with Maistra 0.12.0 Key: SWSQE-902 URL: https://issues.jboss.org/browse/SWSQE-902 Project: Kiali QE Issue Type: QE Task Reporter: Guilherme Baufaker Rêgo It seems readinessProbe/LivenessProbes might be causing issues with maistra 0.12.0 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Elizabeth Clayton resolved DROOLS-3784. --------------------------------------- Resolution: Done Resolved per: https://issues.jboss.org/browse/DROOLS-4205 Note: The followup usability study will test the designs, unresolved issues will be filed as new jiras. > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: Field, UX, UXTeam, drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, constraints.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4588) @PreDestroy order violation JSR-345

by Igor Dmitriev (Jira)

[ https://issues.jboss.org/browse/WFCORE-4588?page=com.atlassian.jira.plugi... ] Igor Dmitriev updated WFCORE-4588: ---------------------------------- Description: Wildlfy 11.0.0 Bean X with @Startup and @Singleton annotations make long running task, Y bean (also with @Startup and @Singleton) @DependsOn bean X. Hovewer, during container shutdown (Ctrl+C) bean X is destroying first and closing resources, causing bean Y fall to error. Expected behavior: JSR-345: The container ensures that all singleton session beans with which a singleton session bean has a DependsOn relationship are still available during the PreDestroy callback. So, bean Y must be destroyed first, then bean X. was: Bean X with @Startup and @Singleton annotations make long running task, Y bean (also with @Startup and @Singleton) @DependsOn bean X. Hovewer, during container shutdown (Ctrl+C) bean X is destroying first and closing resources, causing bean Y fall to error. Expected behavior: JSR-345: The container ensures that all singleton session beans with which a singleton session bean has a DependsOn relationship are still available during the PreDestroy callback. So, bean Y must be destroyed first, then bean X. > @PreDestroy order violation JSR-345 > ----------------------------------- > > Key: WFCORE-4588 > URL: https://issues.jboss.org/browse/WFCORE-4588 > Project: WildFly Core > Issue Type: Bug > Components: Server > Environment: Windows 7 Pro, java 8 > Reporter: Igor Dmitriev > Assignee: Jeff Mesnil > Priority: Major > > Wildlfy 11.0.0 > Bean X with @Startup and @Singleton annotations make long running task, Y bean (also with @Startup and @Singleton) @DependsOn bean X. Hovewer, during container shutdown (Ctrl+C) bean X is destroying first and closing resources, causing bean Y fall to error. > Expected behavior: > JSR-345: The container ensures that all singleton session beans with which a singleton session bean has a DependsOn relationship are still available during the PreDestroy callback. > So, bean Y must be destroyed first, then bean X. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-901) Create jenkins master in PSI as a backup for jenkins2

by Filip Brychta (Jira)

Filip Brychta created SWSQE-901: ----------------------------------- Summary: Create jenkins master in PSI as a backup for jenkins2 Key: SWSQE-901 URL: https://issues.jboss.org/browse/SWSQE-901 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta Consider if we want to use existing jenkins https://issues.jboss.org/browse/SWSQE-605 Or create just some tmp jenkins on a VM in PSI -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4376) Abbreviated comparison with Map fails in executable-model

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4376?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-4376: --------------------------------- Story Points: 3 > Abbreviated comparison with Map fails in executable-model > --------------------------------------------------------- > > Key: DROOLS-4376 > URL: https://issues.jboss.org/browse/DROOLS-4376 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.24.0.Final > Reporter: Toshiya Kobayashi > Assignee: Luca Molteni > Priority: Major > Labels: support > > When we write abbreviated comparison with Map, > {noformat} > import java.util.Map; > rule R1 when > Map(this['money'] >= 65 && <= 75) > then > end > {noformat} > executable-model build fails. > {noformat} > [ERROR] testMapAbbreviatedComparison[FLOW_DSL](org.drools.modelcompiler.CompilerTest) Time elapsed: 0.258 s <<< ERROR! > java.lang.UnsupportedOperationException: Unknown expression: this["money"] > at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.findLeftLeafOfNameExpr(ExpressionTyper.java:875) > at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.findLeftLeafOfNameExpr(ExpressionTyper.java:867) > at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.findLeftLeafOfNameExpr(ExpressionTyper.java:867) > at org.drools.modelcompiler.builder.generator.DrlxParseUtil.trasformHalfBinaryToBinary(DrlxParseUtil.java:331) > at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:170) > at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpression(ExpressionTyper.java:118) > at org.drools.modelcompiler.builder.generator.drlxparse.ConstraintParser.parseBinaryExpr(ConstraintParser.java:309) > at org.drools.modelcompiler.builder.generator.drlxparse.ConstraintParser.getDrlxParseResult(ConstraintParser.java:114) > at org.drools.modelcompiler.builder.generator.drlxparse.ConstraintParser.drlxParse(ConstraintParser.java:81) > at org.drools.modelcompiler.builder.generator.visitor.pattern.PatternDSL.findAllConstraint(PatternDSL.java:124) > at org.drools.modelcompiler.builder.generator.visitor.pattern.PatternDSL.buildPattern(PatternDSL.java:191) > at org.drools.modelcompiler.builder.generator.visitor.ModelGeneratorVisitor.visit(ModelGeneratorVisitor.java:128) > at org.drools.compiler.lang.descr.PatternDescr.accept(PatternDescr.java:267) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-900) Create OCP 4.1 cluster in PSI as a backup for b22

by Filip Brychta (Jira)

Filip Brychta created SWSQE-900: ----------------------------------- Summary: Create OCP 4.1 cluster in PSI as a backup for b22 Key: SWSQE-900 URL: https://issues.jboss.org/browse/SWSQE-900 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta While the b22 will be down we need to have another cluster in PSI. We should use the latest OCP 4.1 and configure it the same way as b22 cluster. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4588) @PreDestroy order violation JSR-345

by Igor Dmitriev (Jira)

Igor Dmitriev created WFCORE-4588: ------------------------------------- Summary: @PreDestroy order violation JSR-345 Key: WFCORE-4588 URL: https://issues.jboss.org/browse/WFCORE-4588 Project: WildFly Core Issue Type: Bug Components: Server Environment: Windows 7 Pro, java 8 Reporter: Igor Dmitriev Assignee: Jeff Mesnil Bean X with @Startup and @Singleton annotations make long running task, Y bean (also with @Startup and @Singleton) @DependsOn bean X. Hovewer, during container shutdown (Ctrl+C) bean X is destroying first and closing resources, causing bean Y fall to error. Expected behavior: JSR-345: The container ensures that all singleton session beans with which a singleton session bean has a DependsOn relationship are still available during the PreDestroy callback. So, bean Y must be destroyed first, then bean X. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4205) DMN: UI enhancements for Data Type editor

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ] Elizabeth Clayton resolved DROOLS-4205. --------------------------------------- Resolution: Done > DMN: UI enhancements for Data Type editor > ----------------------------------------- > > Key: DROOLS-4205 > URL: https://issues.jboss.org/browse/DROOLS-4205 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: overview.png > > > *User Story* > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. > *Requested UI enhancements, based on user feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)* > NESTING ISSUES ARE HIGH PRIORITY > - Fix Dropdown menu labeling (Structure) > - Weird tooltip on Structured row. > - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder. > - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology. > - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu. > - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance. > - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu > RELATED SAVE INTERACTIONS (Save, Delete, Remove) > - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model > - - It's not obvious that you have to select the "check mark" to commit the change. > - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked. > OTHER: > - “Constraint” link was confusing, but location was good. > - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.) > - Questions around Save - should it not require Save at the row level. > - It feels unnatural to have to click the "Constraints" to open the Constraints modal. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4205) DMN: UI enhancements for Data Type editor

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4205?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4205: ------------------------------------------- [~karreiro] [~tirelli] The proposed redesigns are fully documented, so I'm planning to close this jira. * The redesign proposal is a google doc posted at: https://docs.google.com/presentation/d/10GZUd6oLaQohK27iJ1S6eF-WfvF8whXH5... * I also created 4 click-thru prototypes, for the usability study, that further detail the interactions - they're posted at: https://issues.jboss.org/browse/DROOLS-4372 > DMN: UI enhancements for Data Type editor > ----------------------------------------- > > Key: DROOLS-4205 > URL: https://issues.jboss.org/browse/DROOLS-4205 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: overview.png > > > *User Story* > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. > *Requested UI enhancements, based on user feedback from 7.4 implementation (keyboard shortcuts are covered in a separate Epic)* > NESTING ISSUES ARE HIGH PRIORITY > - Fix Dropdown menu labeling (Structure) > - Weird tooltip on Structured row. > - It wasn’t clear wasn’t what was nested, and looking for drag-n-drop to nest and reorder. > - Finding “Structure” in the dropdown - was separate, blue and at the bottom. Terminology. > - Nested data types, - all 3 used the field already open, but confusion about adding additional rows. Kebab didn’t work so well. Terminology for kebab menu. > - Due to the icon at the top level and no icons at the second level, the indenting of second level items is not very clear for users. Make sure the nesting is very clear at a glance. > - Better way to add a new field that is always visible to the user and clear to use without having to go into a kabob menu > RELATED SAVE INTERACTIONS (Save, Delete, Remove) > - Inline editing of the content in the rows would make the experience nicer than having a whole row edit model > - - It's not obvious that you have to select the "check mark" to commit the change. > - After adding a new data type field, undo becomes available but instead of removing the field, it resets the field name and type to the defaults. Redo then becomes available but doesn't appear to do anything when clicked. > OTHER: > - “Constraint” link was confusing, but location was good. > - In the dialog, “Add” wasn’t found too well. (Bug adding a null constraint.) > - Questions around Save - should it not require Save at the row level. > - It feels unnatural to have to click the "Constraints" to open the Constraints modal. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2019