April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3929) Cleanup and consolidate submarine-codegen

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-3929: -------------------------------------- Summary: Cleanup and consolidate submarine-codegen Key: DROOLS-3929 URL: https://issues.jboss.org/browse/DROOLS-3929 Project: Drools Issue Type: Task Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi Fix For: 8.0.0.Final After codegen refactoring there are some classes that do little more than carrying data around. This task is to remove those leftovers and in general cleanup the codebase so that any dangling part is removed or repurposed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3929) Cleanup and consolidate submarine-codegen

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3929?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3929: ----------------------------------- Sprint: 2019 Week 17-19 > Cleanup and consolidate submarine-codegen > ----------------------------------------- > > Key: DROOLS-3929 > URL: https://issues.jboss.org/browse/DROOLS-3929 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > After codegen refactoring there are some classes that do little more than carrying data around. This task is to remove those leftovers and in general cleanup the codebase so that any dangling part is removed or repurposed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2342) Replace FD with FD_ALL

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2342?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2342. ---------------------------- Resolution: Done > Replace FD with FD_ALL > ---------------------- > > Key: JGRP-2342 > URL: https://issues.jboss.org/browse/JGRP-2342 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.0 > > > In some sample configurations (e.g. tcp.xml), FD is still used. Replace this with FD_ALL or FD_ALL2. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2337) DiagnosticsHandler without reflection

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2337?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2337 at 4/23/19 3:54 AM: --------------------------------------------------------- Added class {{NonReflectiveProbeHandler}} (https://github.com/belaban/JGroups/blob/master/src/org/jgroups/stack/NonR...). For an example see https://github.com/belaban/JGroups/blob/master/tests/perf/org/jgroups/tes.... was (Author: belaban): Added class {{NonReflectiveProbeHandler}}. For an example see https://github.com/belaban/JGroups/blob/master/tests/perf/org/jgroups/tes.... > DiagnosticsHandler without reflection > ------------------------------------- > > Key: JGRP-2337 > URL: https://issues.jboss.org/browse/JGRP-2337 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > Attachments: bla.java > > > Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{"op"}} and {{"jmx"}} commands are handled via reflection. > However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image. > Investigate creating a {{ProbeHandler}} for {{"jmx"}} and {{"op"}} commands, which does not use reflection. 2 alternatives come to mind: > * Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application > * Point to a running stack. The code uses reflection (obviously this needs to run in non-native mode) to generate the native {{ProbeHandler}} from the list of protocols running in the current stack. This code can then be compiled and used in native image generation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2337) DiagnosticsHandler without reflection

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2337?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2337 at 4/23/19 3:53 AM: --------------------------------------------------------- Added class {{NonReflectiveProbeHandler}}. For an example see https://github.com/belaban/JGroups/blob/master/tests/perf/org/jgroups/tes.... was (Author: belaban): Added class {{NonReflectiveProbeHandler}}. For an example see https://github.com/belaban/JGroups/blob/master/tests/perf/org/jgroups/tes.... > DiagnosticsHandler without reflection > ------------------------------------- > > Key: JGRP-2337 > URL: https://issues.jboss.org/browse/JGRP-2337 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > Attachments: bla.java > > > Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{"op"}} and {{"jmx"}} commands are handled via reflection. > However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image. > Investigate creating a {{ProbeHandler}} for {{"jmx"}} and {{"op"}} commands, which does not use reflection. 2 alternatives come to mind: > * Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application > * Point to a running stack. The code uses reflection (obviously this needs to run in non-native mode) to generate the native {{ProbeHandler}} from the list of protocols running in the current stack. This code can then be compiled and used in native image generation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2337) DiagnosticsHandler without reflection

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2337?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2337. ---------------------------- Resolution: Done Added class {{NonReflectiveProbeHandler}}. For an example see https://github.com/belaban/JGroups/blob/master/tests/perf/org/jgroups/tes.... > DiagnosticsHandler without reflection > ------------------------------------- > > Key: JGRP-2337 > URL: https://issues.jboss.org/browse/JGRP-2337 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > Attachments: bla.java > > > Probe.sh sends commands to cluster nodes, and they are handled by each node's DiagnosticsHandler. {{"op"}} and {{"jmx"}} commands are handled via reflection. > However, reflection is not allowed by the GraalVM running in native mode, unless all attributes and methods of all protocols would be listed in a JSON file. This is apparently very costly as the native image builder creates a transitive closure over all classes whose methods and/or fields are listed in the JSON file, and thus includes too many classes in the native image. > Investigate creating a {{ProbeHandler}} for {{"jmx"}} and {{"op"}} commands, which does not use reflection. 2 alternatives come to mind: > * Offline creation and compilation: point to a list of protocols for which code is generated (an alternative ProbeHandler class). This class is then instantiated and set in the channel at runtime by the application > * Point to a running stack. The code uses reflection (obviously this needs to run in non-native mode) to generate the native {{ProbeHandler}} from the list of protocols running in the current stack. This code can then be compiled and used in native image generation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3928) DMN refactor codegen for same strategy

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3928: -------------------------------------- Summary: DMN refactor codegen for same strategy Key: DROOLS-3928 URL: https://issues.jboss.org/browse/DROOLS-3928 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3927) DMN compile error in codegen when maven plugin and expression in input clause

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3927: -------------------------------------- Summary: DMN compile error in codegen when maven plugin and expression in input clause Key: DROOLS-3927 URL: https://issues.jboss.org/browse/DROOLS-3927 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Attachments: Traffic Violation.dmn Using codegen via maven plugin with the attached model fails compilation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-719) Polarion Uploader - Required Fields

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-719?page=com.atlassian.jira.plugin.... ] Sunil Kondkar updated SWSQE-719: -------------------------------- Attachment: Screenshot_No-AutomationScript-MissingData.png > Polarion Uploader - Required Fields > ----------------------------------- > > Key: SWSQE-719 > URL: https://issues.jboss.org/browse/SWSQE-719 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure, pqi > Attachments: Screenshot_MissingData.png, Screenshot_No-AutomationScript-MissingData.png > > > The Polarion Uploader needs to include the following fields when creating test cases, so that PQI report is accurate: > - Level > - Component > - Test Type > - Sub Type > - Description > - Verifies > - Automation / Automation Script (When Type is "Automation") -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-719) Polarion Uploader - Required Fields

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-719?page=com.atlassian.jira.plugin.... ] Sunil Kondkar commented on SWSQE-719: ------------------------------------- Checked SWSQE-869. Everything looks correct. Now it populates 'approver' data. Now there is one missing data for: automation test case with no automation script. If we have some link or description in 'Automation Script' section, then its done. !Screenshot_No-AutomationScript-MissingData.png|thumbnail! > Polarion Uploader - Required Fields > ----------------------------------- > > Key: SWSQE-719 > URL: https://issues.jboss.org/browse/SWSQE-719 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure, pqi > Attachments: Screenshot_MissingData.png, Screenshot_No-AutomationScript-MissingData.png > > > The Polarion Uploader needs to include the following fields when creating test cases, so that PQI report is accurate: > - Level > - Component > - Test Type > - Sub Type > - Description > - Verifies > - Automation / Automation Script (When Type is "Automation") -- 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 April 2019