[JBoss JIRA] (DROOLS-3064) POJO Unification
by Edoardo Vacchi (Jira)
Edoardo Vacchi created DROOLS-3064:
--------------------------------------
Summary: POJO Unification
Key: DROOLS-3064
URL: https://issues.jboss.org/browse/DROOLS-3064
Project: Drools
Issue Type: Task
Reporter: Edoardo Vacchi
Assignee: Edoardo Vacchi
implement a general algorithm for recursive unification of POJO structures
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (SWSQE-450) Analyze Pipeline Execution Times
by Matt Mahoney (Jira)
Matt Mahoney created SWSQE-450:
----------------------------------
Summary: Analyze Pipeline Execution Times
Key: SWSQE-450
URL: https://issues.jboss.org/browse/SWSQE-450
Project: Kiali QE
Issue Type: Task
Reporter: Matt Mahoney
Assignee: Filip Brychta
PR Jenkins CI jobs are taking at times 30 min to complete. Are there any optimization opportunities that could improve on the pipeline execution time duration?
This is just *one* snapshot of a pipeline time breakdown, but perhaps s
17 minutes was waiting (Spin up the Jenkins Agent)
17 minutes running the jobs themselves
Almost 2 minutes (1.30 min) to Install Istio (Which doesn't sound too much)
3 Minutes to Install Bookinfo
8 minutes to Build and Deploy Kiali
4 minutes -> to deploy kiali with Kiali Checker
4 minutes -> to build with Yarn
2 Minutes to run e2e-tests
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFCORE-4147) (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFCORE-4147?page=com.atlassian.jira.plugi... ]
Marek Kopecký updated WFCORE-4147:
----------------------------------
Labels: Java11 (was: )
> (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
> ---------------------------------------------------------------
>
> Key: WFCORE-4147
> URL: https://issues.jboss.org/browse/WFCORE-4147
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Assignee: James Perkins
> Priority: Blocker
> Labels: Java11
>
> Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
> Merging of [PR3496|https://github.com/wildfly/wildfly-core/pull/3496] introduces:
> * new blocker regression
> ** Wrong JAVA_OPTS propagation on JDK8
> *** Default JAVA_OPTS, like max heap size (xmx), xms, etc. are not propagated to JVM on bat scripts
> *** set "GC_LOG=true"
> *** standalone.bat
> *** ->
> *** {noformat}===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: "C:\Users\Administrator\playground\wfly.30.gc\wildfly"
> JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
> JAVA_OPTS: ""-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman" -Xloggc:"C:\Users\Administrator\playground\wfly.30.gc\wildfly\standalone\log\gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading "
> ==============================================================================={noformat}
> *** it looks like some quotation bug
> *** according to the jconsole - max heap size (Xmx) is not set correctly (~1.8GB), according to the cli - program.name is not set correctly (program.name = "standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman")
> * new blocker bug
> ** wrong PowerShell GC logging
> *** "standalone.bat + jdk11 + gc enabled" creates:
> **** standalone\log\gc.log
> **** standalone\log\gc.log.0
> *** "standalone.ps1 + jdk11 + gc enabled" creates:
> **** * standalone\log\gc.log
> Target release of this jira should be WF15
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFCORE-4147) (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFCORE-4147?page=com.atlassian.jira.plugi... ]
Marek Kopecký updated WFCORE-4147:
----------------------------------
Description:
Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
Merging of [PR3496|https://github.com/wildfly/wildfly-core/pull/3496] introduces:
* new blocker regression
** Wrong JAVA_OPTS propagation on JDK8
*** Default JAVA_OPTS, like max heap size (xmx), xms, etc. are not propagated to JVM on bat scripts
*** set "GC_LOG=true"
*** standalone.bat
*** ->
*** {noformat}===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "C:\Users\Administrator\playground\wfly.30.gc\wildfly"
JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
JAVA_OPTS: ""-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman" -Xloggc:"C:\Users\Administrator\playground\wfly.30.gc\wildfly\standalone\log\gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading "
==============================================================================={noformat}
*** it looks like some quotation bug
*** according to the jconsole - max heap size (Xmx) is not set correctly (~1.8GB), according to the cli - program.name is not set correctly (program.name = "standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman")
* new blocker bug
** wrong PowerShell GC logging
*** "standalone.bat + jdk11 + gc enabled" creates:
**** standalone\log\gc.log
**** standalone\log\gc.log.0
*** "standalone.ps1 + jdk11 + gc enabled" creates:
**** * standalone\log\gc.log
Target release of this jira should be WF15
was:
Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
Merging of [PR3496|https://github.com/wildfly/wildfly-core/pull/3496] introduces:
* new blocker regression
** Wrong JAVA_OPTS propagation on JDK8
*** Default JAVA_OPTS, like max heap size (xmx), xms, etc. are not propagated to JVM on bat scripts
*** set "GC_LOG=true"
*** standalone.bat
*** ->
*** {noformat}===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "C:\Users\Administrator\playground\wfly.30.gc\wildfly"
JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
JAVA_OPTS: ""-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman" -Xloggc:"C:\Users\Administrator\playground\wfly.30.gc\wildfly\standalone\log\gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading "
==============================================================================={noformat}
*** it looks like some quotation bug
*** according to the jconsole - max heap size (Xmx) is not set correctly (~1.8GB), according to the cli - program.name is not set correctly (program.name = "standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman")
* new bug
** wrong PowerShell GC logging
*** "standalone.bat + jdk11 + gc enabled" creates:
**** standalone\log\gc.log
**** standalone\log\gc.log.0
*** "standalone.ps1 + jdk11 + gc enabled" creates:
**** * standalone\log\gc.log
Target release of this jira should be WF15
> (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
> ---------------------------------------------------------------
>
> Key: WFCORE-4147
> URL: https://issues.jboss.org/browse/WFCORE-4147
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Assignee: James Perkins
> Priority: Blocker
>
> Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
> Merging of [PR3496|https://github.com/wildfly/wildfly-core/pull/3496] introduces:
> * new blocker regression
> ** Wrong JAVA_OPTS propagation on JDK8
> *** Default JAVA_OPTS, like max heap size (xmx), xms, etc. are not propagated to JVM on bat scripts
> *** set "GC_LOG=true"
> *** standalone.bat
> *** ->
> *** {noformat}===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: "C:\Users\Administrator\playground\wfly.30.gc\wildfly"
> JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
> JAVA_OPTS: ""-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman" -Xloggc:"C:\Users\Administrator\playground\wfly.30.gc\wildfly\standalone\log\gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading "
> ==============================================================================={noformat}
> *** it looks like some quotation bug
> *** according to the jconsole - max heap size (Xmx) is not set correctly (~1.8GB), according to the cli - program.name is not set correctly (program.name = "standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman")
> * new blocker bug
> ** wrong PowerShell GC logging
> *** "standalone.bat + jdk11 + gc enabled" creates:
> **** standalone\log\gc.log
> **** standalone\log\gc.log.0
> *** "standalone.ps1 + jdk11 + gc enabled" creates:
> **** * standalone\log\gc.log
> Target release of this jira should be WF15
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFCORE-4147) (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
by Marek Kopecký (Jira)
Marek Kopecký created WFCORE-4147:
-------------------------------------
Summary: (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
Key: WFCORE-4147
URL: https://issues.jboss.org/browse/WFCORE-4147
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Reporter: Marek Kopecký
Assignee: James Perkins
Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
Merging of [PR3496|https://github.com/wildfly/wildfly-core/pull/3496] introduces:
* new blocker regression
** Wrong JAVA_OPTS propagation on JDK8
*** Default JAVA_OPTS, like max heap size (xmx), xms, etc. are not propagated to JVM on bat scripts
*** set "GC_LOG=true"
*** standalone.bat
*** ->
*** {noformat}===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "C:\Users\Administrator\playground\wfly.30.gc\wildfly"
JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
JAVA_OPTS: ""-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman" -Xloggc:"C:\Users\Administrator\playground\wfly.30.gc\wildfly\standalone\log\gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading "
==============================================================================={noformat}
*** it looks like some quotation bug
*** according to the jconsole - max heap size (Xmx) is not set correctly (~1.8GB), according to the cli - program.name is not set correctly (program.name = "standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman")
* new bug
** wrong PowerShell GC logging
*** "standalone.bat + jdk11 + gc enabled" creates:
**** standalone\log\gc.log
**** standalone\log\gc.log.0
*** "standalone.ps1 + jdk11 + gc enabled" creates:
**** * standalone\log\gc.log
Target release of this jira should be WF15
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2522:
--------------------------------
Description:
The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
h2. Manual Acceptance test
h3. Stunner
- Chrome (/)
- Firefox (/)
- Edge (/)
h3. DMN
- Chrome (/)
- Firefox (/)
- Edge (/)
was:
The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
h2. Manual Acceptance test
h3. Stunner
- Chrome
- Firefox
- Edge
h3. DMN
- Chrome (/)
- Firefox (/)
- Edge (/)
> [DMN Designer] Palette aesthetics
> ---------------------------------
>
> Key: DROOLS-2522
> URL: https://issues.jboss.org/browse/DROOLS-2522
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: DROOLS-2522 (resized).png, DROOLS-2522.mp4, Screen Shot 2018-10-01 at 12.26.15 PM.png, palette.png
>
>
> The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
> h2. Manual Acceptance test
> h3. Stunner
> - Chrome (/)
> - Firefox (/)
> - Edge (/)
> h3. DMN
> - Chrome (/)
> - Firefox (/)
> - Edge (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2522:
--------------------------------
Description:
The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
h2. Manual Acceptance test
h3. Stunner
- Chrome
- Firefox
- Edge
h3. DMN
- Chrome (/)
- Firefox (/)
- Edge (/)
was:
The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
h2. Manual Acceptance test
h3. Stunner
- Chrome
- Firefox
- Edge
h3. DMN
- Chrome (/)
- Firefox
- Edge
> [DMN Designer] Palette aesthetics
> ---------------------------------
>
> Key: DROOLS-2522
> URL: https://issues.jboss.org/browse/DROOLS-2522
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: DROOLS-2522 (resized).png, DROOLS-2522.mp4, Screen Shot 2018-10-01 at 12.26.15 PM.png, palette.png
>
>
> The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
> h2. Manual Acceptance test
> h3. Stunner
> - Chrome
> - Firefox
> - Edge
> h3. DMN
> - Chrome (/)
> - Firefox (/)
> - Edge (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3062) [DMN Designer] [UX] Automatic layout feature prompt
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3062?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-3062:
------------------------------------------
I've read the parent JIRA description and understand the concept, and I remember Edson's STD example (I think that was his point anyway). But it's difficult for me to propose a prompt without being able to visualize it better. Would it be possible to attache a before and after mockup, to see exactly how it would change for the user and why they'd use it? i.e., why it's not just that way to begin with if it's an improved layout. I could propose something more meaningful that way.
> [DMN Designer] [UX] Automatic layout feature prompt
> ---------------------------------------------------
>
> Key: DROOLS-3062
> URL: https://issues.jboss.org/browse/DROOLS-3062
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, drools-tools
>
> User should be able to invoke automatic layout feature anytime during diagram design phase. There should appear prompt that would explain the autolayout feature.
> Please propose the the prompt.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2522:
--------------------------------
Description:
The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
h2. Manual Acceptance test
h3. Stunner
- Chrome
- Firefox
- Edge
h3. DMN
- Chrome (/)
- Firefox
- Edge
was:
The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
h2. Manual Acceptance test
h3. Stunner
- Chrome
- Firefox
- Edge
h3. DMN
- Chrome
- Firefox
- Edge
> [DMN Designer] Palette aesthetics
> ---------------------------------
>
> Key: DROOLS-2522
> URL: https://issues.jboss.org/browse/DROOLS-2522
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: DROOLS-2522 (resized).png, DROOLS-2522.mp4, Screen Shot 2018-10-01 at 12.26.15 PM.png, palette.png
>
>
> The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
> h2. Manual Acceptance test
> h3. Stunner
> - Chrome
> - Firefox
> - Edge
> h3. DMN
> - Chrome (/)
> - Firefox
> - Edge
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months