December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4714) [DMN Designer] Filtering doesn't show results properly

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4714?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4714: -------------------------------- Attachment: filter-navigate-trough.webm > [DMN Designer] Filtering doesn't show results properly > ------------------------------------------------------ > > Key: DROOLS-4714 > URL: https://issues.jboss.org/browse/DROOLS-4714 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: filter-navigate-trough.webm, filter.webm > > > This issue is caused by DROOLS-4484 > See the attached video, when user filter a field of a structure, results are shown inappropriately. > h2. Acceptance criteria > - Issue from video fixed (/) > - Filter data type entry, navigate trough results (x) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4714) [DMN Designer] Filtering doesn't show results properly

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4714?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4714: -------------------------------- Description: This issue is caused by DROOLS-4484 See the attached video, when user filter a field of a structure, results are shown inappropriately. h2. Acceptance criteria - Issue from video fixed (/) - Filter data type entry, navigate trough results (x) [^filter-navigate-trough.webm] was: This issue is caused by DROOLS-4484 See the attached video, when user filter a field of a structure, results are shown inappropriately. h2. Acceptance criteria - Issue from video fixed (/) - Filter data type entry, navigate trough results (x) > [DMN Designer] Filtering doesn't show results properly > ------------------------------------------------------ > > Key: DROOLS-4714 > URL: https://issues.jboss.org/browse/DROOLS-4714 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: filter-navigate-trough.webm, filter.webm > > > This issue is caused by DROOLS-4484 > See the attached video, when user filter a field of a structure, results are shown inappropriately. > h2. Acceptance criteria > - Issue from video fixed (/) > - Filter data type entry, navigate trough results (x) [^filter-navigate-trough.webm] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4714) [DMN Designer] Filtering doesn't show results properly

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4714?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4714: -------------------------------- Description: This issue is caused by DROOLS-4484 See the attached video, when user filter a field of a structure, results are shown inappropriately. h2. Acceptance criteria - Issue from video fixed (/) - Filter data type entry, navigate trough results (x) was: This issue is caused by DROOLS-4484 See the attached video, when user filter a field of a structure, results are shown inappropriately. h2. Acceptance criteria - Issue from video fixed (/) - Filter data type entry, edit it (x) > [DMN Designer] Filtering doesn't show results properly > ------------------------------------------------------ > > Key: DROOLS-4714 > URL: https://issues.jboss.org/browse/DROOLS-4714 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: filter.webm > > > This issue is caused by DROOLS-4484 > See the attached video, when user filter a field of a structure, results are shown inappropriately. > h2. Acceptance criteria > - Issue from video fixed (/) > - Filter data type entry, navigate trough results (x) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4714) [DMN Designer] Filtering doesn't show results properly

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4714?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4714: -------------------------------- Description: This issue is caused by DROOLS-4484 See the attached video, when user filter a field of a structure, results are shown inappropriately. h2. Acceptance criteria - Issue from video fixed (/) - Filter data type entry, edit it (x) was: This issue is caused by DROOLS-4484 See the attached video, when user filter a field of a structure, results are shown inappropriately. h2. Acceptance criteria - Issue from video fixed (/) > [DMN Designer] Filtering doesn't show results properly > ------------------------------------------------------ > > Key: DROOLS-4714 > URL: https://issues.jboss.org/browse/DROOLS-4714 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: filter.webm > > > This issue is caused by DROOLS-4484 > See the attached video, when user filter a field of a structure, results are shown inappropriately. > h2. Acceptance criteria > - Issue from video fixed (/) > - Filter data type entry, edit it (x) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4714) [DMN Designer] Filtering doesn't show results properly

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4714?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4714: -------------------------------- Description: This issue is caused by DROOLS-4484 See the attached video, when user filter a field of a structure, results are shown inappropriately. h2. Acceptance criteria - Issue from video fixed (/) was: This issue is caused by DROOLS-4484 See the attached video, when user filter a field of a structure, results are shown inappropriately. > [DMN Designer] Filtering doesn't show results properly > ------------------------------------------------------ > > Key: DROOLS-4714 > URL: https://issues.jboss.org/browse/DROOLS-4714 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: filter.webm > > > This issue is caused by DROOLS-4484 > See the attached video, when user filter a field of a structure, results are shown inappropriately. > h2. Acceptance criteria > - Issue from video fixed (/) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4711) [DMN Designer] User is able to drag single data type entry horizontally

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4711?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4711: -------------------------------- Description: This issue is caused by DROOLS-4484 If there is single data type entry user is able to drag in horizontally. h2. Acceptance Criteria - Drag structure (/) - Drag structure field (/) - Drag simple type (/) was: This issue is caused by DROOLS-4484 If there is single data type entry user is able to drag in horizontally. h2. Acceptance Criteria - Drag structure - Drag structure field - Drag simple type > [DMN Designer] User is able to drag single data type entry horizontally > ----------------------------------------------------------------------- > > Key: DROOLS-4711 > URL: https://issues.jboss.org/browse/DROOLS-4711 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Optional > Labels: drools-tools > Attachments: horizontally.webm > > > This issue is caused by DROOLS-4484 > If there is single data type entry user is able to drag in horizontally. > h2. Acceptance Criteria > - Drag structure (/) > - Drag structure field (/) > - Drag simple type (/) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4711) [DMN Designer] User is able to drag single data type entry horizontally

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4711?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4711: -------------------------------- Description: This issue is caused by DROOLS-4484 If there is single data type entry user is able to drag in horizontally. h2. Acceptance Criteria - Drag structure - Drag structure field - Drag simple type was: This issue is caused by DROOLS-4484 If there is single data type entry user is able to drag in horizontally. > [DMN Designer] User is able to drag single data type entry horizontally > ----------------------------------------------------------------------- > > Key: DROOLS-4711 > URL: https://issues.jboss.org/browse/DROOLS-4711 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Optional > Labels: drools-tools > Attachments: horizontally.webm > > > This issue is caused by DROOLS-4484 > If there is single data type entry user is able to drag in horizontally. > h2. Acceptance Criteria > - Drag structure > - Drag structure field > - Drag simple type -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12838) Upgrade Infinispan to 9.4.17.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12838?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-12838: --------------------------------------- Tracking branch is https://github.com/wildfly-clustering/wildfly/tree/infinispan-9.4.x (as used in CI) > Upgrade Infinispan to 9.4.17.Final > ---------------------------------- > > Key: WFLY-12838 > URL: https://issues.jboss.org/browse/WFLY-12838 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Major > > Just a tracker for now. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12838) Upgrade Infinispan to 9.4.17.Final

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12838: ------------------------------------- Summary: Upgrade Infinispan to 9.4.17.Final Key: WFLY-12838 URL: https://issues.jboss.org/browse/WFLY-12838 Project: WildFly Issue Type: Component Upgrade Components: Clustering Reporter: Radoslav Husar Assignee: Paul Ferraro Just a tracker for now. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-276) Boot time of application built via S2I is much longer than in before-Galleon times

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-276?page=com.atlassian.jira.plugin.... ] Jean Francois Denise commented on WFWIP-276: -------------------------------------------- [~jbliznak], I agree with the scope. That has the size of an RFE but should be treated as an implementation detail. I am not sure we want to document/support this feature outside the cloud context. We will need to document the main workflow (how a server reach the stabilized state), but should be short and hide a lot of the details. > Boot time of application built via S2I is much longer than in before-Galleon times > ---------------------------------------------------------------------------------- > > Key: WFWIP-276 > URL: https://issues.jboss.org/browse/WFWIP-276 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Critical > Attachments: test-app.zip > > > As a consequence of Galleon RFEs EAP7-891 and mainly EAP7-1216 there is big difference in pod with EAP application start up time which requires S2I configuration. > This is an overview of quick comparison of average boot times of the application pods of the attached test app (we are not interested in build/deploy pod times etc): > ||17.0-6||pod time||EAP boot||config time > |#1 | 8283|6128|2155 > |#2 | 9446|7548|1898 > |#3 | 8767|6871| 1896 > |#4 | 8568|6272| 2296 > |#5 | 8000 |6362|1638 > ||average ||8613ms||6636ms||1977ms > ||18.0-7||pod time||EAP boot||config time > |#1 |13769|5716|8053 > |#2 |13362|5952|7410 > |#3 |14261|6093|8168 > |#4 |14322|6135|8187 > |#5 |13921|6326|7595 > ||average||13927ms||6044ms||7883ms > pod time = time from the pod start until EAP is fully booted (log contains {{started in ..}}) > EAP boot = time of boot EAP itself == {{started in ..}} > config time = the difference of previou timess = anything before EAP boot begins > Again we are talking here about the time needed for prepared application image to full start. We can clearly see the EAP boot times are comparable between 17 and 18 images but the configs times are almost 4 times longer with CD18 images. > This is very unfortunate as in my point of view the pod boot time is the most critical time for our users - they would typically prepare the app images only once in a time but their application can scale up and down many times during its uptime. > The cause of this that when S2I is needed with image 18.0+ the part of the configuration that was previously done during S2I build just once is now processed on *each* pod start. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2019