June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4532) Investigate new JDK 13 regressions

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4532?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-4532 at 6/19/19 5:15 PM: ------------------------------------------------------------------- [~ropalka] Is the javax.security removal still expected in JDK 13? I don't know what "rampdown Phase I" formally means but it sounds like a point where once it begins entire packages wouldn't be getting removed. > Investigate new JDK 13 regressions > ---------------------------------- > > Key: WFCORE-4532 > URL: https://issues.jboss.org/browse/WFCORE-4532 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Richard Opalka > Assignee: Darran Lofthouse > Priority: Critical > Labels: jdk13 > Fix For: 9.0.2.Final > > > Latest Open JDK 13 Early Access 25 introduced three new regressions in our test suite. > Failing tests are: > wildfly-core/elytron/src/test/java/org/wildfly/extension/elytron/TlsTestCase.java > wildfly-core/testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosHttpMgmtSaslTestCase.java > wildfly-core/testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosNativeMgmtSaslTestCase.java > Could somebody from our security team have a look what is going on [~darran] ? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12212) Restore LastNodeToLeaveRemoteEJBTestCase, disabled for JDK 11 runs if necessary

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12212?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12212: ----------------------------------------- I see the originally work did include some work to adapt execution to JDK 11. In case these wasn't already considered, there's a separate surefire execution for this test, which perhaps could be in a separate profile only enabled for JDK 8. > Restore LastNodeToLeaveRemoteEJBTestCase, disabled for JDK 11 runs if necessary > ------------------------------------------------------------------------------- > > Key: WFLY-12212 > URL: https://issues.jboss.org/browse/WFLY-12212 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > Priority: Major > > The WLFY-11682 work[1] originally included a test, but that test was removed before the PR was merged. AIUI the test was removed because it could not work on JDK 11 due to byteman/arquillian issues.[2] The test did seem to work on JDK 8. > Having the test removed means this functionality isn't guarded against regression. So this issue is to track getting it restored. If it can be disabled on JDK 11 runs pending the arquillian/byteman issue being resolved, that's ok. > [1] https://github.com/wildfly/wildfly/pull/12133 > [2] https://github.com/arquillian/arquillian-extension-byteman/issues/25 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12212) Restore LastNodeToLeaveRemoteEJBTestCase, disabled for JDK 11 runs if necessary

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12212?page=com.atlassian.jira.plugin... ] Paul Ferraro reassigned WFLY-12212: ----------------------------------- Assignee: Richard Achmatowicz (was: Paul Ferraro) > Restore LastNodeToLeaveRemoteEJBTestCase, disabled for JDK 11 runs if necessary > ------------------------------------------------------------------------------- > > Key: WFLY-12212 > URL: https://issues.jboss.org/browse/WFLY-12212 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Brian Stansberry > Assignee: Richard Achmatowicz > Priority: Major > > The WLFY-11682 work[1] originally included a test, but that test was removed before the PR was merged. AIUI the test was removed because it could not work on JDK 11 due to byteman/arquillian issues.[2] The test did seem to work on JDK 8. > Having the test removed means this functionality isn't guarded against regression. So this issue is to track getting it restored. If it can be disabled on JDK 11 runs pending the arquillian/byteman issue being resolved, that's ok. > [1] https://github.com/wildfly/wildfly/pull/12133 > [2] https://github.com/arquillian/arquillian-extension-byteman/issues/25 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-255) PeriodicRotatingFileHandler doesn't rotate log content when using Compression

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-255?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-255: --------------------------------- Affects Version/s: (was: 1.5.9.Final) (was: 2.0.11.Final) > PeriodicRotatingFileHandler doesn't rotate log content when using Compression > ----------------------------------------------------------------------------- > > Key: LOGMGR-255 > URL: https://issues.jboss.org/browse/LOGMGR-255 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.11.Final > Reporter: Alain Baxter > Priority: Critical > > When configuring a PeriodicRotatingFileHandler where the suffix ends with .zip or .gz, as such: > {noformat} > <periodic-rotating-file-handler name="FILE" autoflush="true"> > <formatter> > <named-formatter name="PATTERN"/> > </formatter> > <file relative-to="jboss.server.log.dir" path="server.log"/> > <suffix value=".yyyy-MM-dd-HH.gz"/> > <append value="true"/> > </periodic-rotating-file-handler> > {noformat} > This is supposed to compressed the rotated logs to save space. See https://issues.jboss.org/browse/LOGMGR-30 > What I'm seeing is that the rotation log file is successfully created and compressed at the periodic interval, however the log file content is not removed. > This means that the log file itself continues to grow instead of rotating log content, and each rotation log contains the content from all the previous, so their size gets larger and larger: > {noformat} > -rw-r--r--. 1 jboss jboss 1779799 Jun 18 21:03 server.log > -rw-r--r--. 1 jboss jboss 21831 Jun 18 19:00 server.log.2019-06-18-18.gz > -rw-r--r--. 1 jboss jboss 55168 Jun 18 20:00 server.log.2019-06-18-19.gz > -rw-r--r--. 1 jboss jboss 88021 Jun 18 21:00 server.log.2019-06-18-20.gz > {noformat} > *NOTE:* This issue would exist for SizeRotatingFileHandler and PeriodicSizeRotatingFileHandler -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-255) PeriodicRotatingFileHandler doesn't rotate log content when using Compression

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-255?page=com.atlassian.jira.plugin... ] James Perkins reassigned LOGMGR-255: ------------------------------------ Assignee: James Perkins > PeriodicRotatingFileHandler doesn't rotate log content when using Compression > ----------------------------------------------------------------------------- > > Key: LOGMGR-255 > URL: https://issues.jboss.org/browse/LOGMGR-255 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 2.1.11.Final > Reporter: Alain Baxter > Assignee: James Perkins > Priority: Critical > > When configuring a PeriodicRotatingFileHandler where the suffix ends with .zip or .gz, as such: > {noformat} > <periodic-rotating-file-handler name="FILE" autoflush="true"> > <formatter> > <named-formatter name="PATTERN"/> > </formatter> > <file relative-to="jboss.server.log.dir" path="server.log"/> > <suffix value=".yyyy-MM-dd-HH.gz"/> > <append value="true"/> > </periodic-rotating-file-handler> > {noformat} > This is supposed to compressed the rotated logs to save space. See https://issues.jboss.org/browse/LOGMGR-30 > What I'm seeing is that the rotation log file is successfully created and compressed at the periodic interval, however the log file content is not removed. > This means that the log file itself continues to grow instead of rotating log content, and each rotation log contains the content from all the previous, so their size gets larger and larger: > {noformat} > -rw-r--r--. 1 jboss jboss 1779799 Jun 18 21:03 server.log > -rw-r--r--. 1 jboss jboss 21831 Jun 18 19:00 server.log.2019-06-18-18.gz > -rw-r--r--. 1 jboss jboss 55168 Jun 18 20:00 server.log.2019-06-18-19.gz > -rw-r--r--. 1 jboss jboss 88021 Jun 18 21:00 server.log.2019-06-18-20.gz > {noformat} > *NOTE:* This issue would exist for SizeRotatingFileHandler and PeriodicSizeRotatingFileHandler -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12212) Restore LastNodeToLeaveRemoteEJBTestCase, disabled for JDK 11 runs if necessary

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12212: --------------------------------------- Summary: Restore LastNodeToLeaveRemoteEJBTestCase, disabled for JDK 11 runs if necessary Key: WFLY-12212 URL: https://issues.jboss.org/browse/WFLY-12212 Project: WildFly Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro The WLFY-11682 work[1] originally included a test, but that test was removed before the PR was merged. AIUI the test was removed because it could not work on JDK 11 due to byteman/arquillian issues.[2] The test did seem to work on JDK 8. Having the test removed means this functionality isn't guarded against regression. So this issue is to track getting it restored. If it can be disabled on JDK 11 runs pending the arquillian/byteman issue being resolved, that's ok. [1] https://github.com/wildfly/wildfly/pull/12133 [2] https://github.com/arquillian/arquillian-extension-byteman/issues/25 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4199) [DMN Designer] Documentation tab - Add namespace to the diagram

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4199: --------------------------------------- Summary: [DMN Designer] Documentation tab - Add namespace to the diagram Key: DROOLS-4199 URL: https://issues.jboss.org/browse/DROOLS-4199 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Add namespace to the diagram cover. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 updated DROOLS-3784: -------------------------------------- Sprint: 2019 Week 23-25 > 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: Story > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Search feature in GDST 7.5

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4142: -------------------------------------- Sprint: (was: 2019 Week 23-25) > [GSS-RFE] UX design: Search feature in GDST 7.5 > ----------------------------------------------- > > Key: DROOLS-4142 > URL: https://issues.jboss.org/browse/DROOLS-4142 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png > > > This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation. > h1. Requirement > - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it. > - We may add auto-suggestion mechanism > - Do we need search history? > - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. > - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty. > h1. UX design > - Add magnifying-glass icon. > - Search-box can be popup window after clicking on icon or just pop field > - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both. > h1. Documentation > - Replace picture of GDT and DMN editor where they become obsolete > h1. Acceptance test > - Enter to large amount of data in search box > - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. > - Searching for non-existing result > - Result appearing once > - Result appearing multiple times > - Set of inputs: > *- A-Z > *- a-z > *- 0-9 > *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - + > *- Blank spaces -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4127) Review current implementation of Data Types section.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4127?page=com.atlassian.jira.plugi... ] Elizabeth Clayton resolved DROOLS-4127. --------------------------------------- Resolution: Done [~sarahjane] Marking this as Resolved. > Review current implementation of Data Types section. > ----------------------------------------------------- > > Key: DROOLS-4127 > URL: https://issues.jboss.org/browse/DROOLS-4127 > Project: Drools > Issue Type: Sub-task > Reporter: Elizabeth Clayton > Assignee: Sarahjane Clark > Priority: Major > Labels: UX, UXTeam > > Preparatory work for a usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. > * Review the current CICD implementation of the 7.x DMN editor, data types section. > * Review documented usability concerns. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 June 2019